Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Publisher / Web Design / May 2005

Tip: Looking for answers? Try searching our database.

Publishing Pub 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
BrentDraygon - 30 May 2005 22:55 GMT
(MS Pub 2003 with service packs up to date)
One novice stumbling block for me was how to publish to the web,  the
available advice includes both FTP and HTTP.  I found that HTTP is easier,
esp with incremental publishing enabled (just  changes the page that have
changed).  I had to talk to my host server tech support for HTTP, they had a
separate user ID and passwork for HTTP which I entered when publishing (these
can be saved for more automatic connection).

I  found that for a pub  of say 2MB it will take serveral minutes  to
publish for the first time even with broadband. Updates will take a lot less
time.

I also found that  I needed to make sure that Front Page extentions were
turned on for my hosting pacakge, I can contol that from my account manager.  
At one time I had to have these reinstalled as they got corrupted.  (These
applied even though I am not using Front Page).

Even though I do not use the FTP publising method, I still have an FTP
client  (Cute FTP) to see my files on the server to see what happened after
publishing under HTTP and to upload other files for linking to from my site.

When reviewing an updated website, I have to first clear out the browser
cached files or I will likely get  pages from the old version

B Smith
David Bartosik - 30 May 2005 23:10 GMT
inline....

>"BrentDraygon" wrote:

> (MS Pub 2003 with service packs up to date)
> One novice stumbling block for me was how to publish to the web,  the
[quoted text clipped - 3 lines]
> separate user ID and passwork for HTTP which I entered when publishing (these
> can be saved for more automatic connection).

full documentation is found at
http://www.publishermvps.com/WebDesign/Version2003/tabid/33/Default.aspx

>  I  found that for a pub  of say 2MB it will take serveral minutes  to
> publish for the first time even with broadband. Updates will take a lot less
> time.

correct.

> I also found that  I needed to make sure that Front Page extentions were
> turned on for my hosting pacakge, I can contol that from my account manager.  
> At one time I had to have these reinstalled as they got corrupted.  (These
> applied even though I am not using Front Page).

Covered on the http://www.publishermvps.com/Default.aspx?tabid=30

FPSE are only required if you are using a form page. OR if you simply want
to use http uploads. FPSE are what support the http uploading.

Once using FPSE you are not to use ftp, ftp connections will break (corrupt)
FPSE.
Your host support should have that documented in their support publications.

> Even though I do not use the FTP publising method, I still have an FTP
> client  (Cute FTP) to see my files on the server to see what happened after
> publishing under HTTP and to upload other files for linking to from my site.

mistake.
if using http then use the Web Folder via the Windows Explorer to drag and
drop files and maintain folders. view your Windows OS Help if you don't know
about Web Folders. You would already have one present with the name of your
site.

> When reviewing an updated website, I have to first clear out the browser
> cached files or I will likely get  pages from the old version

Yes, just common sense.

> B Smith

was there a question here??

David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com

Rate this thread:






 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.