Skin Updates
Suggestions
I have noticed something about the way that skins are updated from the marketplace. On yesterday, I ran the update to upgrade my Elastic skin to v1.2, upon completion, I ended up rolling my site (skin) back to v1.1.4 for the following reasons:
1. The update effected the look & feel of my site as it changed my background from the set image to a black background.
2. In addition, the update changed my menu (in mobile view) & it also changed my header (behavior) from scrolling to fixed.
3. The () content boxes (in my site index) have also been changed to a layout that don't really appeal to users of my mobile interface.
My Suggestion(s):
A. Please don't steer away from the look & feel of v1.1 - v1.1.4, elastic skin.
B. Is there a way to fix the marketplace skin update system to where it will only inject code revisions into our sites, without affecting the customizations that were put in place by us (the site owners)? Had I not rolled back to the previous version, I would've had to go back into the jrCore to reinsert the desired customizations that I added prior to the update.
** I love what you guys are doing with the jr5 project, in no shape, form or fashion am I trying to knock or bash how you guys manage the jr Road map, my suggestions are in my humbled opinion.
Thanks
updated by @trickyricky: 07/10/14 04:03:43AM