Forum Replies Created

Viewing 15 replies - 1 through 15 (of 82 total)
  • Thread Starter dhunink

    (@dhunink)

    @gagan0123 are you looking to fix this, following the suggestion made by @hbwarper?

    Thread Starter dhunink

    (@dhunink)

    Hi!
    I’ve done some more debugging and nailed it down to specific situation where there’s no menu set for a menu location. Happens a lot when the plugin is installed on a new installation where the user did not yet created menu’s and/or assigned these menu’s to a menu location.
    In that case the $item object is indeed empty, which is normal behavior. But the code always assumes the $item object consists of something.
    My suggestion:
    add a simple check in the function that checks if the $item object has the desired content. If not, the function does not need to continue.

    Just what I was looking for 😀
    Using taxonomies to define relationships between users would be absolutely amazing!

    Seeing this when trying to activate:

    Fatal error: Uncaught Error: Class ‘MailChimp_WooCommerce_MailChimpApi’ not found in /customers/f/d/e/hoeve-bouwlust.nl/httpd.www/wp-content/plugins/mailchimp-for-woocommerce/mailchimp-woocommerce.php:83 Stack trace: #0 /customers/f/d/e/hoeve-bouwlust.nl/httpd.www/wp-content/plugins/mailchimp-for-woocommerce/mailchimp-woocommerce.php(357): mailchimp_get_api() #1 /customers/f/d/e/hoeve-bouwlust.nl/httpd.www/wp-content/plugins/mailchimp-for-woocommerce/includes/class-mailchimp-woocommerce-activator.php(47): mailchimp_update_connected_site_script() #2 /customers/f/d/e/hoeve-bouwlust.nl/httpd.www/wp-content/plugins/mailchimp-for-woocommerce/mailchimp-woocommerce.php(220): MailChimp_Woocommerce_Activator::activate() #3 /customers/f/d/e/hoeve-bouwlust.nl/httpd.www/wp-includes/class-wp-hook.php(286): activate_mailchimp_woocommerce(”) #4 /customers/f/d/e/hoeve-bouwlust.nl/httpd.www/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(”, Array) #5 /customers/f/d/e/hoeve-bouwlust.nl/httpd.www/wp-includes/plugin.php(453): WP in /customers/f/d/e/hoeve-bouwlust.nl/httpd.www/wp-content/plugins/mailchimp-for-woocommerce/mailchimp-woocommerce.php on line 83

    Hi,

    I’m looking at exactly this functionality and decided to give your plugin a try instead of coding it myself. But since it’s not yet possible, I was wondering if there is a ETA for this feature, so I can decide wether or not I’m going to script it myself… Thanks.

    I am running into the exact same issue here. I’ve tied it down to IE11.
    No problems in Edge or Firefox.

    Looks like the conflict appears, on my end, when using Themeco’s Pro theme.

    Do you have a bit more details on your solution?

    Thread Starter dhunink

    (@dhunink)

    Hi David,

    that works like a charm, thanks for the tip!

    Thread Starter dhunink

    (@dhunink)

    Hi!
    Just updated to version 2.1.4. There are still warnings…
    No cache in place.
    The notices appear to regard different lines though.

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\AdminOutputControllerTrait define the same property ($wordpress) in the composition of UserAccessManager\Controller\Frontend\PostController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/PostController.php on line 538

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\AdminOutputControllerTrait define the same property ($wordpressConfig) in the composition of UserAccessManager\Controller\Frontend\PostController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/PostController.php on line 538

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\LoginControllerTrait define the same property ($wordpress) in the composition of UserAccessManager\Controller\Frontend\ShortCodeController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/ShortCodeController.php on line 137

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\LoginControllerTrait define the same property ($php) in the composition of UserAccessManager\Controller\Frontend\ShortCodeController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/ShortCodeController.php on line 137

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\LoginControllerTrait define the same property ($wordpressConfig) in the composition of UserAccessManager\Controller\Frontend\ShortCodeController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/ShortCodeController.php on line 137

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\LoginControllerTrait define the same property ($template) in the composition of UserAccessManager\Controller\Frontend\ShortCodeController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/ShortCodeController.php on line 137

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\AdminOutputControllerTrait define the same property ($wordpress) in the composition of UserAccessManager\Controller\Frontend\TermController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/TermController.php on line 380

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\AdminOutputControllerTrait define the same property ($wordpressConfig) in the composition of UserAccessManager\Controller\Frontend\TermController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/TermController.php on line 380

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\LoginControllerTrait define the same property ($wordpress) in the composition of UserAccessManager\Controller\Frontend\RedirectController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/RedirectController.php on line 415

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\LoginControllerTrait define the same property ($php) in the composition of UserAccessManager\Controller\Frontend\RedirectController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/RedirectController.php on line 415

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\LoginControllerTrait define the same property ($wordpressConfig) in the composition of UserAccessManager\Controller\Frontend\RedirectController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/RedirectController.php on line 415

    Strict Standards: UserAccessManager\Controller\Controller and UserAccessManager\Controller\Frontend\LoginControllerTrait define the same property ($template) in the composition of UserAccessManager\Controller\Frontend\RedirectController. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in /home/users/topogftp/staging.topografieindeklas.nl/wp-content/plugins/user-access-manager/src/Controller/Frontend/RedirectController.php on line 415

    Thread Starter dhunink

    (@dhunink)

    Hi Martha,

    you should have created a separated topic for this, your questions is absolutely off-topic.
    Having that said: load the website and check your console (for example: use FireBug in Firefox). You have some huge issues with your minify plugin. Disable that plugin and recheck.

    Thread Starter dhunink

    (@dhunink)

    Hi,
    thanks, that will work.
    But is this kind of a bug that will be fixed, or how should I handle this modification when updating the plugin in the future?

    Nope, and believe me: I’ve tried.
    Sadly the team of W3 Total Cache is not responding on any of the questions regarding this issue..

    Found any solution?

    I’ve used this plugin with SSL enabled before. Can your share any more details about your setup? What made you conclude that the plugin isn’t SSL compatible?

    Thread Starter dhunink

    (@dhunink)

    I tried this way:

    wp_register_script('arcgis-api-js', '//js.arcgis.com/3.12/', array('jquery', 'jquery-ui-core'), NULL, false);

    Unfortunately without succes

    Thread Starter dhunink

    (@dhunink)

    Finally fixed it, although I’m still wondering why this was needed to be fixed with WP 4.1, wile it worked without this fix in WP 4.0

    Turned out that the problem was in timing. WordPress is loading jQuery UI in the footer (which is excellent, off course). Loading any JS file that uses the DoJo loader BEFORE the jQuery UI script tags, breaks it.

    So I ended up with a solution that forces any DoJo related JS file in the footer:

    wp_register_script('arcgis-api-js', $serverProtocol.'//js.arcgis.com/3.12/', array('jquery'), NULL, true);
    wp_register_script('page_provincies_map-js', $scriptdir.'/js/tpgrf_page_provincies_map.js', array('arcgis-api-js'), NULL, true);
    
    wp_enqueue_script('arcgis-api-js');
    wp_enqueue_script('page_provincies_map-js');

Viewing 15 replies - 1 through 15 (of 82 total)