Hi,
1) Der Grund warum die 404 Seite in Deutsch erscheint ist, dass wir Enfold schon übersetzt haben (de_DE.po & mo Dateien im Enfold/lang/ Ordner). Der Originaltext ist natürlich in Englisch.

2) Kriesi hat hier einfach nur ein großes Bild eingefügt (kein Slider). Möchtest du einen Slider einfügen verwende folgenden php Code im error404.php Template

do_shortcode("[av_layerslider id='3']");

und statt 3 füge die ID des gewünschten LayerSlider ein.

Tbh there’s no easy way to remove the spaces. The Enfold gallery does not support a masonry layout at the moment (eg like demonstrated here: http://www.nextgen-gallery.com/nextgen-pro/#promasonry ) and if the images have different aspect ratios you’ll see white spaces because the grid is not flexible. We’ll consider to add this gallery layout to Enfold in the future but (for now) I’d suggest to crop the thumbnails (then all thumbnails have the same size & aspect ratio) or to use the nextgen Gallery plugin with the pro extension: http://www.nextgen-gallery.com/nextgen-pro/ which supports the masonry layout too.

Hi,
Yes, there’s a limit on the form label length because our theme generates the form field name based on the form label text and i.e. the label “Yes, I am happy for AALC to use share my email address among full members of the AALC” will result in the field name “avia_yes_i_am_happy_for_aalc_to_use_share_my_email_address_among_full_members_of_the_aalc_1” which is probably too long. Just for test purposes – try to reduce the label characters of the checkbox and see if this fixes issue 2) – if yes I’ll look into a solution.

Hi,
no, because all of our themes use the default woocommerce templates and we just modify small parts of them with filters and actions (see the code in /wp-content/themes/enfold/config-woocommerce/config.php). The reason is that custom shop templates would make our theme incompatible with many third party WooCommerce shop extensions and we want to ensure that our theme users can use as many third party plugins as possible without modifying a theme file. If you want to create a custom shop template I’d recommend to read the codex articles here: http://docs.woothemes.com/documentation/plugins/woocommerce/woocommerce-codex/theming/ about theming. I’d recommend to avoid changes to the theme files especially because they’re often not upgrade safe and you need to check the template changes before you can upgrade WooCommerce to the latest version…

You can try http://www.codebeautifier.com/?lang=en

I strongly recommend to use Please use Codestyling: http://wordpress.org/plugins/codestyling-localization/ to translate the theme.
Install the plugin, go to Tools > Localization and select “Themes”. Then search for “Enfold” in the list and click on “Add new language”. Then select your language from the list and click the “create po-file” button. Click on “Rescan” to fetch all text strings. Then click on “Edit” and translate the required strings from the “avia_framework” textdomain. At least click the “create mo file” button next to the “Textdomain” selection dropdown (top left corner).

Hi,
I think I found a solution for the revisions issue and we’ll fix this in the next update (Enfold 2.2). For a quick fix add following code to the bottom of functions.php

add_action('wp_restore_post_revision',  'avia_builder_restore_revision', 10, 2);

        function avia_builder_restore_revision( $post_id, $revision_id )
        {
            //$post     = get_post($post_id);
            $revision = get_post($revision_id);
            $meta_fields = array('_aviaLayoutBuilderCleanData', '_avia_builder_shortcode_tree');

            foreach($meta_fields as $meta_field)
            {
                $builder_meta_data  = get_metadata( 'post', $revision->ID, $meta_field, true );

                if (!empty($builder_meta_data))
                {
                    update_post_meta($post_id, $meta_field, $builder_meta_data);
                }
                else
                {
                    delete_post_meta($post_id, $meta_field);
                }
            }
        }

It seems like your menu name includes Cyrillic characters and this can break our menu script. A quick fix is to rename the menu. Just use latin characters for the menu name and re-save it. Eg call the main menu “Main Menu” and the top menu “Sub Menu” and it should work.

We’ll change the menu classes & ids in the next version and then you should be able to use Cyrillic, Greek, etc. characters for the menu(s) too without breaking the menu script.

I’m not sure if it will do what you want but this plugin: http://wordpress.org/plugins/groups/ allows you to restrict the access to certain pages/areas by creating groups with custom capabilities. You can assign users to the groups and then add capabilities to the group. The logic is very flexible because you’re not limited to membership levels but you have full control over all capabilities of the group members.

Hi,
1) No, probably not. I’d be surprised if such a plugin exists. I think Kriesi’s inspiration was this script: http://tympanus.net/Tutorials/CircularNavigation/index2.html but he heavily modified the design and code.

2) You can hire a freelancer to implement such a feature. Kriesi said he’ll write some tutorials about his child theme functions but I can’t promise you that the “cycle nav” will be covered by the tutorial. I doubt that he’ll release it as a free/paid plugin or as a template builder element.

I think that a third party plugin causes this issue because something adds a lot of IE related code to the website. I.e. code like

<!--[if gte mso 9]><xml><br />
<w:worddocument><br />
<w:view>Normal</w:view><br />
<w:zoom>0</w:zoom><br />
<w:trackmoves></w:trackmoves><br />
<w:trackformatting></w:trackformatting><br />
<w:punctuationkerning></w:punctuationkerning><br />
<w:validateagainstschemas></w:validateagainstschemas><br />
<w:saveifxmlinvalid>false</w:saveifxmlinvalid><br />
<w:ignoremixedcontent>false</w:ignoremixedcontent><br />
<w:alwaysshowplaceholdertext>false</w:alwaysshowplaceholdertext><br />
<w:donotpromoteqf></w:donotpromoteqf><br />
<w:lidthemeother>EN-US</w:lidthemeother><br />
<w:lidthemeasian>X-NONE</w:lidthemeasian><br />
<w:lidthemecomplexscript>X-NONE</w:lidthemecomplexscript><br />
<w:compatibility><br />
<w:breakwrappedtables></w:breakwrappedtables><br />
......

which uses the conditional tag

<!--[if gte mso 9]>

to “hide” the information from other browsers. But obviously IE8 and IE9 are affected and the code seems to break them.

Hallo,
verwendet ihr Windows oder Mac als Betriebssystem? Ich kann den Fehler auf meinen PCs (Win8) mit keinen Browser reproduzieren – zB Chrome: http://www.screenr.com/vmlH

Ich habe den Thread einmal für Kriesi markiert, da er sich die Website auch mit MacOSX ansehen kann.

Hi,
yes – thank you for the notice. We are aware of the issue and it will be fixed in the next version.

Maybe you need to exclude one or more js files from the “minify” cache. Can you post a link to your website please – it helps us to find the js code which causes the error(s).