Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
boro_boy Posted April 30, 2016 Posted April 30, 2016 I've bought a custom theme from ipsfocus, but everytime I update the theme, it resets everything to default so I have to spend 5 mins changing everything again. I asked on their forum here: http://www.ipsfocus.com/forums/topic/10459-when-updating-theme-it-resets-it-to-default/ But the "root admin" was unsure how this works. Is it possible to upload an update to a theme without losing all your custom edits to the theme? Thanks in advance.
Nathan Explosion Posted May 1, 2016 Posted May 1, 2016 I'd expect it to do that. You've got the original theme....you've then customised it. Then an update of the original theme is uploaded....I'd expect it to reset your customisations. Without having much knowledge of the update functionality, I doubt it is designed to look at your modified theme and compare it to the update and then present differences to you and ask you if you want to keep/change them. Other options? Depends on what the changes are that you are making. Are they template edits, or custom.css changes, or colour changes in the theme settings itself?
Dll Posted May 1, 2016 Posted May 1, 2016 I'd expect it to over-write template and (non custom) css changes, but not theme settings which it appears to.
steve00 Posted May 1, 2016 Posted May 1, 2016 1 hour ago, Dll said: I'd expect it to over-write template and (non custom) css changes, but not theme settings which it appears to. You would be better to create your own css file within the custom section of css (e.g. mycustom.css) then when you upload a new version it will not (or should not) overwrite your mycustom.css file) If you make your changes to custom.css file then yes, when you upload new version it will overwrite the custom.css file with the new one.
Dll Posted May 1, 2016 Posted May 1, 2016 1 hour ago, steve00 said: You would be better to create your own css file within the custom section of css (e.g. mycustom.css) then when you upload a new version it will not (or should not) overwrite your mycustom.css file) If you make your changes to custom.css file then yes, when you upload new version it will overwrite the custom.css file with the new one. It doesn't update the custom css changes, it keeps those intact, but the issue is that the theme settings get overwritten by default values, none of which can easily be saved to file or anything else so you have to manually re-do them all.
steve00 Posted May 1, 2016 Posted May 1, 2016 1 minute ago, Dll said: It doesn't update the custom css changes, it keeps those intact, but the issue is that the theme settings get overwritten by default values, none of which can easily be saved to file or anything else so you have to manually re-do them all. What theme settings in particular ?
Dll Posted May 1, 2016 Posted May 1, 2016 All of them, anything which is set under settings within the customisation screen in the acp is returned to default values. I've raised this as a bug now, as I'm convinced this can't be working as intended as there's little point having an option to update a theme currently, you may upload any updates as a new theme every time.
Simon Woods Posted May 1, 2016 Posted May 1, 2016 I think the type of thing the uploader is wiping out includes the 'Logos' tab, right?
steve00 Posted May 1, 2016 Posted May 1, 2016 As I said more info .... are you referring to front end colors, button colors, text colors or something completely different If button, text colors etc then change via css If something different then as mentioned more info 2 minutes ago, Simon Woods said: I think the type of thing the uploader is wiping out includes the 'Logos' tab, right? Uploading new version has never removed logo from my themes (hope never does either)
Colonel_mortis Posted May 1, 2016 Posted May 1, 2016 I believe this bug has been fixed in 4.1.11, but will only take effect once you have modified the settings while running 4.1.11.
Dll Posted May 1, 2016 Posted May 1, 2016 33 minutes ago, Colonel_mortis said: I believe this bug has been fixed in 4.1.11, but will only take effect once you have modified the settings while running 4.1.11. I don't think it has unfortunately. @steve00 - it is any and all theme settings which are set under the settings option in the ACP. Colours, backgrounds, responsiveness, features unique to the skin, and anything else which is available to set.
Nathan Explosion Posted May 1, 2016 Posted May 1, 2016 19 minutes ago, Dll said: I don't think it has unfortunately. @steve00 - it is any and all theme settings which are set under the settings option in the ACP. Colours, backgrounds, responsiveness, features unique to the skin, and anything else which is available to set. Simple thing to check - ask the theme owner of those settings/items are included in the theme file? If they are - then, as I said earlier to the OP...I'd expect them to be set in place. The theme contains those items - it's not just templates and css, the settings are part of the theme too. If they aren't included in the theme file then report it as a bug.
jcdesign Posted May 1, 2016 Posted May 1, 2016 I copy the theme and then uploading a new version over the copy theme. In this way you only have to the half work, but always standard, change background image, logo, footer setting, guest message and more. After this make the new updated theme as default and set as members theme.
Dll Posted May 1, 2016 Posted May 1, 2016 38 minutes ago, Nathan Explosion said: Simple thing to check - ask the theme owner of those settings/items are included in the theme file? If they are - then, as I said earlier to the OP...I'd expect them to be set in place. The theme contains those items - it's not just templates and css, the settings are part of the theme too. If they aren't included in the theme file then report it as a bug. Thanks, removing them from the upload file does seem to work. So maybe the developers of themes could provide a setting less upload file to make life simpler?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.