Support Forum
Hi, I'm still playing with the bubblewrap of SimplePress 4. And what I'm seeing so far I like - very much. Now, I'm not too much in the way of a skinner, but I like type (font) consistency - so I've done a straightforward mod of all font-family declarations in the CSS files to suit the rest of the site I'll probably put it "in production" on.
Of course, the problem with that is that an update / upgrade will wipe out those mods, so...
I'm wondering whether it's possible to include some way to accommodate preserved customization of the CSS - e.g. via an external but "safely" located file, or by some override mechanism (and embedding the custom bits in the "standard" WP theme folder CSS file, or via a database blob, or...
Dunno. I guess I'll copy my CSS files in the meantime, just in case! [Image Can Not Be Found]
(Um, if I overlooked something already in place for that... Please delete this post and shoot me, in whichever most convenient order)
What is this "Admin Menu" of which you speak? There actually is an "Admin Menu"? [Image Can Not Be Found]
OK, more seriously: from the information I saw there earlier, it essentially explains how to customize, but is silent on where to customize outside the plugin folder - with plugin upgrades typically that means: customizing is out of the window (i.e. will have to copy back in any changes).
Not a biggie, just thought it might be handy, perhaps, to figure out a standardized mechanism to deal with custom CSS that is upgrade-persistent. Then again, I'm not sure if the number of users tweaking CSS is significant enough to bother, so I'm fine with it.
Now you can shoot me. [Image Can Not Be Found]
copy the skins folder you want to modify and paste it into the skins directory and rename it to whatever you want to call it. go into that new directory and rename the .css file to match the directory name exactly with the .css extension. you now have your own skin that wont be deleted upon upgrades. you may have to update it later if we add new features that require additional styling but it wont get deleted.
you can go into the styles tab and choose it for your skin.
Visit Cruise Talk Central and Mr Papa's World
Aha! Now that's unexpected, but clever. I assumed (ahem...) that plugin folders are supposed to be treated as a danger zone in their entirety: clever coding that. Indeed, it's a much more intuitive approach to assume everything stays put.
Either way: thanks twice - for the very quick asnwers, and most of all, for your hard work developing a hard-core rocking plug covered all over in win.
Consider this topic closed and irrelevant!
thanks for the kind words... of course, if you delete the plugin folder before upgrading, all will be lost 
but if you just upgrade, at least we wont overwrite it
enjoy!
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)