ttoaster

Hi Peter,

Yes I am aware of that option, but it doesn’t do what I need, it only blocks matching URLs without the domain name that the hacker tries to access, e.g.

You would currently block /test.php or */test.* but not
https://fake.siteurl.com/test.php (such as a staging or development full URL which should not be used to access the real site). The full URL is being captured in Wordfence live traffic logs, so it should be easy to add this functionality to the existing UI?

Hope this makes sense?

Regards,
Martin

Thank you for the clarification, it might be an idea to add this information to the FAQ and product description…

Thank you for the information.

Any plans to add HPOS support?

OK, it works, but only if you use HTML markup for the space, e.g.  

Right, I see that you have now released 7.0.4, so I updated from 7.0.3 to 7.0.4 on my dev site and no critical error email. I will try it on my live site.

BTW the plugin was already set to “Do not delete anything”

Update: Just upgraded my live site from 6.11.8 to 7.0.4 and no critical error email…

• This reply was modified 6 months, 3 weeks ago by ttoaster.
• This reply was modified 6 months, 3 weeks ago by ttoaster.

Hi,

No, I still get a critical error email when upgrading to 7.0.3, see below:

WordPress version 6.5.2
Active theme: Vogue (version 10.9.2)
Current plugin: Site Reviews (version 7.0.3)
PHP version 8.0.30

Error Details
=============
An error of type E_ERROR was caused in line 261 of the file /home/shop/wp-content/plugins/site-reviews/plugin/Modules/Console.php. Error message: Uncaught Error: Call to undefined method GeminiLabs\SiteReviews\Helpers\Str::hash() in /home/omgcyb5/shop/wp-content/plugins/site-reviews/plugin/Modules/Console.php:261
Stack trace:
#0 /home/shop/wp-content/plugins/site-reviews/plugin/Modules/Console.php(39): GeminiLabs\SiteReviews\Modules\Console->setLogFile()
#1 [internal function]: GeminiLabs\SiteReviews\Modules\Console->__construct()
#2 /home/shop/wp-content/plugins/site-reviews/plugin/Container.php(110): ReflectionClass->newInstanceArgs(Array)
#3 /home/shop/wp-content/plugins/site-reviews/plugin/Container.php(219): GeminiLabs\SiteReviews\Container->construct('GeminiLabs\\Site...')
#4 [internal function]: GeminiLabs\SiteReviews\Container->GeminiLabs\SiteReviews\{closure}()
#5 /home/omgcyb5/shop/wp-content/plugins/site-reviews/plugin/Helper.php(353): call_user_func(Object(Closure))
#6 /home/shop/wp-content/plugins/site-reviews/plugin/Helper.php(239): GeminiLabs\SiteReviews\Helper::runClosure(Object(Closure))
#7 /home/shop/wp-content/plugins/site-reviews/plugin/Container.php(220): GeminiLabs\SiteReviews\Helper::ifTrue(true, Object(Closure), Object(Closure))
#8 /home/shop/wp-content/plugins/site-reviews/plugin/Container.php(67): GeminiLabs\SiteReviews\Container->resolve('GeminiLabs\\Site...', Array)
#9 /home/shop/wp-content/plugins/site-reviews/helpers.php(63): GeminiLabs\SiteReviews\Container->make('GeminiLabs\\Site...', Array)
#10 /home/shop/wp-content/plugins/site-reviews/helpers.php(210): glsr('GeminiLabs\\Site...')
#11 /home/shop/wp-content/plugins/site-reviews/plugin/Controllers/MainController.php(77): glsr_log()
#12 /home/omgcyb5/shop/wp-includes/class-wp-hook.php(324): GeminiLabs\SiteReviews\Controllers\MainController->logOnce('update.php')
#13 /home/shop/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#14 /home/shop/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#15 /home/shop/wp-admin/includes/template.php(2222): do_action('admin_footer', 'update.php')
#16 /home/shop/wp-admin/update.php(53): iframe_footer()
#17 {main}
? thrown

As you still haven’t addressed the HPOS issue I have stopped using your plugin and deleted it. I’m not going to reward this type of bait and switch behaviour.

I did consider purchasing your plugin before this HPOS change, but you have now lost any chance of that happening.

It is a known issue that still hasn’t been resolved (more than 5 weeks have now passed), and bcrodua should know this; see this earlier thread on the same issue:

https://www.ads-software.com/support/topic/can-save-the-email-checkbox/

• This reply was modified 9 months, 1 week ago by ttoaster.

Yes, I guessed that was the case as the package was refreshed/updated about 15 minute after I posted here. I have since updated my sites to the latest (fixed) version, and all seems to be working.

Hi Darla,

No there are no Fatal Error Logs.

I’m not sharing my System Report output with you, as it is irrelevant; the issue did not occur before I upgraded to the latest version of Woocommerce.

Furthermore, I am seeing this on multiple sites, and I have already given you the details of what I believe is causing the issue… see my original posting.

Hi,

Thank you. That works pretty well, I did tweak it a bit for my own sites.

Hi Jarryd,

The issue is with 2.12.2 not 2.12.1….

The issue only appears when you manually add a new user, and then manually add a level to the new user. You can set the expiry then, but when you save the page/user and look at it again, the Expiry is set back to NO.

Update: Managed to fix it by changing the session type to WC Session from PHP Session (although 7.0.0 worked fine with PHP Session and Close Session ticked).

Hi Elliot,

That seems to have fixed the intermittent issue with the login button.

Any chance you can fix the issue I reported with the WPS Hide Login when the Change Password function is used via the Custom Account page in Woocommerce?

Many thanks!