mk2-pronat Posted September 19, 2023 Share Posted September 19, 2023 Hello, I keep reading similar issues but can't seem to figure out what to do with mine. I added a print screen from the console with the error. I'm not a programmer so some explanation would be much appreciated. Can't save any modifications to existing products. Website is https://scufita-rosie.ro/ Link to comment Share on other sites More sharing options...
JBW Posted September 19, 2023 Share Posted September 19, 2023 There is some error in the background, avtivate debug mode to see more details Link to comment Share on other sites More sharing options...
mk2-pronat Posted September 20, 2023 Author Share Posted September 20, 2023 Thank you for your reply. I activated debug mode, and when i try to recreate the problem (save a change to products) it crashed the whole website. I can't access it anymore with chrome. It works with Firefox. I keep seeing this 403 forbidden access for some reason, could it be from the server side of things. The thing is that not all the products are affected and everything works fine if i just create a new product. Link to comment Share on other sites More sharing options...
mk2-pronat Posted October 2, 2023 Author Share Posted October 2, 2023 I am adding some information for future reference about this problem. I've reached out to other forums and developers to better understand what was happening. It seems that the product tokens are not being validated for some products. In PrestaShop, when you perform actions like saving a product, the application generates a CSRF (Cross-Site Request Forgery) token, it is for security reasons. A CSRF token is a unique value generated for a specific action (e.g., saving a product) and is tied to the user's session. When the action is performed, the server checks if the token matches the expected value for that action, enhancing security. I will not go into this because i have limited knowledge and wouldn't want to misinform, i am just forwarding what i was told. In my case, the developer told me that this happens when you import products to the database and the solution was to regenerate the database. I don't know how this is done, but now it works, so in the future if someone has similar problems you might want to look into it from this angle. Good luck. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now