Background of the issue:
I'm the lead developer of LifterLMS, and we received a report that a user of WPML cannot access the Dashboard page or sub-pages. I'm trying to set things up with a couple of languages locally to test and I'm not able to access pages when using the `lang=es` query param, even when using the page ID in case there's some auto-translation that's happening (ie. ?p=18&lang=es). It's behaving differently on their staging site vs. locally with what looks like the same initial WPML settings (?lang= URL structure, etc).
Symptoms:
URLs result in a 404 error with the lang query param set. The menu disappears completely when adding ?lang=es on any page.
Questions:
Why do URLs result in a 404 error with the lang query param set?
Why does the menu disappear completely when adding ?lang=es on any page?
Thanks for the quick reply! I'm actually the lead developer, the support thread was started via the owner's account.
All jobs under WPML > Translation Management, "Translation Jobs" tab show as Completed. The ones I did send were using the "Publish without Review" option. Is there somewhere else to check for unpublished translations? I never did select that page for translation previously and didn't expect the page to become inaccessible if something isn't translated, or for the nav menu to disappear.
After choosing that page for translation and translating it, I can now go to /dashboard/?lang=es and it redirects to /cuadro-de-mandos/?lang=es.
I'm not sure what you mean by "see the ID in the structure"? The page didn't appear at all in the menu, but after translating it, it now appears when viewing with ?lang=es.
It sounds like the issue was resolved by updating the page and it's translation?
If yes, that is great as that would of have been the next step in debugging this type of behavior.
Translations are pulled from our ATE servers and this could of been happening due to a "stuck" translation which gets reset when you re translate or update.
Let me know your results, please.
The topic ‘[Closed] Unable to access pages’ is closed to new replies.