gabez123

Also getting the same error as soon as I updated to the latest AIOS.

I was able to temporary fix it by adding the following to my wp-config.php
define(‘FS_METHOD’, ‘direct’);

This is the error: (blanked out the domain name)

Stack trace
E_WARNING: ftp_pwd() expects parameter 1 to be resource, null given
in ftp_pwd called at /var/www/vhosts/----/wp-admin/includes/class-wp-filesystem-ftpext.php (230)
in WP_Filesystem_FTPext::cwd called at /var/www/vhosts/----/wp-admin/includes/class-wp-filesystem-ftpext.php (453)
in WP_Filesystem_FTPext::is_dir called at /var/www/vhosts/----/wp-admin/includes/class-wp-filesystem-ftpext.php (422)
in WP_Filesystem_FTPext::exists called at /var/www/vhosts/----/wp-content/plugins/all-in-one-seo-pack/app/Common/Tools/BadBotBlocker.php (211)
in AIOSEO\Plugin\Common\Tools\BadBotBlocker::init called at /var/www/vhosts/----/wp-content/plugins/all-in-one-seo-pack/app/AIOSEO.php (308)
in AIOSEO\Plugin\AIOSEO::loadInit called at /var/www/vhosts/----/wp-includes/class-wp-hook.php (287)
in WP_Hook::apply_filters called at /var/www/vhosts/----/wp-includes/class-wp-hook.php (311)
in WP_Hook::do_action called at /var/www/vhosts/----/wp-includes/plugin.php (484)
in do_action called at /var/www/vhosts/----/wp-settings.php (557)
in require_once called at /var/www/vhosts/----/wp-config.php (120)
in require_once called at /var/www/vhosts/----/wp-load.php (37)
in require_once called at /var/www/vhosts/----/wp-blog-header.php (13)
in require called at /var/www/vhosts/----/index.php (17)

• This reply was modified 4 years, 2 months ago by gabez123.

Hi Joy,

The purpose is to help someone from trying to stop a bot from brute forcing the ajax url and trying to guess username/password combinatinations.

I did just figure this out however. Read up the details on how nonces work. Apparently they work for “2 ticks” meaning they expire in 24 hours, each “tick” being 12 hours. The interesting thing is that even though the nonce gets replaced for a new nonce every 12 hours, they are still valid for the full 24 hours. This means that at any one time, 2 different nonce are valid, not just the one.

So, long story short, this means that as long as I set the site cache to less than 12 hours, the nonce will always work, so problem solved.

@leadsoft thank you for the solution, but thats the almost identical solution that I have already implemented. It works well, but I was wondering if there was a better way of doing this.

@corrinarusso – I tried using rewrites but the problem seems to be that when I do a re-write for my specific custom post, it overwrites the re-write for standard posts and pages and they give a 404. It looks like wordpress queries the database for the custom type when there is a match in the rewrite instead of querying for pages/posts. I couldnt find a way to get the same rewrite rule to look for the custom post as well as for post and pages. The solution I have (same as the one provided by @leadsoft) seems to be the only way to bypass this (that I could find).

Do you have a specific solution that I might have missed?

• This reply was modified 4 years, 10 months ago by gabez123.
• This reply was modified 4 years, 10 months ago by gabez123.

Hi Saumuya,

I just tried the script and the jquery iframtracker script just doesnt seem to be triggered when we click on the adsense ad. I tried it through the plugin and i tried it directly and it just doesnt seem to work.

I tested the script on normal iframes and it works fine, but just doesnt seem to work with adsense codes. Could we be doing something wrong?