-
Posts
-
Our live site is currently using v2.3.1 of Enfold and it appears that the original developers customized the parent theme as there is no child theme present. It also looks like edits and customizations were made to custom.css, layout.css, and possibly more files.
We are trying to update a dev site on a testing server first, to make sure we can get v3.0.1 of Enfold working with WordPress 4.0 before we feel comfortable that changes to our live site won’t be ruined.
What would the best way be to go about this? (Use the 3.0.1 version as the parent and create a new child theme and try to input the customizations there?) What is the easiest/best way to find all the customizations that were originally done to make sure that they get applied?
We are having no luck getting the new version working and looking the way its supposed to match the live site on the dev site.
Enfold has a lovely feature built in that allows you to copy settings from the parent to the child. Of course that isn’t going to find the theme file modifications. Given it takes less than 5 minutes to set up a child theme, and the developer failed to do so, I wonder if you really want to find out what they did and replicate it? You may have a more solid footing going forward if you replicate the design and functionality that is important to you without necessarily following what has gone before.
That said, you could obtain a clean copy of the same version number of the theme, and you could then use a diff tool to find differences in the files.
The mods may have a better method, and I’m sure one of them will be along soon…
Hi!
Thank you for using Enfold.
I’m sorry but we won’t be able to help you trace back all the modifications made on the theme but note that all theme options and custom css codes located on Quick CSS will be retained when updating the theme. Since you’re using a very old version of the theme, some of the options and elements might break so you have to adjust those or create them from scratch. Theme update should be done regularly to keep up with WordPress and other code changes. Please refer to this link on how to move the website to a child theme: http://kriesi.at/documentation/enfold/using-a-child-theme/
Best regards,
IsmaelWe have decided to go with a fresh build and use a child theme, however, the child theme changes don’t seem to be taking effect. For example, we’re trying to use editing page.php and footer.php within the child theme folder but the site isn’t showing those changes to those files. The custom.css doesn’t seem to be taking either, the only changes to CSS we can make and see are the ones within the theme settings Quick CSS area. Finally, uploading background images via the theme settings to the footer or socket don’t take affect either.
Is there something we need to do to make the child theme work?
Hi,
That’s strange, can you please create us a WordPress administrator account? post it here as a private reply.
Regards,
JosueI think we figured it out! It appeared to be a server issue that we’ve now resolved.
Our only other outstanding questions is, when we upload and activate the new theme – will we lose the existing page content that pages with the backend editor are using? We understand that you typically have to redo menus and widgets, but we’re worried that switching themes will cause the content on pages to disappear as well. Can you advise?
Hey!
No, that should not be affected as it is stored in the database and not theme-bound.
Best regards,
JosueThanks for your responses Josue!
So even the pages that are using the theme-specific backend editors to bring in columns/sidebar widgets/text areas, etc – these shouldn’t be removed with the theme change?
- You must be logged in to reply to this topic.