Re: Beta 18
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 12318
interpreted = N
texte = >I already have a store front running with beta 15, do I need to do anything >special to conserve it when installing beta 18? Yes. There were a lot of changes for b18, and they're listed in the beta readme. We've gone to true suffix mapping now, and all the sample templates use .tpl instead of .tmpl, and the whole $command thing has changed to better conform to NT standards. These changes are not minor.Any new installs will overwrite files of the same name, so be careful if you've done modifications to templates in the GeneralStore folder, for instance. The beta GeneralStore files will overwrite your new ones! So move/rename all of your templates before installing.Here's what I would do as a transition plan. Let's assume you're using IIS at the moment. I'd go download WebSite 1.1e from ora.com, and install WebSite to respond to port 81 (IIS listens to port 80). Then I'd install b18 into the WebSite folder and play with everything there on port 81. The only tough part here is that you'll have to take down your b15 WebCatalog (shut down the service or quit DBServer.exe) temporarily whenever you want to play with b18, because you can't have both running at once. Don't install b18 as a service: just double-click DBServer.exe whenever you need it running.The idea here is to leave your IIS installation untouched while you get the templates working under WebSite. Once you're happy with the b18 implementation under WebSite, then you can install b18 as a service under IIS and move your templates over.---------------------- Here's another way to do it, but it requires more changes to your original templates, and will take your store down while you're doing the changeover:In your storefront templates: 1) rename all templates to .tpl 2) change all references from .tmpl to .tpl 3) change all $search? to ?command=search& (do the same for $purchase, $add, etc)This technique will move you forward to the new beta, but since you are making changes to your templates (instead of playing in a completely different web server folder) it will be harder to go back to b15 in a n emergency.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Associated Messages, from the most recent to the oldest:
>I already have a store front running with beta 15, do I need to do anything >special to conserve it when installing beta 18? Yes. There were a lot of changes for b18, and they're listed in the beta readme. We've gone to true suffix mapping now, and all the sample templates use .tpl instead of .tmpl, and the whole $command thing has changed to better conform to NT standards. These changes are not minor.Any new installs will overwrite files of the same name, so be careful if you've done modifications to templates in the GeneralStore folder, for instance. The beta GeneralStore files will overwrite your new ones! So move/rename all of your templates before installing.Here's what I would do as a transition plan. Let's assume you're using IIS at the moment. I'd go download WebSite 1.1e from ora.com, and install WebSite to respond to port 81 (IIS listens to port 80). Then I'd install b18 into the WebSite folder and play with everything there on port 81. The only tough part here is that you'll have to take down your b15 WebCatalog (shut down the service or quit DBServer.exe) temporarily whenever you want to play with b18, because you can't have both running at once. Don't install b18 as a service: just double-click DBServer.exe whenever you need it running.The idea here is to leave your IIS installation untouched while you get the templates working under WebSite. Once you're happy with the b18 implementation under WebSite, then you can install b18 as a service under IIS and move your templates over.---------------------- Here's another way to do it, but it requires more changes to your original templates, and will take your store down while you're doing the changeover:In your storefront templates: 1) rename all templates to .tpl 2) change all references from .tmpl to .tpl 3) change all $search? to ?command=search& (do the same for $purchase, $add, etc)This technique will move you forward to the new beta, but since you are making changes to your templates (instead of playing in a completely different web server folder) it will be harder to go back to b15 in a n emergency.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Grant Hulbert
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Denying access by IP address (2000)
Multiple prices (1997)
PCS Frames (1997)
Cannot calculate prices (1997)
Am I going senile? (Price recalc based on quantity) (1997)
Apache SSL and Linux (2002)
Date Sorting (1997)
[shownext] link disappears after first use. Why? - because w/out the formvar, max reset to def (2000)
multi-paragraph fields (1997)
Adding up line items. (2000)
Back to Authnet with storebuilder (2003)
How to Display text in empty fields (1997)
WC Database Format (1997)
Math function in Formula.db (1997)
[WebDNA] How to tidy up data extract ? (2013)
apparently to problem isolated (1997)
latest version? (1998)
RAM variables (1997)
This list needs a digest: rant, rave... (1997)
RE: Missing contexts on NT (1997)