-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frontend not works after updated to Craft CMS 3.3.20.1, but works when there is ?token query string in frontend URL #5475
Comments
Try clearing out your |
web.log |
It looks like there may be an issue with your MySQL connection, per the “MySQL server has gone away” error. There are also errors related to SEOmatic – can you try disabling that plugin in Settings → Plugins, and see if that helps? |
I disabled SEOmatic plugin but still issue occurs Attached updated web.log file |
Here’s a guide that explains how to disable a plugin: https://craftcms.com/guides/disable-a-plugin |
maybe useful that a tooltip on the disable/remove pop-up menus could give a local reminder and brief explanation for how this area is supposed to work? |
@brandonkelly i disabled plugin as you have mentioned but still the issue occurs. |
Thanks, that has narrowed the issue down to the Looks like this is occurring when Craft is trying to write to the |
@brandonkelly Thank you very much. |
Sorry, I should have also mentioned, you can specifically disable element query caching via the cacheElementQueries config setting (without disabling template caching altogether). 'cacheElementQueries' => false, Note that if you do this, your caches won't automatically clear themselves when you create new entries, so you need to manually clear them. At that point, it may make more sense to switch over to using the Cache Flag plugin instead of the native |
Thanks @brandonkelly |
Hi, When login into craft admin panel through localhost/projectname/admin and then we navigate to another tab in the same browser where there is frontend loaded and click on the detail of the "xyz" product then session issues are occuring, can you please suggest something on this? Is it in craft cannot we have frontend and backend working at the same time in same browser? Thanks |
@chandamotiyani Do you have multiple separate Craft installations all running from |
Hi @brandonkelly
|
Looks like that error is coming from a custom |
But also because of the session as well because POST request is not working once I log in into the admin panel of the same project whose front end is opened in the same browser in another tab, so I'm not able to go through the front end because it's throwing error on all the pages its just one of them where it's trying to get the property from POST request but not giving any results. So, can you please tell me that is there any way to go through the front end and the admin panel at the same time in the same browser for single installation of the project as I said already there are no multiple installations? |
Yes that is absolutely possible. I’m certain this is going to be an issue with your custom module, not with Craft. |
@brandonkelly I request you to tell me the way with which we can log in the admin panel and view the front end of the same project in the same browser at the same time. |
@chandamotiyani assuming they both are accessed from the same domain, there’s nothing special you need to do. It’s just like accessing two different pages of the Craft control panel at the same time – of course it’s possible. Try removing your custom module and see if that helps. |
Description
Frontend not works after updated to Craft CMS 3.3.20.1, but works when there is '?token' query string.
I am getting "Internal Server Error" where '?token' query not passed (i added manually in browser url)
But admin section works fine
Before updating Craft CMS frontend never required '?token' query string in URL, it worked without '?token' parameter
Please suggest me how to make frontend as before that is without '?token' query string parameter in URL
Additional info
The text was updated successfully, but these errors were encountered: