Yes Egg agreed, but as you probably know, it was a rhetorical 'why?'
Except for the most simple of sites, WD's Publish function lacks everything you really need to manage the architecture of more complex web sites.
Yes Egg agreed, but as you probably know, it was a rhetorical 'why?'
Except for the most simple of sites, WD's Publish function lacks everything you really need to manage the architecture of more complex web sites.
I just created a simple example of multiple .web files that define a single website. Got it right on the first try!
For this experiment, I felt it was important to keep things pretty bare bones. What results is a three page site, divided between three .web files.
- Create a single web page with navigation buttons.
- button 1: Web Properties > Link to page = index
- button 2: Web Properties > Link to web address = _2.htm
be sure to click 'off' the option box 'Correct address automatically'- button 3: Web Properties > Link to web address = _3.htm
be sure to click 'off' the option box 'Correct address automatically'- Write 'one' at the center of the page (as a visual page indicator).
- File > Save = _1.web
- File > Export website = index.web
__________
- Change 'one' to 'two' at the center of the page (as a visual page indicator).
- File > Save = _2.web
- File > Export website = _2.web
__________
- Change 'two' to 'three' at the center of the page (as a visual page indicator).
- File > Save = _3.web
- File > Export website = _3.web
__________
- FTP the three .htm files and their companion folders to the target location on the hosting server.
- Access your site using an internet browser. In this case, http://www.worx.cc/split/.
cursor = curTIS sorENSON
xWD5 & xX5 Multi-Level Navbar Tutorial | xWD5 & xX5 DropDown Video Tutorial
Upon further review, there seems to be a bit of an export bug (or at least a misunderstanding on my part about how to properly make a particular link assignment).
As noted in the previous procedure, button 1 in the navbar is linked to index.htm. I have double-checked that this is the case within all three .web files. Upon export, however, _2.htm and _3.htm have those links changed to reference themselves, not to index.htm.
Why might this be, and what is the corrective technique.
Thanks.
cursor = curTIS sorENSON
xWD5 & xX5 Multi-Level Navbar Tutorial | xWD5 & xX5 DropDown Video Tutorial
I'm not quite sure what is the problem. The example site here: http://www.worx.cc/split/
works as expected. Links to index.htm work well on all 3 pages.
John.
Thanks for looking, John. I discovered the problem and fixed it.
Here is reference to the version that I was complaining about: http://www.worx.cc/split-old/. Note that once you go to two or three, you simply can't get back to one.
The problem was with my step 2 in the procedure above. _2.web and _3.web must be handled differently. With those files, instead of
I had tobutton 1: Web Properties > Link to page = index
By wrongly pointing to the index page (in these two files), it simply pointed to the first page in that .web file. Instead, I need to explicitly point to a file named index.htm that is located in the same host folder as the other .htm files. Make sense?button 1: Web Properties > Link to web address = index.htm
Because of that procedural difference, and because see that I erroneously said that the the File > Export website outputs a .web file ( ), I'm going to repost the corrected instructions.
cursor = curTIS sorENSON
xWD5 & xX5 Multi-Level Navbar Tutorial | xWD5 & xX5 DropDown Video Tutorial
Here is the revised/corrected procedure for splitting a website into multiple .web files:
- Create a single web page with navigation buttons.
- button 1: Web Properties > Link to web address = index.htm
- button 2: Web Properties > Link to web address = _2.htm
be sure to click 'off' the option box 'Correct address automatically'- button 3: Web Properties > Link to web address = _3.htm
be sure to click 'off' the option box 'Correct address automatically'- Write 'one' at the center of the page (as a visual page indicator).
- File > Save = _1.web
- File > Export website = index.htm
__________
- Change 'one' to 'two' at the center of the page (as a visual page indicator).
- File > Save = _2.web
- File > Export website = _2.htm
__________
- Change 'two' to 'three' at the center of the page (as a visual page indicator).
- File > Save = _3.web
- File > Export website = _3.htm
__________
- FTP the three .htm files and their companion folders to the target location on the hosting server.
- Access your site using an internet browser. In this case, http://www.worx.cc/split/.
cursor = curTIS sorENSON
xWD5 & xX5 Multi-Level Navbar Tutorial | xWD5 & xX5 DropDown Video Tutorial
Great ideas! I wish I had thought of that.
I made a 23 page site that I should have split up into seperate xara pages. The site works fine but is a pain to export the whole thing when I have only made a change to one page. I need to figure out how you all do that use object multiple times to cut down on the load time.
Great Forum - thanks for all the help!
hello Everybody.
I`m new here.
Very enjoyable reading the posts and `learning`.
It was with great interest that I found this thread. Having trawled through some 60 pages or so until I came across what I was looking for.
What is interesting is the htm and the html file saving facility in WD.
I have six files. each once containing about 70 pages.
It works great in html until I save and then it does strange things.
I run smaller files in htm and its fine too. I convert them to html and the strange things happen again.
I wass wondering if it was to do with the `mass conversion`of the pages as they become html instead of my htm.
I reproduced the above file with 6 different files in htm as single page files. so I am suspecting it is because of the use of multiple page files that they become html. So do I need to make each page a seperate file. This I can do and it does appear to be a reasonable way forward. Especially with the editing.
An views, opinions etc.
Thanks.
Bookmarks