semoliner

Thanks Nickolas, the anti-spam dev has assisted me to resolve the issue – all good now! Thank you for your assistance.

• This reply was modified 8 months, 2 weeks ago by semoliner.

Thanks – this turned out to be caused by our anti-spam plugin. As we need that plugin, I suppose I need to contact their dev team to see what they suggest – or can you suggest a workaround?

OK thanks it’s no longer crashing. Can you please check again to confirm whether the admin url (ajax URL which also includes the customized admin) is now no longer exposed in the code?

Hi Nickolas,
Thanks – yes it’s the free version.
upload_max_filesize 1G
post_max_size 128M
max_execution_time 3000
max_input_time -1

• This reply was modified 8 months, 2 weeks ago by semoliner.

Hi, okay, hopefully this might help

[14-Mar-2024 08:15:56 UTC] PHP Deprecated: Return type of Google\Collection::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/soldonhold/soldonhold.com.au/wp-content/plugins/boldgrid-backup-premium/vendor/google/apiclient/src/Collection.php on line 14
[14-Mar-2024 08:15:56 UTC] PHP Deprecated: Return type of Google\Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/soldonhold/soldonhold.com.au/wp-content/plugins/boldgrid-backup-premium/vendor/google/apiclient/src/Collection.php on line 49
[14-Mar-2024 08:16:00 UTC] PHP Fatal error: Uncaught Error: Call to undefined function is_user_logged_in() in /home/soldonhold/soldonhold.com.au/wp-content/plugins/wp-hide-security-enhancer/modules/components/admin-login_php.php:161
Stack trace: 0 /home/soldonhold/soldonhold.com.au/wp-includes/class-wp-hook.php(324): WPH_module_admin_login_php->login_url(‘https://www.sol…’, ”, false) 1 /home/soldonhold/soldonhold.com.au/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘https://www.sol…’, Array) 2 /home/soldonhold/soldonhold.com.au/wp-includes/general-template.php(467): apply_filters(‘login_url’, ‘https://www.sol…’, ”, false) 3 /home/soldonhold/soldonhold.com.au/wp-content/plugins/security-malware-firewall/security-malware-firewall.php(567): wp_login_url() 4 /home/soldonhold/soldonhold.com.au/wp-content/plugins/security-malware-firewall/security-malware-firewall.php(206): spbc_firewall__check() 5 /home/soldonhold/soldonhold.com.au/wp-settings.php(473): include_once(‘/home/soldonhol…’) 6 /home/soldonhold/soldonhold.com.au/wp-config.php(115): require_once(‘/home/soldonhol…’) 7 /home/soldonhold/soldonhold.com.au/wp-load.php(50): require_once(‘/home/soldonhol…’) 8 /home/soldonhold/soldonhold.com.au/wp-blog-header.php(13): require_once(‘/home/soldonhol…’) 9 /home/soldonhold/soldonhold.com.au/index.php(17): require(‘/home/soldonhol…’) 10 {main}

thrown in /home/soldonhold/soldonhold.com.au/wp-content/plugins/wp-hide-security-enhancer/modules/components/admin-login_php.php on line 161
[14-Mar-2024 08:16:00 UTC] PHP Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/soldonhold/soldonhold.com.au/wp-includes/functions.php on line 6031
[14-Mar-2024 08:16:00 UTC] PHP Notice: Function is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/soldonhold/soldonhold.com.au/wp-includes/functions.php on line 6031
[14-Mar-2024 08:16:00 UTC] PHP Fatal error: Uncaught Error: Call to undefined function is_user_logged_in() in /home/soldonhold/soldonhold.com.au/wp-content/plugins/wp-hide-security-enhancer/modules/components/admin-login_php.php:161
Stack trace: 0 /home/soldonhold/soldonhold.com.au/wp-includes/class-wp-hook.php(324): WPH_module_admin_login_php->login_url(‘https://www.sol…’, ”, false) 1 /home/soldonhold/soldonhold.com.au/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘https://www.sol…’, Array) 2 /home/soldonhold/soldonhold.com.au/wp-includes/general-template.php(467): apply_filters(‘login_url’, ‘https://www.sol…’, ”, false) 3 /home/soldonhold/soldonhold.com.au/wp-content/plugins/security-malware-firewall/security-malware-firewall.php(567): wp_login_url() 4 /home/soldonhold/soldonhold.com.au/wp-content/plugins/security-malware-firewall/security-malware-firewall.php(206): spbc_firewall__check() 5 /home/soldonhold/soldonhold.com.au/wp-settings.php(473): include_once(‘/home/soldonhol…’) 6 /home/soldonhold/soldonhold.com.au/wp-config.php(115): require_once(‘/home/soldonhol…’) 7 /home/soldonhold/soldonhold.com.au/wp-load.php(50): require_once(‘/home/soldonhol…’) 8 /home/soldonhold/soldonhold.com.au/wp-blog-header.php(13): require_once(‘/home/soldonhol…’) 9 /home/soldonhold/soldonhold.com.au/index.php(17): require(‘/home/soldonhol…’) 10 {main}

thrown in /home/soldonhold/soldonhold.com.au/wp-content/plugins/wp-hide-security-enhancer/modules/components/admin-login_php.php on line 161
[14-Mar-2024 08:16:00 UTC] PHP Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/soldonhold/soldonhold.com.au/wp-includes/functions.php on line 6031
[14-Mar-2024 08:16:00 UTC] PHP Notice: Function is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/soldonhold/soldonhold.com.au/wp-includes/functions.php on line 6031

Hi, okay I updated to the new plugin version but immediately upon setting the new admin url stub, ‘There has been a critical error on this website’ was generated. I then renamed the plugin to fix this. I then completely uninstalled the plugin and downloaded/installed it again, but again the critical error occurred, this time immediately the plugin was activated.

Thanks Maya, that would be great. The site is soldonhold.com.au
The site has no users apart from myself, so there should be no login forms as far as I know, apart from the hidden login stub that I use to login to WP of course.

I came here because an attack searching for the admin account name was made, which should be impossible since the stub is an unguessable combination. Should we roll back to a previous version while waiting for the update? But I suppose it makes little effective difference, since the admin account name and password are also random characters.

I believe this was likely the issue. I tried 6 purchases in Test Mode, all using different email addresses, and they all went through as expected with the confirmation emails sent correctly. I’ll mark this as resolved and will continue to monitor over time. Thanks for your help!

Thanks. A couple of additional questions before I try out easy-wp-smtp:

1. I noticed that in the Additional Email Settings section, ‘Send Emails in Parallel’ is checked – could this be an issue?
2. During my testing I have been completing the Stripe payment form using one of the email addresses that’s specified in the plugin’s Notification Email Address settings – could that be the issue?

Hi, well I decided to do a couple of test purchases. In the first one (using AU test card no 4000000360000006) the emails didn’t get sent. In the second one (using US test card no 4242424242424242) just a few minutes later, the emails got sent. The log confirms same.

I doubt the test card numbers have anything to do with it, but just mentioning it for completeness. All of our actual purchasers use AU cards.

All of the orders are recorded correctly in the plugin’s Orders page, so we are not losing any sales from this; it just means sometimes I have to get the details from that page instead of via email. Not a huge hassle, but if you think of any other suggestions to try…

By the way, I noticed that the log’s time do not reflect either local time or server time. The times in the log are 5 hours ahead of server time. Not sure why.

• This reply was modified 1 year, 3 months ago by semoliner. Reason: extra info re log times

Here is where we’re up to now… I had our hosting provider move us back to the old server. Unfortunately this has not changed the intermittent logging of eg. ‘FAILURE: Can’t find product with ID: 6263’

It must be considered that for all I know, this may have been an issue from the start (18 months ago), and the only reason I wasn’t aware of it till now is that there was no reason to check the log till recently. If we assume this to be so, then there’s no reason to be concerned about it as it shouldn’t be affecting the operation of the payment processing.

With regard to whether the server move has fixed the issue of this thread (Send Emails to Seller After Purchase stopped working) since this was intermittent, the only way to know will be to continue to monitor. So that’s what I’ll do. I’ll report back here in the coming days, weeks or months…

OK, so I have reinstalled the plugin, and currently this is the entire contents of the log:
[07/23/2023 08:24:29 AM] – Stripe Payments debug log file

[07/24/2023 09:03:34 PM] – FAILURE: Can’t find product with ID: 6263
[07/25/2023 05:49:50 AM] – FAILURE: Can’t find product with ID: 6263
[07/25/2023 07:47:08 PM] – FAILURE: Can’t find product with ID: 6263
[07/25/2023 08:30:06 PM] – FAILURE: Can’t find product with ID: 6263
[07/25/2023 11:10:17 PM] – FAILURE: Can’t find product with ID: 6263
[07/26/2023 12:18:16 AM] – FAILURE: Can’t find product with ID: 6263

We don’t have a product with ID 6263. It seems to be fixated on that number, but previous to reinstallation, other IDs have included 626311, 626411, 63720, 11 and zero.

As I previously mentioned, as you can see from the time stamps, these occur at random times and never coincide with any payment form processing, so I doubt that this would have any bearing on whether the emails get sent or not, but it is very odd.

The two minor issues with the WARNING and the FAILURE in the log; and the main issue with the emails sometimes not sending, all only occur intermittently; ie. the plugin sometimes sends emails and sometimes does not.

So if we were to disable all other plugins and our Astra theme, and then test to see if the plugin behaves how it is supposed to, it may well behave how it is supposed to, but this would prove nothing without a very extended test period which is not possible on a live site.

With regard to:
WARNING: Stripe PHP library conflict! Another Stripe PHP SDK library is being used. Please disable plugin or theme that provides it as it can cause issues during payment process.
Library path: /home/khsorg/public_html/wp-content/plugins/wpforms-lite/vendor/stripe/stripe-php/lib/Stripe.php
It appears to be indicating a conflict between Accept Stripe Payments and WPForms Lite (which has its own Stripe payment functionality but which we have not enabled) but I think this is a red herring because looking at the log, the occurrence of this warning has no bearing on whether the emails get sent or not; ie. sometimes the warning appears and the emails still get sent.

As a test I have just renamed the folder /home/khsorg/public_html/wp-content/plugins/wpforms-lite/vendor/stripe to stripe_hold and will monitor the log to see whether this makes any difference.

With regard to, eg:
[07/05/2023 06:07:54 AM] – FAILURE: Can’t find product with ID: 6263
[07/05/2023 09:04:57 AM] – FAILURE: Can’t find product with ID: 0
[07/05/2023 09:05:02 AM] – FAILURE: Can’t find product with ID: 0
[07/05/2023 02:46:48 PM] – FAILURE: Can’t find product with ID: 6263
These occur at random times and never coincide with any payment form processing. So again, I don’t see how this can have any bearing on whether the emails get sent or not.

If I were to deactivate and delete the Accept Stripe Payments plugin as you suggest, and then reinstall it, would our products be lost?

• This reply was modified 1 year, 4 months ago by semoliner.

Hi,
This happened again today – the Stripe payment was processed normally but the log indicates that neither the seller nor the buyer emails were sent. Our anti-spam plugin indicates that the form was not blocked by it.
I think the only thing we discussed earlier that might be an issue is that our web host did move us to a different server a few weeks ago. If you think this may be the cause and is worth pursuing with them, what should I ask them about this issue?

EDIT
In case it’s relevant, I have noticed some warnings in the log, though they are not directly related to the sale in question. I’m seeing this several times in the log:
WARNING: Stripe PHP library conflict! Another Stripe PHP SDK library is being used. Please disable plugin or theme that provides it as it can cause issues during payment process.
Library path: /home/khsorg/public_html/wp-content/plugins/wpforms-lite/vendor/stripe/stripe-php/lib/Stripe.php

I’m also seeing this sort of thing a lot, relating to a non-existent product
[07/15/2023 11:09:35 AM] – FAILURE: Can’t find product with ID: 6263
[07/15/2023 02:54:19 PM] – FAILURE: Can’t find product with ID: 6263
[07/15/2023 02:54:22 PM] – FAILURE: Can’t find product with ID: 626311
[07/16/2023 05:09:29 AM] – FAILURE: Can’t find product with ID: 6263
[07/16/2023 05:21:25 AM] – FAILURE: Can’t find product with ID: 6263
[07/16/2023 05:22:42 AM] – FAILURE: Can’t find product with ID: 6263
[07/16/2023 05:26:30 AM] – FAILURE: Can’t find product with ID: 6263
[07/17/2023 03:24:20 AM] – FAILURE: Can’t find product with ID: 6263
[07/17/2023 03:42:03 AM] – FAILURE: Can’t find product with ID: 6263

• This reply was modified 1 year, 4 months ago by semoliner. Reason: Additional info