Thanks for taking a look, I have created a staging site at hidden link, I am just waiting for the IT team to point the DNS. Unfortunately, we can't test this on the root domain as this would require us installing WPML on their live ecommerce website which is very busy so that isn't an option for us.
Here are few lines from the debug log
[02-Dec-2025 14:58:42 UTC] WordPress database error Table 'dbgggjnw4cggj5.wp_actionscheduler_logs' doesn't exist for query SHOW FULL COLUMNS FROM `wp_actionscheduler_logs` made by do_action_ref_array('action_scheduler_run_queue'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->run, ActionScheduler_QueueRunner->do_batch, ActionScheduler_Abstract_QueueRunner->process_action, ActionScheduler_Abstract_QueueRunner->schedule_next_instance, ActionScheduler_ActionFactory->repeat, ActionScheduler_ActionFactory->store, ActionScheduler_HybridStore->save_action, ActionScheduler_DBStoreMigrator->save_action, ActionScheduler_DBStore->save_action, ActionScheduler_DBStore->save_action_to_db, do_action('action_scheduler_stored_action'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_Logger->log_stored_action, ActionScheduler_DBLogger->log
[02-Dec-2025 14:58:55 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
megamenu-pro
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the
init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/customer/www/godminster.com/public_html/global/wp-includes/functions.php on line 6121
[02-Dec-2025 14:58:55 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
acf
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the
init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/customer/www/godminster.com/public_html/global/wp-includes/functions.php on line 6121
This from the server error log but it doesn't specify whether this would be from the main site or the sub site
2025-12-02 12:27:40 UTC [nginx][error] 64143#0: *4768444 openat() "/home/u2139-4guvgwq86pu8/www/godminster.com/public_html/.well-known/passkey-endpoints" failed (2: No such file or directory), client: 104.28.86.128, server: godminster.com, request: "GET /.well-known/passkey-endpoints HTTP/2.0", host: "godminster.com"
2025-12-02 11:57:04 UTC [nginx][error] 36992#0: *4746285 openat() "/home/u2139-4guvgwq86pu8/www/godminster.com/public_html/.well-known/passkey-endpoints" failed (2: No such file or directory), client: 104.28.40.85, server: godminster.com, request: "GET /.well-known/passkey-endpoints HTTP/2.0", host: "godminster.com"
2025-12-02 11:43:03 UTC [nginx][error] 31702#0: *4736691 directory index of "/home/u2139-4guvgwq86pu8/www/godminster.com/public_html/.well-known/acme-challenge/" is forbidden, client: 4.230.41.104, server: godminster.com, request: "GET /.well-known/acme-challenge/ HTTP/1.1", host: "godminster.com", referrer: "hidden link"
2025-12-02 10:05:10 UTC [nginx][error] 31212#0: *4663617 openat() "/home/u2139-4guvgwq86pu8/www/godminster.com/public_html/.well-known/passkey-endpoints" failed (2: No such file or directory), client: 104.28.40.161, server: godminster.com, request: "GET /.well-known/passkey-endpoints HTTP/2.0", host: "godminster.com"
2025-12-02 06:30:35 UTC [nginx][error] 18745#0: *4520665 openat() "/home/u2139-4guvgwq86pu8/www/godminster.com/public_html/.well-known/passkey-endpoints" failed (2: No such file or directory), client: 104.28.86.125, server: godminster.com, request: "GET /.well-known/passkey-endpoints HTTP/2.0", host: "godminster.com"
2025-12-01 08:49:40 UTC [apache][authz_core:error] [pid 56826] [client 185.45.224.74:12136] AH01630: client denied by server configuration: /home/customer/www/godminster.com/public_html/wp-content/uploads/2023/04/index.php
---
If it does appear to be a conflict with the live site, would you maybe recommend us loading the website on a sub-domain instead and remapping the URLs? Our other option is to use a fresh domain but that then changes the whole SEO strategy.
I sorted out a mismatch of the domain URL with www
I have tested the site with the WPML plugin disabled and I can create a new page and publish. Unfortunately when I activate the WPML plugins we just hit the same issue as before so there must be something related to WPML that is causing this or a conflict somewhere.
I’ve identified the issue and have already escalated it. I was not able to reproduce the problem on my local environment. It appears to be related to the fact that your site is running in a subdirectory and the option “Use directory for default language” is enabled. This combination seems to be causing the issue.
If you temporarily disable the “Use directory for default language” option from WPML > Languages, everything works correctly.
I’ve forwarded this to our second-tier team for further investigation and guidance. I’ll update you as soon as I have more information—this may take a day or two but we will do our best to be quicker, since I know this is a bit showstopper for your website.
I look forward to your team's feedback, I'm going to be travelling overseas tomorrow so won't be able to check the ticket again until the weekend at the earliest.
I will share with you as soon as I have some feedback, in the meantime if this is a workable solution for you, you can disable option Use directory for default language and continue like that, until we have a solution.
That's great you've got it working, I've just re-enabled the theme and plugins on the staging version and it seems to be OK now. Can I just ask what i need to do on the godminster.com/global site? I've already got a page called 'Global', I need to set this as the root page but I can't seem to set that. Would you be able to take a look to see if we can use that, if not I guess we can start with an empty page again.
There is no way to select the root page, but you can delete your current Global page in both languages, and then from WPML > Languages click on Create a root page and create new one.
Let me know how it goes and if anything else I can do to help.
I've managed to set the root page but I'm still having problems publishing. It seems that I can now save changes to my existing pages in the default language but not the Swedish pages. Could you take a look to see if I've missed anything?
Note this is on hidden link
Thanks
Andy
PS - I'm +10 hours in Australia (from UK) so maybe a delay in replying
Very weird situation, I have checked and I could see it works fine on staging site, then after checking back and forth between production and staging, it started happening again on staging site, so I am not really sure what is the cause. I still suspect it might be something related to server / firewall side.
I will check now again with our 2nd tier, so they can advise further, and then I will get back to you.
our 2nd tier team checked further, as same as I, they are not experiencing any problems on their test setup.
While comparing your site with test environment, they noticed they cannot replicate your language setup — they’re not sure how it was created.
For example, your English language is set with the code “us”, but it still uses the standard locale en_US. If we try to reproduce this configuration, it gets rejected because the default locale en_US is already in use, so it can not be saved. Also looks like you are using a custom language, but it doesn’t show the little X (delete) icon that regular custom languages have. Image attached from my side.
Can you please share more info on how this language setup was originally created? Did you create custom language during setup or later, or maybe altered them in database?
