This is maybe caused by your own css-styling – as far as I could figure this out, you are using a child theme. So you should check your stuff first…

On the second sight, there’s the alpha class missing on the surrounding container, but this won’t affect the box sizing. Also, there’s a margin which obviously shouldn’t be there.

Example:

Try to set this CSS:

.sidebar_left .content {margin-right:0;}

This solves the color section prob, but also affects other elements.

In addition, the style.css of your child is missing (Failed to load resource: the server responded with a status of 404 (Not Found) ).

>> http://lavitasana.oscar.nl/wp-content/themes/enfoldchild/style.css?ver=1

This is all I can point out to you…

Guude aach! :)

After a little bit of investigation there seems to be a defect (http://bbpress.trac.wordpress.org/ticket/2309). It may be fixed with a future release of bbPress. This may be the one leading to your pages error.

The two other notices belong to a double declaration of a constant – you may remove one of them. :)

Memory ain’t a prob, but this should ALWAYS be checked when running wordpress. You have a total of 256M – remove any limitations you have inserted before (WP_MEMORY_LIMIT).

I would encourage you to set up a new and fresh install of wordpress on the same server. Create a subdirectory (like ‘wp-test’) in your home directory. Configure WordPress and install Enfold right after that. Setup your Permalinks as desired and create a few pages. If everything is okay, enable the debugging in wp-config. After that, go ahead with your plugins – one by one. Try to reproduce the misbehaviour. bbPress should be the last…

If you are still stuck, one of the moderators here may have a look to your installation.

Best wishes!

Did you put it in Custom CSS field in Enfold setup?

You should provide more infos on your prob and maybe a screenshot… :)

Please deaktivate any Plugin and try to use this one:

http://wordpress.org/plugins/wp-memory-usage/

Have a look to your dashboard and also your footer (backend) – it will show you the available memory there. You are probably running low on PHP memory…

Yes, I think there is a small problem too. While experimenting with the home page, I’ve also added a Color Section to the very end enabling the “parallax”-effect (fixed bgr). Doesn’t stick only to Mac users… :)

Image was displayed, but when I scrolled down, the footer began to flicker. At the end of the page the background image was gone (white bgr). Didn’t dive into that, because I won’t use that effect at the end of a page (pretty much useless). :)

But for now it seems to be gone on my installation. I’m still using 1.4.

Have a look here (the section won’t be there for long): http://pcawp.portalservices.de/ – maybe you can figure something out by yourself…

Update: Changed position and some really Chrome-specific things are going on… I’ll try to change scroll-behaviour on Chrome…

Video: http://www.screenr.com/VCHH

@media only screen and (max-width: 767px) {

.responsive #main avia-layerslider {

display:none;

}

}

Should do the trick… (untested)

Good to know. Never reading any tooltips… :D But I checked the LayerSlider code and there’s a do_shortcode for the Div-Section of a Slide. Should also work with nested ones.

Quick and dirty: insert the shortcode to a (blank) page and locate the generated output in source view. Copy it over in your LayerSlider element and it should work fine.

Obviously, the LayerSlider won’t process any shortcodes. Could be annoying if you use a gallery… :)

Otherwise, have a look over here: http://codecanyon.net/item/layerslider-responsive-wordpress-slider-plugin-/1362246

There’s a changelog which files are modified. You’ll only need to exchange those files. It’s just a minor update… :)

All three issues are related to a low memory setup of your webspace and/or server. Please check the memory_limit which is allocated to PHP.

Try this plugin – it adds the values to your footer: http://wordpress.org/plugins/wp-memory-usage/

Set WB_DEBUG in wp-config.php to true, open up a page or portfolio and have a look to the footer of your WordPress backend. If there’s an error showing up regarding a memory exhaust, you’ll have to raise your limits.

Many people had this issues since the past months. You should have at least 96M allocated to PHP. If you are going to use some heavier plugins like WooCommerce or WPML (or a lot of small ones), you need to have at least 128M.

Good luck!

After investigation the memory consumption of the avia framework you should at least allocate 96M to PHP. If you use other plugins, that may add buttons (or any other element) to the MCE, you should raise it to 128M.

To be on the safe side and especially when using WPML I recommend 256M as a minimum.

Check your memory with this plugin on the go: http://wordpress.org/plugins/wp-memory-usage/

If you just like to embed the flag icons, you may need to follow these steps:

Open functions.php, locate in line 362

add_theme_support( 'avia_post_meta_compat');

Below add:

/*

* F1 add: Language selector (flags) function for header (right menu)

*/

function header_lang_flags(){

$languages = icl_get_languages('skip_missing=0&orderby=code');

if(!empty($languages)){

echo '<ul>';

foreach($languages as $l){

echo '<li>';

if($l['country_flag_url']){

if(!$l['active']) echo '<a href="'.$l['url'].'">';

echo '<img src="'.$l['country_flag_url'].'" alt="'.$l['native_name'].'" title="'.$l['native_name'].'" />';

if(!$l['active']) echo '</a>';

}

echo '</li>';

}

echo '</ul>';

}

}

Then open up header.php, locate on line 113:

do_action('avia_meta_header');

Add below:

header_lang_flags();

Have fun.

You also may create a childtheme to add your personal stuff, but that won’t help you eitherway… lots of code to do… :)

So I’d like to mention you should just enable the builder for the post types.

1. Locate meta.php within config-templatebuilder/avia-template-builder/config/

2. Have a look at lines 4-7:

$boxes = array(

);

Change to:

$boxes = array(

);

You just have to add the ‘post’ type to enable the builder for posts. Don’t worry – actually it’s working very fine. If you encounter any errors, just remove it.