I am testing a web page by publishing it locally so that eventually it can be ftp’d to a server.
Upon local export, the folders for the various pages have the names, page-1, page-2, etc, rather than the names they were given in RW, i.e., ‘home,’ ‘about us,’ etc.
The names were changed in RW before export to a local folder.
If the eventual URL is “domain/page-six/” it will look a bit confusing, since with page renamings and all there are only three pages.
Is there a fix in RW before export?
I think you are confusing the page names (for navigation) with the folder name. The names in the left-hand inspector under “Pages” are the page names. They are used as the wording of the pages in navigation menus of the site.
The actual folder names and the file name of the generated HTML files are set in the right-hand inspector. They are set on the first page of settings under the General Settings heading.
Current, best practices are to name your folder to indicate what the page is about and to leave the filename as index.html. Also, make sure that “Tidy Website Links” is selected under Advanced settings in the left-hand inspector.
Here’s where you enter the folder name and the filename:
Edit: these settings affect the generated HTML files whether created via export or published to a web server.
2 Likes
Hi there, I have a similar problem. I puplished my site locally in a folder (pagenames are correct). When testing it by opening the “index.html” file, my homepage pops up (Mac, Safari), but when I want to go to my linked pages (impressum etc.) the finder opens and just shows me the folder there, not the site.
It works in preview in RW8.
Now my question: does this change when I upload it directly to a FTP-Server or did built something wrong? Thank you.
Webpages are designed to be served by a web server. Publishing all pages of a site to a local folder will produce all the files needed for a web server to use.
By opening the file(s) directly with a browser, you’re skipping the very important web server step. Web servers like Apache, Nginx or IIS do quite a bit of “stuff” with these files prior to the end users browsers getting them. Thinks like PHP and “tidy links“ are handled.
If you’re looking to preview your site locally prior to publishing to your hosting company then you’ll need to run a web server on your Mac. Luckily that sounds more complicated than it is, there’s a product that has a free version called MAMP available. It runs full versions of Apache, mySQL and PHP on your Mac with a simple, single interface.
3 Likes
Thank you so much, teefers. I’ll try that later. I thought it could be something like that but didn’t want tgo upload something into the web that isn’t ready yet. Thank you!
Is there a free, Linux alternative for testing?
The Linux versions were the originals called LAMP. Use your favorite search engine for “ lamp linux”.
LAMP = Linux + Apache + MySql + Php
MAMP = Mac + Apache + MySql + Php
I used MAMP for years before these acronyms dawned on finally me – I seem to remember that it hit me, embarrassingly, while on a facetime call with Joe Workman.
If there is a sort of dyslexia for acronyms… I’ve got that. LOL 
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.