- This topic has 3 replies, 2 voices, and was last updated 13 years, 10 months ago by
.
-
Posts
-
I would like to upgrade to the latest version, but I am concerned about changes made to my existing installation – beyond settings within the plugin.
– Changes to the stylesheet
– Additions for integration with iDev affiliate (replicating this should be simple)
– Changes made by your support, this was all I was provided “Found the issue. It was conflicting with another plugin. Added a workaround in eStore to address this.”
While I can likely identify the changes I made and copy the code, I am most concerned about the undocumented workaround added and whether the plugin will work (or not) following the upgrade.
Also, if I simply copy the old stylesheet over, will anything break in the new version? i.e. were there new styles added?
1. Changes to the stylesheet – You should always add your custom CSS in the “wp_eStore_custom_style.css” file. That file is never modified by us. This way during the upgrade you just keep a backup of that file and then after the upgrade you replace that file.
2. Custom integration that are not officially supported by eStore will need to be reapplied. You can tell us what you did and we can look into adding this integration as an option in eStore (we will add it, if it is reasonably easy and benefits a lot of customers).
3. If we told you that we added conditions in the plugin then this change also made to the core. So there is nothing to worry.
You can take a backup and keep a backup copy of your current eStore somewhere on your PC. If things do not turn out good you can roll back.
I believe most of my CSS changes were in the extra shortcodes plugin because they were mods to one of the fancy displays. I am assuming these are thus irrelevant to updating the core then.
Are styles listed in wp_eStore_custom_style.css set to automatically override others or do I need to add something like .custom before it?
Upgrading eStore code does not directly affect the extra shortcodes plugin.
The custom CSS (wp_eStore_custom_style.css) is loaded after the main eStore CSS. CSS will always take the last defined definition for a class or ID. So yes you can use the custom CSS file to override any main CSS (no need to add .custom before it).
- You must be logged in to reply to this topic.