Front End Pagebuilder (sim To #203068)
blue_Shift
I saw in the above referenced item that the way SEF urls are configured can cause this problem. But based the answer, my setting appear to be correct. Strict routing in my setup was off in the plugin, SEF urls on in global configuration but I am getting 404 on front end edit. Should the plugin be on, strict routing off? Hidden field for login.
Credentials and links are in the hidden field.
Ziaul Kabir
Accepted AnswerHello,
Thanks for reaching out to us.
Please- re-check your administartor url.
It's shows 404.
Thanks
blue_Shift
Accepted AnswerHad the question mark at the wrong end. The administrator link has been updated (corrected)
Ziaul Kabir
Accepted AnswerI see that the new pages are working correctly in the front-end editor. I have now enabled all features of the SEF plugin.
It looks like there may be some caching on your hosting environment. Please clear the cache there, as well as on your Joomla site. Then check the site again using incognito mode or a different browser.
Let me know once you've done this and share any updates.
blue_Shift
Accepted AnswerFLASH. JUST IN. Front end edit started working.
-- Deprecated --
I had followed these steps. Note the interesting log entry.
- Cleared Joomla cache
- Cleared browser caches (Chrome, Firefox)
- Cleared PHP opcache (which was disabled anyway) in Plesk
- Flushed DNS cache on my system
Result was [briefly] still a 404 in both normal and incognito modes, Chrome and Frefox both.
EDIT - the front end edit is [was] fetching the 404 page (GET), not throwing a 404 error. (Image)
Ziaul Kabir
Accepted AnswerI took a backup of your site and ran it on my local PC. I can confirm that the front-end editor is working correctly for this page (see attached screenshot).
It appears that the issue is likely related to caching. Please try the following steps:
- Clear your cPanel cache.
- Clear your Joomla cache.
- Clear your browser cache.
After performing these steps, the editor should function properly. Or you may check from different isp or pc.
Best regards,
blue_Shift
Accepted AnswerI updated the information in the reply above to clarify success, as you had given this information in the accepted answer. After I followed it, there was a five minute delay before front end edit began working, so clearing all these caches seems to have forced something else to update - an ISP cache? the database? - resulting in a short period of latency. But your answer did indeed work.