I'm getting ready to move towards the daily builds of version 17, but I have one question. from what I'm reading, this is not going to be compatable with the old runemaster web of what was in prior versions, and moving forward, it's being replaced with echickens web program. My question is, will updating to ver 17 kill my present web, or will I have a chance to update slowly, or should I switch over to EC web program first. I've put a lot of work into my web page, and I don't want to lose it by just switching versions of sync. Thanks
I'm getting ready to move towards the daily builds of version 17, but I
have one question. from what I'm reading, this is not going to be compatable with the old runemaster web of what was in prior versions, and moving forward, it's being replaced with echickens web program. My
question is, will updating to ver 17 kill my present web, or will I have a chance to update slowly, or should I switch over to EC web program first.
I've put a lot of work into my web page, and I don't want to lose it by just switching versions of sync. Thanks
v3.17 will work fine with the legacy/runemaster Web UI. You don't have to switch to echicken's or any other Web UI framework if you don't want to.
I'm getting ready to move towards the daily builds of version 17, but I have one question. from what I'm reading, this is not going to be compatable with the old runemaster web of what was in prior versions, and moving forward, it's being replaced with echickens web program. My question is, will updating to ver 17 kill my present web, or will I have a chance to update slowly, or should I switch over to EC web program first. I've put a lot of work into my web page, and I don't want to lose it by just switching versions of sync. Thanks
v3.17 will work fine with the legacy/runemaster Web UI. You don't have to switch to echicken's or any other Web UI framework if you don't want to.
Do you have a compelling reason to move to version 3.17? 3.16c is still quite recent. Just wondering if there's some new feature or bug fix that you want to take advantage of.
Not sure where you read that, but it isn't true. The stock web UI will still work, and my latest web UI isn't even in the Synchronet CVS repository yet.
How do you plan on updating? If you're on Windows and grabbing the sbbs_dev.zip and sbbs_run.zip archives, they won't touch your 'web' directory IIRC.
a thought (being I am doing this) if you have another computer setup sbbs on it, then change the web info in sbbsctrl and start move your current sbbs pages over, and make any changes and and soon as your happy with it, move the changes over to your main sbbs (after you changes the info in sbbsctrl)
a thought (being I am doing this) if you have another computer setup sbbs on it, then change the web info in sbbsctrl and start move your current sbbs pages over, and make any changes and and soon as your happy with it, move the changes over to your main sbbs (after you changes the info in sbbsctrl)
Actualy, thats what I'm in the process of doing.
It will allow me to keep
what I have while I move forward with a new web design,,
and I will be able to test it locally as I go. Thanks
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 06:57:44 |
Calls: | 510 |
Messages: | 220571 |