earthways
Forum Replies Created
-
This issue is resolved. An error in the server settings caused the issue.
Thanks for your help.Indeed, these are the issues that are left unresolved. The subject of the ticket should be edited to delete ‘Invalid user ID’
The URL they use to register is the one I gave above. The home page or /register. It is happening with all levels and with the GDPR data request as well. It is also happening with the emails reporting activity on the website to peepso users, such as messages being send. Sometimes these are send, sometimes they are not. I am trying out some things to solve this issue. A pattern there is not clear to me. The clear pattern is that the registration emails are never sending and the GDPR requests are not being executed by Cron as they should be. The emails are being send when I execute Cron manually, but the GDPR requests are not able to be executed manually.
Payment gateway I am using is Stripe. Orders are showing up well. They are showing up well in the dashboard of peepso
Indeed the REST EPI.
The URL is this one: ( I think to read in the error report on the wordpress health report )
xxxxxxxxx are used to disguise email and identifiable links for safety reasons.homepageURL/wp-json/wp/v2/types/post?context=edit (port 443)
These are the plugins that are active:
Advanced iFrame Version 2020.9 by Michael Dempfle | Auto-updates disabled
ImageMagick Engine Version 1.6.5 by Orangelab | Auto-updates disabled
xxxxxxxxxxxxxxxxsecurity plugin that I do not wish to publicisexxxxxxxx
Mailchimp for WooCommerce Version 2.5.0 by Mailchimp | Auto-updates disabled
myCred Version 2.0.1 by myCred | Auto-updates disabled
Paid Memberships Pro Version 2.5.2 by Stranger Studios | Auto-updates disabled
Paid Memberships Pro – Email Templates Add On (.org) Version 0.8.1 by Paid Memberships Pro | Auto-updates disabled
Paid Memberships Pro – Mailchimp Add On Version 2.3.1 by Stranger Studios | Auto-updates disabled
Paid Memberships Pro – WooCommerce Add On Version 1.7 by Paid Memberships Pro | Auto-updates disabled
PeepSo Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Core: Audio & Video Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Core: Chat Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Core: Friends Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Core: Groups Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Core: Photos Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Extras: VIP Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Integrations: myCRED Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Monetization: Paid Memberships Pro Version 3.1.2.0 by PeepSo | Auto-updates disabled
PeepSo Monetization: WooCommerce Version 3.1.2.0 by PeepSo | Auto-updates disabled
xxxxxxxxxxxxsecurity plugin that I do not wish to publicize xxxxxxxxxxx
WooCommerce Version 4.8.0 by Automattic | Auto-updates disabled
WooCommerce Product Vendors Version 2.1.45 by WooCommerce | Auto-updates disabled
xxxxxxxxxxxxsecurity plugin that I do not wish to publicize xxxxxxxxxxx
WP Crontrol Version 1.9.0 by John Blackbourn & crontributors | Auto-updates disabled`
I update the symptoms list, as some are resolved and are not linked.
The symptoms are these:
– Some registration emails are not being send
– Cron job issues
– I can’t upgrade to php.7.4
– The rest EPA throws an error 404.
– the site could not complete a loopback request.Hi, there, that issue is not related no and has been resolved. Thanks for your help. I will wait for the update and venture back if the original hasn’t been resolved.
I have the same issue as @crpeng above. I followed your recommendations regarding loopbackrequest issues and the issue persists.
Another error which might be linked. This error manifest itself When a new user tries to log in before the administrator has approved the new account. This user will never be able to log in again on the same device. This is not caused by any security plugins I use. It happens when these are disabled too or when IP is whitelisted on these. Refreshing browser and cookies does not solve the issue.
I need to create a new user and transfer the data to that one to circumvent the problem.Got it sorted. No worries
Forum: Plugins
In reply to: [Contact Form 7] Selectable Recipient with Pipes and syntax error fieldThanks Sometimesisurf,
Missing the “*” on the [select*… seems to have been my issue.
that was indeed the issue. The instructions page should be updated, really.