Viewing What happens when publishing to a pre-existing folder with pre-exising pages?
What happens when publishing to a pre-existing folder with pre-exising pages?
|
User: John S. 11 years ago
|
|
|
I'm publishing via FTP, so all the new content is going to the same host as where my old iWeb content lives. Before I started writing to folders that contain existing iWeb content, I want to know what will happen in several scenarios. Scenario 1 - Publishing to an Existing iWeb folder Lets assume the iWeb site lives at: www.domain.com/old_iweb_site/home_page.html. What happens if I publish a new page within www.domain.com/old_iweb_site/ folder, such as www.domain.com/old_iweb_site/everweb_new_page.html? My concern is that EverWeb will delete the old folder contents and then publish its new content. Scenario 2 - Re-using existing URL names What happens if there is an existing old URL and EverWeb publishes the exact same URL? I would expect EverWeb to overwrite the file. Or, will this be a problem for EverWeb ? Thus far I've been testing pages in a new directory, outside of the live site. I'm trying to decide how to approach the iWeb to EverWeb migration. If I can write to existing folders created by iWeb and EverWeb only overwrites content if the file names match, then I can do a slow, page by page migration. In other words, develop the page in EverWeb, publish it and never use iWeb again for that page (or pages). If EverWeb wipes the directory clean before publishing, then I need to recreate the entire site in EverWeb before publishing to the live site. Hopefully this all makes sense :) |
|
|
User: Roddy 11 years ago
|
|
|
Trying to overwrite an existing site one page at a time is a recipe for chaos. Better to publish your new site to a different folder and add redirects to the redundant iWeb created pages. Ideally, you should create a whole new site and publish it to the root folder - rather than a sub folder as iWeb did. ------------------------------- Roddy Website: http://everwebwidgets.com Contact: http://everwebwidgets.com/ewWidgets-home/contact.html NOTE: I am an EverWeb user and NOT affiliated with EverWeb! Any opinions expressed in this forum are my own. |
|
|
User: John S. 11 years ago
|
|
| This is going to be chaos no matter what... it's 100's of pages to be re-written and that will take me 6 months. And yes, a whole other can of worms is the iWeb folder structure. In a way, iWeb's structure is a blessing because the "old" site lives in that folder, where as the EverWeb site will live above the iWeb folder. It's a chinese wall of sorts. As a new EverWeb page goes live, the old iWeb page can changed to a simple redirect. It'll be messy for several months and the analytics stats will be hosed. My concern (as implied by those scenarios) is that EverWeb does some housekeeping during the publishing process and clears out directories. I don't think it will, but need to create some dummy test sites and see what happens. | |
|
User: Caroline Z. 11 years ago
|
|
| I'm in the same boat. Re-writing hundreds of pages from an iWeb site. Curious to see how this plays out. | |
|
User: Jumbo T. 11 years ago
|
|
|
Based on the link in this topic : http://billing.ragesw.com/forum.php?act=thread&tid=2869&p=1#post5 and assuming you have a folder with the sitename in upper- and lowercase, you can do it this way :  After you uploaded the EW site and pages display correctly, rename the FOLDER to FOLDER_. Then links will redirect to folder and nobody will get hurt. Last edit 11 years ago |
|
|
User: James R. 11 years ago
|
|
| I just went to my provider account and dumped all of the iWeb folders/files. Then uploaded my entire Everweb site and no problems at all. | |
| Post Reply |
| You must login or signup to post. |