It's better to write script changes into a vbs (or similar) script that reads the original file and applies your changes in the correct place. After an upgrade, you just re-run your 'setup' script to reapply the changes. This is the approach I've taken, FWIW. If there are major changes to the part of the Actinic script that your edits apply to, then it may not work, but as noted here, scripts are unlikely to change where there are workaround hacks available!!
Announcement
Collapse
No announcement yet.
Add to Basket
Collapse
X
-
ActiveStock
On-line, real-time stock control plug-in for Actinic V7, V8 and V9
**New - Captcha plug-in for your Contact Us form**
ActiveStock website
Free 30 Day Trial
ActiveStock Blog (including a new tutorial on a 'Sort By' function for long section pages)
-
Nick
The hack does exactly as you say.
Unfortunately, this thread has wandered off course on to a discussion about general script changes. The point being that, next time you upgrade Actinic (e.g. from v9.0.3 to v9.0.4), your script changes will get overwritten and your IT guy will have to manually put this hack in again. Not a big issue if you don't upgrade often and are always clear on what needs to be done, but a big PITA (as Darren put it) if you have lots of sites with lots of script hacks and upgrade often....ActiveStock
On-line, real-time stock control plug-in for Actinic V7, V8 and V9
**New - Captcha plug-in for your Contact Us form**
ActiveStock website
Free 30 Day Trial
ActiveStock Blog (including a new tutorial on a 'Sort By' function for long section pages)
Comment
Comment