ManuelAva Posted May 25, 2021 Share Posted May 25, 2021 (edited) Hello everybody, Yesterday, we added a new customized child theme to our site -we had previously tried it in a local version. Everything was working ok. After adding it, the changes we had made were working ok as well -some minor changes in the views. Today we found out something. Evertyhing we had been doing in the last month was lost. Our texts were lost, our pages were lost, etc. We reverted to the old at_movic theme but we are in the same place. Strangely, some new translations we had added yesterday are working and still there. Does anybody know how to proceed now? I would be very grateful for any help. Edit1: OK. One thing. I've realized is that when a new child theme is created, an appagebuilder directory with its content is automatically created. This directory was created for an old version of our web that we deplyoed in local for testing purposes. BUT I uploaded it to the server (for the newest, correct version) as it is part of the theme. Could this be part of the problem? Again, restoring the at_movic default theme didn't solve it so I dont know. Edit2: Apparently adding our new theme deleted everything related to the appagebuilder configuration in our database. We restored our backup and everything is ok now - aside from momentaneous heart stroke. We'll try to edit the parent theme instead; as far as I know this is not recommended at all but we'll see how it works. Regards Edited May 25, 2021 by ManuelAva Syntax (see edit history) Link to comment Share on other sites More sharing options...
w3bsolutions Posted May 26, 2021 Share Posted May 26, 2021 This appagebuilder is not something from Prestashop core. Do you use a page builder or a third party module? Link to comment Share on other sites More sharing options...
ManuelAva Posted May 26, 2021 Author Share Posted May 26, 2021 We are using this: https://addons.prestashop.com/es/personalizacion-pagina/20111-ap-page-builder.html Link to comment Share on other sites More sharing options...
w3bsolutions Posted May 26, 2021 Share Posted May 26, 2021 Well, it seems the issue is related to that addon then, since it does not happen on a default installation. Just wanted to note that since in your initial post and title it seems like it’s and issue with Prestashop itself. Glad you managed to solve it 1 Link to comment Share on other sites More sharing options...
ManuelAva Posted May 26, 2021 Author Share Posted May 26, 2021 I agree. I thought it was an error in PS related to adding a new child theme but looks that it is not. Thanks for the interest! 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