Forum Replies Created

Viewing 18 posts - 1 through 18 (of 18 total)
  • Author
    Posts
  • Hi Mike,

    Thanks for your reply. All clear.
    #topicclosed

    Best regards,
    Joris

    Hi Yigit,

    Thanks for your quick response/fix! Replacing the files did the trick for me.

    I presume (and hope) these fixes will be implemented in an Enfold update soon? I’ve got quite a few websites using Enfold and it’s quite cumbersome to update all files for all websites by hand.

    Best regards,
    Joris

    in reply to: Update Enfold from 5.2.1 to 5.3 doesn't work with WPML 4.5.14 #1376680

    Same for my sites running WPML 4.5.14 and Enfold 5.3. I’ve had to downgrade to PHP 7.4 to get the sites running again.

    PHP Fatal error: Uncaught InvalidArgumentException: Trying to read non existing property in class avia_superobject: wpml in /wp-content/themes/enfold/framework/php/base-classes/class-object-properties.php:33

    Best, Joris

    in reply to: Sidebars disappear on 4.9.2 #1345873

    Hi, same here. Please fix

    in reply to: Dequeue Parent theme custom.css #1312719

    Hi thinkjarvis,

    You probably want to de-queue custom.css to improve performance. The better way to improve performance is to enable “CSS file merging and compression” at the Performance setting of the theme. This way only one CSS-file for the theme will be loaded and there is no need to de-queue any other CSS-files.

    in reply to: Troubles with 4.8.4 update on Icon box and #1310987

    Same here. Also issues with styling of buttons and no styles (padding, background-color) being applied to columns. Went back to 4.8.3

    in reply to: Small bug in navigation menu lay-out when included via widget #1188430

    Hi Ismael,

    Great! Topic closed.

    Joris

    in reply to: Small bug in navigation menu lay-out when included via widget #1187654

    Hi Ismael,

    Thanks for your reply.

    I’ve created a few pages at our own site to show the issue: https://emazing.nl/chapter-1/

    I’ve created a navigation menu and added it to a widget area via the ALB to all pages. I’ve also included the navigation menu via the sidebar. Both menus show the same lack of indentation with the submenu when viewing a page which is not part of the current chapter.

    I don’t think it’s really important because the fix is quite ease and also because I hardly ever see a (Enfold) website with this kind of navigation. I ran into this because a client of ours uses a navigation menu in this manner.

    Best regards,
    Joris

    in reply to: Enfold 4.7.1 Timeline Module Broken #1173339

    Thx Jo. Also for explaining the fix in detail.

    in reply to: Enfold 4.7.1 Timeline Module Broken #1173309

    Pretty clear: Call to undefined function rray_key_exists() in /wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/timeline/timeline.php:981

    It’s a typo: if( !rray_key_exists( ‘font-size’, $this->title_styling ) ) Please fix.

    in reply to: Social Share Buttons #1166905

    Hi,

    I believe the newly introduced (Version 4.6.3.1) ” rel=”noreferrer noopener” for a target=”_blank” and cross domain links to ALB elements, menus and other links ” causes the icons to disappear. This also happens to social profile icons in header and footer.

    The function avia_targeted_link_rel() is called in line 173 of enfold\includes\helper-social-media.php.
    Commenting it out //$html = avia_targeted_link_rel( $html ); solves the problem for now.

    Best regards,

    Emazing

    • This reply was modified 5 years ago by Emazing.
    in reply to: Woocommerce deprecation error only with Enfold #1094433

    Hi antisemitism,

    Enfold is not properly compatible with Woocommerce 3.6+ because Enfold uses a deprecated WooCommerce function (get_woocommerce_term_meta).

    Please note the “error” you are getting actually is a “notice”. You could suppress this message by disabling the WordPress debugging mode:
    Change define( ‘WP_DEBUG’, true ) to define( ‘WP_DEBUG’, false ) in your wp-config.php file to suppress this message/error/notice for now.

    In the meantime I’m quite sure Enfold will replace the deprecated function in the next release of Enfold.

    in reply to: Woocommerce deprecation error only with Enfold #1094384

    FYI
    get_woocommerce_term_meta is used on multiple lines in:

    /enfold/config-woocommerce/admin-options.php
    /enfold/config-woocommerce/config-356.php
    /enfold/config-woocommerce/config.php

    Best regards,
    Emazing

    in reply to: Forms #616295

    Hi Andy,

    It seems that the same bug has been reintroduced in version 3.5.2 but now on a different line number:
    Notice: Undefined variable: extra in \wp-content\themes\enfold\framework\php\class-form-generator.php on line 592

    I’ve now defined the variable “extra” on line 571 to fix this error:

    line 571: $p_class = $required = $element_class = $prefilled_value = $select = $extra = "";

    Best regards,
    Joris

    in reply to: Problems after update to version 3.4.6 #553251

    Hi,

    Problem solved I guess. $suboptions[1] did not have a value because I (we?) didn’t enter it when composing the form.

    When adding a Select Element to a form the example next to the “Form Element Options” says you have to enter the options as Option 1, Option 2, Option 3 (comma separated) but the code expects a comma separated key-value pair. You should enter the options as Option 1|option1, Option 2|option2, Option 3|option3. Is this correct?

    Best regards,
    Emazing

    in reply to: Problems after update to version 3.4.6 #553183

    Hi,

    I’ve deactivate all plugins and completely delete Enfold from my WordPress theme directory before downloading + uploading a fresh copy from themeforest but I get the same error “Notice: Undefined offset: 1 in /wp-content/themes/enfold/framework/php/class-form-generator.php on line 595”. On line 595 it says “$key = trim($suboptions[1]);” which doesn’t exists.

    				$suboptions =  explode('|',$option);
    				if(is_array($suboptions))
    				{
    					$key = trim($suboptions[1]);
    					$value = trim($suboptions[0]);
    				}
    

    I’m not an experienced programmer but could it be that “$suboptions = explode(‘|’,$option);” always returns an array even though $option is a single string (single value from select options submitted via the admin-panel) without ‘|’ in i?. Because the array has only one value this causes $suboptions[1] to generate the error.

    I’ve replaced line 595 with $key = isset($suboptions[1]) ? trim($suboptions[1]) : trim($suboptions[0]); and that solves it for now.
    It also might be a solution to remove all lines mentioned above since is_array($suboptions)) is always true and $suboptions[1] is always empty.

    NB. If I would turn off WordPress debugging the notice goes away but in that case $suboptions[1] (used as the value for the option in the dropdownmenu) is empty and this causes the value not to be sent when submitting the form.

    Best regards,
    Emazing

    in reply to: Forms #530623

    Hi Ismael,

    I’ve created a temporary testpage at a customers website and sent you the details via the ‘private content’ option.

    Best regards,
    Joris

    in reply to: Forms #529954

    Hey there,

    I can reproduce this error (PHP Notice: Undefined variable: extra in path/to/enfold/framework/php/class-form-generator.php on line 299) when using a form WITHOUT LABELS and a TEXT INPUT which has NO VALIDATION.

    I’ve now defined the variable extra on line 227 to fix this error:

    line: 277 $p_class = $required = $element_class = $value = $extra = "";

    Best regards,
    Joris

Viewing 18 posts - 1 through 18 (of 18 total)