Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
Awesome! Can they please use bobby.k@onthegosystems.com
|
dougC-3
|
Thanks Bobby - I will keep you posted.
|
dougC-3
|
Hi Bobby,
I added you as a collaborator in Flywheel, you will be receiving an invitation from them soon. Please let me know if you need something else from us.
Fixing this problem is very important for us because the majority of our clients speak Chinese and we really need a bilingual website up and running as soon as possible.
Thank you very much for your help.
If you need anything else, feel free to call me at 214 854 8575.
|
Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
Thank you, I have now joined.
How can I gain access to the FTP? I currently don't see an option via the dashboard.
|
dougC-3
|
Hi Bobby,
The sFTP settings are pretty straightforward since you're at the FlyWheel level.
Here's the support doc that explains how to connect:
hidden link
|
dougC-3
|
Hi Bobby,
We received an email from WPML, please see below:
Howdy!
WordPress has 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, WPML Multilingual CMS.
First, visit your website (hidden link) and check for any visible issues. Next, visit the page where the error was caught (hidden link) 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.
hidden link
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.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.9.4
Active theme: HC2 Theme (version 0.1.0)
Current plugin: WPML Multilingual CMS (version 4.8.6)
PHP version 8.2.30
|
Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
Thank you, I am in!!
Ok...
1. I was able to resolve the issue that was keeping WPML deactivated.
I have deleted the WPML plugin and re installed the latest and stable version using a fresh version.
Previous installation was corrupted.
2. I can see now that WordPress is installed within a directory
org-hc2-capital/hc2-capital-primary
in this set up, it is not recommended to use Languages in directories.
We can leave it as is for now but if issues persist switching to a different format might be a solution. (will keep an eye on this)
I am now moving forward to the ATE error and will update shortly
|
dougC-3
|
Hi Bobby,
I'm so glad you were able to solve the problem about the plugin.
We don't want to have issues in the future because WordPress was installed within a directory.
Can we switch to a different format now? Is this something you can do or we need to ask the marketing agency?
Many Thanks.
|
dougC-3
|
Hi Bobby - Good morning, Do you have any updates?
Thanks.
|
Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
Good morning,
You can most likely keep it the way it is, if any issues were to arise they would have already 🙂
Changing the format is easy BUT it is going to change the URLs so best to avoid when possible.
Now regarding the ATE errors we have made progress and after some final tests I will update you as soon as possible.
|
Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
While we are testing, as a test would you mind logging in with this account
goodgiant
dev-email@flywheel.local
Does the issue persist?
|
dougC-3
|
Hi Bobby - I noticed all our posts (under POSTS) are gone, they were replaced with posts about casinos... Do you know why?
Do you think it would be easier if I just email you directly to bobby.k@onthegosystems.com so we can all be in the same page (the agency and you)?
Many Thanks.
|
dougC-3
|
What do you mean with ATE errors? How is this affecting the website?
About the casino posts, we suspect a bot/bad actor has pushed content into the site via one or more rogue admin accounts. To remedy, the rogue admins need removal, purge the erroneous posts, and whatever exploit was used to gain access need identification and closure.
Because this could impact WMPL's ability to access the site and continue troubleshooting their plugin, we recommend WPML finalize their work before the security issue is addressed.
I hope you can finish troubleshooting as soon as possible so we can address this security issue.
Many Thanks.
|
dougC-3
|
Hi Bobby,
Please note the SEO plugin Yoast is causing an error in the website. Feel free to deactivate, we won't be using this plugin.
See below from WordPress:
Howdy!
WordPress has 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, Yoast SEO.
First, visit your website (hidden link) and check for any visible issues. Next, visit the page where the error was caught (hidden link) 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.
hidden link
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.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.9.4
Active theme: HC2 Theme (version 0.1.0)
Current plugin: Yoast SEO (version 27.3)
PHP version 8.2.30
Error Details
=============
An error of type E_COMPILE_ERROR was caused in line 4 of the file /www/wp-content/plugins/wordpress-seo/src/integrations/admin/migration-error-integration.php. Error message: Namespace declaration statement has to be the very first statement or after any declare call in the script
|
Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
Hi Doug,
We've been able to identify the cause of the issue.
After thorough testing, we can confirm this is not related to WPML or WordPress.
The problem is happening at the hosting level (Flywheel).
Their servers are modifying the redirect URLs after they are generated, which breaks the authentication signature and causes the error you're seeing.
To get this resolved, you'll need to contact Flywheel support. I've put together the message below that you can send directly to them — it includes all the technical details their team will need to fix it.
Let me know once you've sent it and we can follow up from there.
---------------------------------------------
We've identified a server-level issue affecting redirect functionality on hc2capital.com.
Our developers ran an isolated test — a standalone PHP file issuing a plain 302 redirect with no WordPress or plugins involved. The test set this exact Location header:
hidden link
The curl response showed:
location: hidden link
The %2F in the path parameter is being decoded to / by the server before the response reaches the client.
The other encoded characters (%20, %26) are not being decoded — so this appears to be selective URL normalisation being applied to Location headers somewhere in your stack (likely Fastly based on the response headers).
This breaks URL authentication because the security signature is based on the exact redirect URL.
Any modification after signing invalidates it.
What we need:
please disable the decoding/normalisation of percent-encoded characters in Location headers for this site. Specifically, %2F must be passed through unchanged.
Full curl response for reference:
< HTTP/2 302
< location: <em><u>hidden link</u></em>
< x-fw-server: Flywheel/5.1.0
< x-fw-version: 5.0.0
< fastly-restarts: 1
< x-served-by: cache-iad-kiad7000071-IAD, cache-iad-kiad7000071-IAD
< via: 1.1 e87cc4d29c1d8030afdf5225cac7744c.cloudfront.net (CloudFront), 1.1 google
|
