tmuikku

Hi, the issues is also with Matomo standalone installation, auth error in logs makes fail2ban to ban clients, not fun. Please fix it, make sure no such error happens.

Hi,

do you have lots of products? Older version of the plugin fetched all products from database, looped them through and collected all custom fields to make filter dropdown, which is silly. They have now added possibility to override the function so that you can fix the issue without hacking the plugin code.

Here, add this to your theme functions.php to override problematic function. Edit to your use case if needed.

function woosea_get_meta_keys_for_post_type( $post_type, $sample_size = 'modified' ) {
    $meta_keys = array();

    $add_woosea_basic = get_option ('add_woosea_basic');
    if($add_woosea_basic == "yes"){
            $posts     = get_posts( array( 'post_type' => $post_type, 'limit' => $sample_size ) );
    } else {
/*
This is the silly line, replace with something more intelligent 
like limiting the numberposts, 
or selectively fetch products that provide all necessary options you need.
-T
*/
//                             $posts     = get_posts( array( 'post_type' => $post_type, 'numberposts' => -1 ) );
            $posts     = get_posts( array( 'post_type' => $post_type, 'numberposts' => 10 ) );
    }

    foreach ( $posts as $post ) {
            $post_meta_keys = get_post_custom_keys( $post->ID );
            $meta_keys      = array_merge( $meta_keys, $post_meta_keys );
    }

    // Use array_unique to remove duplicate meta_keys that we received from all posts
    // Use array_values to reset the index of the array
        return array_values( array_unique( $meta_keys ) );
}

Hi,
sent diagnostics to you earlier today, hope it helps.

Hi,
no errors on MySQL or PHP error logs. SHOW ENGINE INNODB STATUS \G is not listing related deadlocks either.

Hi! thanks, tried to find this thread the other day but didn’t ??

Still happens. Optimized tables. wfconfig table is only 257 rows and 1.4Mb in size.

On most of HTTP requests these wfconfig related queries are the only one that are marked as slow queries. Which is kind of weird since otherwise got huge database, it is a woocommerce site with post meta table with 1.6million rows for example.

Anyway, not a huge problem, you can mark this resolved. If you guys got time benchmark this thing someday and if you find ways to optimize, please do ??

• This reply was modified 6 years, 5 months ago by tmuikku.

Contact form sent. Thanks

See https://core.trac.www.ads-software.com/ticket/41335
You should remove IF NOT EXIST from the migrations that use dbDelta().

Alright here is alternative way to add the hl URL argument to recaptcha api script url.
Use WordPress script_loader_src filter which is in WP_Scripts::do_item() method.

This way you are not dependent if WPCF plugin updates unless they change the script handle from google-recaptcha to something else. You could do additional checks to the script $src or if this was a script added by WPCF7 or what ever.
This is a simple example, put into your theme functions.php:

function mytheme_wpcf7_recaptcha_set_language($src, $handle) {
    
    if ('google-recaptcha' == $handle) {
        $current_language = 'de'; 
        $src = add_query_arg('hl', $current_language, $src);
    }
 
    return $src;
}
add_filter( 'script_loader_src', 'mytheme_wpcf7_recaptcha_set_language', 1, 2 );

Supported language codes here https://developers.google.com/recaptcha/docs/language

I’ve got also need to set the language per site language (multilanguage site).

Please add WordPress filter for reCAPTCHA api arguments.
Deregistering and registering the script again with custom argumets does the job but leaves more work to maintain a site.

Thanks

Cool! I updated another site, from 6.3.2 to 6.3.4 today. Same thing happened.
ips.php file got emptied out on the update or some procedure after the update.

Here is ls few seconds before update and few seconds after update.

# ls -la wp-content/wflogs/
drwxrwxr-x 2 client apache 4096 Mar 17 07:02 .
drwxr-xr-x 14 client apache 4096 Feb 22 09:02 ..
-rw-rw—- 1 client apache 40083 Mar 15 09:24 attack-data.php
-rw-rw—- 1 client apache 425163 Mar 17 07:02 config.php
-rw-rw-r– 1 client apache 133 Jan 25 17:02 .htaccess
-rw-rw—- 1 client apache 691 Mar 15 09:22 ips.php
-rw-rw-r– 1 client apache 87671 Mar 15 17:05 rules.php
-rw-rw—- 1 client apache 39141 Mar 15 17:05 wafRules.rules
# ls -la wp-content/wflogs/
drwxrwxr-x 2 client apache 4096 Mar 17 07:18 .
drwxr-xr-x 14 client apache 4096 Feb 22 09:02 ..
-rw-rw—- 1 client apache 40083 Mar 15 09:24 attack-data.php
-rw-rw—- 1 client apache 425247 Mar 17 07:18 config.php
-rw-rw-r– 1 client apache 133 Jan 25 17:02 .htaccess
-rw-rw—- 1 client apache 51 Mar 17 07:18 ips.php
-rw-rw-r– 1 client apache 87671 Mar 15 17:05 rules.php
-rw-rw—- 1 client apache 39141 Mar 15 17:05 wafRules.rules

Hi,
ownership is the same as with other files in the folder and throught the WP installation. Permissions -rw-rw—-, like the config.php in the wflogs folder.
Filesize is 51 bytes it contains only the <?php exit(‘Access denied’); __halt_compiler(); ?> line.

I checked a backup before the plugin update and the ips.php file is 2971 bytes and has data in it after the PHP line. Permissions and ownership in the backup file are the same as with current production file.

This is a self hosted server. The issue appeared when the plugin was updated to version 6.3.3 via WP dashboard, just like many times before ??

Hi,

hmm, the problem persists. Only logged in users trigger the warning.
Deleting ips.php file didn’t help. The file is only one line.

Any ideas? It is not a serious problem, I could do fresh install of the plugin. There is @ in the code to suppress warnings on the unpack() function call but I’ve got custom error handler to send me mail on all errors that shows it. This is first time I see the error (WF 6.3.3).

Hi,
seems like the problem fixed it self, no warnings in the log files anymore.

Thanks!

Ooops indeed :S
For a site I’m maintaining it seems to be line 1755 in class/UserAccessManager.class.php that causes the issue. There might be other causes as well, haven’t had time to check all out yet.
$aTermPosts = get_posts($aArgs);

One could comment out line ~338 in user-access-manager.php

...
// add_filter('get_terms', array($oUserAccessManager, 'showTerms'), 10, 2);
...

Hi,

Will do, I’m sorry wasting your time. I’m in a hurry with a project and need to evaluate plugins to use and not to use, fast.

Thanks for your support.