Slow Submissions
This topic contains 21 replies, has 3 voices, and was last updated by Alex Rollin 6 years, 1 month ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
September 14, 2019 at 1:43 pm #508196
Thanks Kiran!
I got this email recently, does this have anything to do with this issue or is it something that at least needs to be addressed?
Howdy!
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, GeoDirectory Pricing Manager.
First, visit your website (https://veganlinked.com/) and check for any visible issues. Next, visit the page where the error was caught (https://veganlinked.com/wp-admin/admin-ajax.php) and check for any visible issues.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.
To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
Error Details
=============
An error of type E_PARSE was caused in line 674 of the file /home/veganlinked/public_html/wp-content/plugins/geodir_payment_manager/includes/carts/class-geodir-pricing-cart-invoicing.php. Error message: syntax error, unexpected ”status’ (T_ENCAPSED_AND_WHITESPACE), expecting ‘)’September 14, 2019 at 1:52 pm #508198As for the issue with slow submissions potentially being due to the emails, I just contacted the hosting provider regarding that.
I’m curious though, couldn’t all of the submissions happen first before the emails so the end user doesn’t have to wait? This seems like it would really speed things up.
I think you’re right about the submissions being slow because of the email because the staging site works perfect with email notifications disabled.
September 16, 2019 at 1:32 pm #508416This reply has been marked as private.September 16, 2019 at 2:34 pm #508427Today the hosting provider said this, is this something that can help resolve this?
Hi Jeff,
Thank you for reaching out. I too ran some tests and found it to be about 6-10 seconds depending on the connection accessing it via the website, but running it via command line was instant.
Test via apache: Test email sentTotal Execution Time: 0.10310674905777 Mins
Test via SSH: Test email sent<b>Total Execution Time:</b> 0.00089786450068156 Mins
It is to be expected that the server is going to take a bit longer to process via HTTP then it would via SSH. What happens if you try switching your mail modules to use SMTP in the code base instead of using the phpmail() functionality? Does your script offer this? I know the likes of contactform7 etc offer the ability to send via both. I would be very interested in seeing the difference between the two.September 16, 2019 at 5:51 pm #508476Yes, SMTP is better than server email in most cases. See also:
https://wpgeodirectory.com/support/topic/automatic-messages-went-into-spam-folder/#post-428048September 17, 2019 at 3:19 am #508550This reply has been marked as private.September 17, 2019 at 11:59 am #508609He is saying you should use an SMTP plugin or an API to send email. You can fix that, yes. We say the same thing here:
https://wpgeodirectory.com/docs-v2/integrations/email/#smtp -
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket