IvanKa Posted 4 hours ago Share Posted 4 hours ago Hello, We recently migrated our PrestaShop store to a new domain. The store configuration and version (PrestaShop 8.1.7) remained unchanged during the migration. However, after the migration, the AxonCreator editor stopped working completely. Error: Instead of the editor interface, we see an error message: "The preview could not be loaded" with text stating "We're sorry, but something went wrong. Click on 'Learn more' and follow each of the steps to quickly solve it." When clicking on the debug link, we're redirected to a 404 error page at api.axonviz.com. What we have already tried: Reset the AxonCreator module Completely updated the entire Akira theme using the module updater Switched between different themes (Akira and custom child theme) Disabled ALL modules except AxonCreator to eliminate conflicts Cleared cache after each change Verified that the frontend pages display correctly and the theme loads properly Browser Console & Network Analysis: Checked browser console (F12 > Console tab) - NO JavaScript errors or warnings related to AxonCreator Checked browser Network tab (F12 > Network tab) - NO failed requests or HTTP errors The editor interface loads successfully, the error appears only when trying to display the preview iframe No CORS errors, no blocked requests, no 4xx or 5xx errors in the network tab Current situation: The error occurs for ALL posts/pages when attempting to open any content in the AxonCreator editor. The frontend works fine - pages display normally with the Akira theme. The issue is only in the editor preview system. The fact that there are no console or network errors suggests the problem is either server-side or related to API authentication/authorization. Store Information: PrestaShop Version: 8.1.7 AxonCreator Module Version: 2.6.2.5 Akira Theme Version: 2.6.0.9 Frontend: Working correctly Module configuration: Accessible and enabled Questions for troubleshooting: Could this be related to API authorization after the domain change? Do we need to update API keys or authentication tokens in the AxonCreator module settings? Are there any database entries or configuration settings that store the old domain URL that need to be updated? What server-side logs or error files should we check to get more detailed information about what's failing? Do we need to update any configuration files in /modules/axoncreator/ directory? Is there a way to enable debug mode or verbose error logging in the AxonCreator module to get more detailed information about what exactly is causing the preview error? We need more specific error messages instead of a generic "something went wrong" to understand the root cause. What steps would you recommend to diagnose and fix this issue? Thank you Link to comment Share on other sites More sharing options...
ComGrafPL Posted 47 minutes ago Share Posted 47 minutes ago License for the specific domain? have you ask module support? 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