To solve this:

1. Enable twentytwelve as theme.

2. Open the post, save it once (you should see the contents of the avia builder).

3. You may also try to recover from a revision.

4. Re-enable Enfold and everything should be fine.

To prevent this from happening:

1. Limit the amount of revisions.

2. Increase the autosave feature of WordPress.

Open up wp-config.php and add the following constant above /* That’s all, stop editing! Happy blogging. */

/** Extending the autosave feature to 20 minutes */

define('AUTOSAVE_INTERVAL', 1200 );

/** Limit draft count */

define('WP_POST_REVISIONS', 3);

Short explanation:

When you start editing with the builder and open up lets say a toggle (editing one of the elements with the MCE) a misbehaviour may occur when WordPress autosaves in the background. Raising the autosave won’t solve the prob, but prevents the above situation.

Memory issues: Already checked your PHP Max (there are some plugins for that)? You may also try to enable the WordPress debug mode in wp-config.php.

Good luck!

What you can do is:

1) Open a blank page or create a new one

2) Add only the testimonial slider and fill it with the right content

3) Click the “Templates” button on the top right of your Avia Layout Builder content

4) Click “Save Entry as Template” and give it a name

5) Close the page (shouldn’t need to save this page)

6) Open the page where you want to add the testimonial slider and click that “Templates” button again

7) Choose the name you gave the testimonial slider and it will be added to the bottom of your page content

Once added, you can reposition it as usual.

Keep in mind that any further changes you make after you saved it won’t be saved to the template. So if you ever lose the testimonial slider, you can add it again from the templates but it will be the version it was when you originally saved that.

It’s better than nothing, and I’m not fond of this method. Just for this issue I don’t use the testimonial slider. It should really be a central item where you change it once and it changes everywhere it’s shown, like a widget etc.

Perhaps there are better alternatives, so best wait for possible feedback from others.

RGBA (and HSL) color definitions won’t make it in IE and Opera. You should have a look at progressive enhancements to get things going. To get it straight: IE likes to have it’s very own solution for this.

The Microsoft gradient takes a start and end color. If you look a lil bit closer to the hex value, you’ll notice the two additional digits in front. This is the alpha channel to have it transparent. So if you define 0.6 in RGBA, the digits should be 60. Additionally, the zoom:1 prevents crappy font rendering (somehow).

No worries, found a different thread with a function.php edit.

https://kriesi.at/support/topic/breadcrumbs-change-you-are-here

Thanks!

Hi!

You can use following css code to add a padding before the slider element. Make sure that no other element is used before the slider, otherwise the code won’t work

.avia-fullwidth-slider.avia-builder-el-0{

padding-top: 75px;

}

I’d recommend to insert it into the quick css field.

Regards,

Peter

1) Yes, it’s not always possible to combine all elements/shortcodes with each other. There’re some limitations…

2) However afaik the notification shortcode should work with the tabs. I’d use the “shortcode generator” (magic wand icon in the TinyMCE editor field on the post editor screen) to generate the “notification” shortcode. Then copy the shortcode text and insert it into a tab element and save the content. And voila – you should have a notification box inside a tab. I made a short screencast to demonstrate the workflow: http://www.screenr.com/JsgH

3) Please don’t add the shortcode html code directly – wordpress will add paragraph tags to it because of the wpautop filter.

The rgba value syntax seems to be correct. Try to change the color value (this converter will help you: http://hex2rgba.devoth.com/ ) or try to add a !important tag to it:

#top .page-id-2429 #av_section_1 .avia_textblock {

background: rgba(55,55,55,0.6) !important;

}

Try this one:

Just to show you the difference between #color and rgba(). ;)

If you like to apply it to all pages, try this selector: .page .avia_textblock