Quote:
|
Originally Posted by Michael P That is correct, we do not build a new stylesheet based off the old way of doing stylesheets. So you will need to change the default.css to use your old settings if you are not using your forum integrated stylesheets. |
Well, I just made most of the changes to default.css, and it's not even taking those changes so long as vb2 integration is enabled.
Further, as a photopost customer, I am disappointed that I was forced to PAY, to UPGRADE for the purpose of patching SECURITY HOLES in the code I'd already paid for. Then, grudgingly doing so, I now find that the apperance settings from my prior install were not culled and re-installed in the new version, and I am to manually pick and choose each appearance setting and place it into a style sheet (that right now doesn't work) ? Honestly, an "upgrade" process that doesn't transfer prior application settings is not even qualified to be described as an "upgrade". Photopost is the ONLY software in my extensive history that would ever purport to offer an "upgrade script", then knowingly NOT transfer across prior configuration elements, then willingly say "yeah, we left those out". My jaw is literally on the floor. The old settings weren't even dumped out to a TEXT file to make the admin aware of what just happened to the entire appearance of his gallery! There's not even a lonely little caveat in the upgrade script that mentions "hey, your apperance settings are being DROPped without archival, please account for this." This is a serious flaw guys.
Look, all I wanted was my gallery to not be vulnerable to sql injection code via URL manipulation of the photopost php scripts. That's ALL I wanted. Now, assuming that we can even get default.css to work properly with vb2 integration enabled, I am stuck doing tit-for-tat APPLICATION changes by hand ?
This is NOT the proper way to care for and evolve your software train. OK, so let's try and get default.css working; but let it be known that making a free BUGFIX available for those using older code would have been the industry-standard way of doing things.
Thanks,
Jayson