Forum Replies Created

Viewing 13 replies - 16 through 28 (of 28 total)
  • Thread Starter Hlsg

    (@hlsg)

    Hey, thanks for the reply.
    I’m adopting your plugin for the frist time, so what I’m actually interested in is testing Wordfence itself on my local server. So I don’t actualy need this functionality thoroughly integrated in it, I would just like to know what to edit in your code in order to disable it without compromising other functionality.
    I’m guessing I need to commet out some functions, right?
    Thanks!

    Invisible reCaptcha for WordPress doesn’t properly work with TML, as it’s completly ineffective if you disable JS. That means that there’s no server side validation, so bots will just go through painlesly.

    Hello,

    Your information on teh new crawler is a bit cryptic at best. I presume this is what it handles. My main concearn is that i woudl like to access the actual sitemap used to see if it is crawling what it’s supposed to.
    Also, my questions from an abose post stand:
    – will it be sitemap based and, if so, will it be able to parse sitemap indexes that contain partial XML sitemap themselves?
    – will it prime the cache immediatly after purging regardless of server load or will it be opportunistic?

    I gusee i still wish i could use my own sitemap.

    Thnak you!

    Thanks for teh reply. No inconvenince. Just wanted to confirm that you didn’t just miss it in the changelog. So we should expect this in 1.0.16?

    Hello,

    Has this been pushed to a later version than 1.0.15?

    Thanks!

    Hello!

    I am very interested in this aswell.
    A couple of questions:
    – do you have an approximate ETA on this?
    – will it be sitemap based and, if so, will it be able to parse sitemap indexes that contain partial XML sitemap themselves?
    – will it prime teh cache immediatly after purging regardless of server load or will it be opportunistic?

    Thanks!

    +1
    It would seem to be a general bug with 0.9.1
    I presume we’ll seee an update soon as it would seem to be affecting all users(presumably, since i’ve tested extensively on different development stacks and WP installs).

    Thread Starter Hlsg

    (@hlsg)

    Actually, i just figured it out. The barebones theme i started with came with a sidebar defininition, which i removed and moved on. Now, i reactivated that definition and, the meta widget along with the stadard WP widgets search and whatnot were added to it. Removed meta and it’s all good.
    I guess is_active_widget checks only if a widget is added to a sidebar and returns true even if said sidebar is no longer defined or active.

    I’m sorry for taking up your time for no good reason and thank you for this always useful plugin!

    Thread Starter Hlsg

    (@hlsg)

    Excellent. Thank you!

    Hlsg

    (@hlsg)

    I’m interested in this too.

    Hello TC.K
    I’ve set the correction you suggested above for multiple select, but leaving a multiple select on the default option always returns no results. Seems to be because of uwpqsftaxoall becoming an array.

    Here are prints on the “taxo” get variables with normal and multi select on just the first:

    Array ( [0] => Array ( [name] => zona [opt] => 1 [term] => Array ( [0] => uwpqsftaxoall ) ) [1] => Array ( [name] => invecinare [opt] => 1 [term] => uwpqsftaxoall ) [2] => Array ( [name] => tip-de-proprietate [opt] => 1 [term] => uwpqsftaxoall ) [3] => Array ( [name] => facilitate [opt] => 1 [term] => animale ) )

    this one has the first element as a multi select and returns no results

    Array ( [0] => Array ( [name] => zona [opt] => 1 [term] => uwpqsftaxoall ) [1] => Array ( [name] => invecinare [opt] => 1 [term] => uwpqsftaxoall ) [2] => Array ( [name] => tip-de-proprietate [opt] => 1 [term] => uwpqsftaxoall ) [3] => Array ( [name] => facilitate [opt] => 1 [term] => animale ) )

    this one is with all selects and its fine.

    the same stuff is selected in both cases.

    Thanks!

    Nevermind, its in the cart template.. Why, woocommerce, why? :))

    I’ve encountered this aswell and i find the above mentioned solutions lacking.
    First add ‘woocommerce’ as a class to all the pages of your site that woocommerce does not recognise as its own to ensure that the notices are styled consistently wherever they appear by adding this to your functions.php:

    add_filter('body_class', 'append_woo_classes');
    function append_woo_classes($classes){
    if ( ! is_woocommerce()) {
    $classes[] = 'woocommerce woomanual';
    };
    return $classes;
    };

    The “woomanual” class is so we know the class was added manually just in case we need to differentiate from woocommerces native pages.

    Second, either add:

    <?php wc_print_notices(); ?>

    to your templates or somehow hook the function to the beginning of your content and unhook the original before shop and before single product. It will still execute twice before the cart, but that will not be and issue as the first execution clears the queue. Something like this in functions.php:

    remove_action( 'woocommerce_before_shop_loop', 'wc_print_notices', 10 );
    remove_action( 'woocommerce_before_single_product', 'wc_print_notices', 10 );
    add_action( 'YOUR_HOOK_HERE', 'wc_print_notices', 10 );

    Does anybody know how to unhook wc_print_notices from the cart page aswell?

Viewing 13 replies - 16 through 28 (of 28 total)