|
|
Final Notes
This is a collection of various notes related to publishing with Composer or just
using it in general. Basically, just some observations about Composer and
the relationship to ChurchServe accounts.
Noteworthy Issues
Here are some interesting things about the behaviour of Mozilla Composer:
- After making edits to a web page, clicking the Publish icon will
cause Composer to update the web page without bringing up the Publish dialog
(works softa like a "save to remote" feature).
- If you save the edited file
to your local computer before publishing the change will cause the Publish
dialog to appear.
- If you save a file you edit after publishing, Composer seems to "forget"
the local location of the file -- which will prompt you for the location
on your computer to save the file. This is noteworthy because it might
confuse some people that try to edit something they just published.
- If a user has never setup any publishing sites before, the first
time the user attempt to publish, the Settings tab will appear. This
tab must be filled out completely before being able to publish.
- Mozilla allows you to keep track of several Publishing Sites by
using the Publishing Site Settings dialog -- accessible from the Edit
menu, then Publishing Site Settings menu item.
Noteworthy Issues related to ChurchServe accounts
- Free and Almost Free Website accounts usually will not use the
subdirectory location field in the Publishing tab unless the page belongs
in a specific subfolder. The base or root directory of the Free and Almost
Free Website account is the default directory the FTP client will log into
-- this is not the case for all other hosting services by ChurchServe.
- All other (paid) services provided by ChurchServe make the base or root
website content directory under the /website subdirectory. Failure to specify this
as your subdirectory while publishing will cause your files to go to the wrong
location (and not show up on the web). Other programs that use FTP will have
this same behaviour.
Observations about Mozilla Composer
Some obvervations about using Composer as a Web Page editor and Website Manager.
- Composer is a great deal considering it is free.
- The publishing feature of Composer is fine for uploading
web pages one at a time but not a good solution for managing
a large website. Even publishing a several page website requires
one to open each page and publish it accordingly.
- Along the lines of the previous note, Composer is better suited
for the creation and editing of individual web pages and then one
should consider using a full fledged FTP client to upload
all the website content.
Back to Contents
Back to Contents
|