|
Home > Archive > FrontPage Server Extensions for Windows > March 2004 > Bizzare Publishing problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Bizzare Publishing problem
|
|
|
| This was originally posted in the Frontpage General Group, but after further troubleshooting this appears to be an Extension 2002 issue.
The file path is incorrect for the images that do not show.
http://www.melco-service.com/_borde...ges/Samples.jpg
is the incorrect path
http://www.melco-service.com/images/Samples.jpg
is the correct one.
Looks like the Extensions are making changes that should not be made?
The real problem is that FrontPage 2000 can open the web just fine, and looks "normal" as it should. However after publishing to a webserver running EXT '02 the web looks like this www.melco-service.com
Any thoughts or suggestions would be most appreciated!
Orginal Post:
Our Technical support site needed revamping, so I setup an area on our FrontPage Intranet for them to redesign a site using a subweb on the Intranet. Things are great on the intranet site, the service dept can open the web directly and make any changes cr
eate forms, modify, etc. My plan was to then take this sub web and publish it to our webserver. The webserver is an NT4sp6a and I installed 2003 Ext without a problem. I deleted the old web in IIS, created a brand new web which I then converted to a FP we
b. Then I opened the Intranet subweb and published to the new blank FP site. The website publishes successfully according to FP 2000 (which we are using to develop the web).
Now check out the bizzare result:
www.melco-service.com
the bizzare thing is that if you refresh the website as FP is publishing it looks good! it is not until is "publishes successfully" does it get hosed up.
I have already reinstalled the extensions twice, as well as deleted and recreated the website. I have also recalculated links and republished, as well as deleted the files on the server (using webfolders) and republised. One thing that I did run into a pr
oblem with is that I read an article about pubishing to a local folder first, then publishing from the local webfolder up to the webserver. I get the following error when this is attempted: "An error occurred accessing your FrontPage web files. Authors -
if authoring against a web server, please contact the webmaster for this server's site. WebMasters - please see the server's system log for more details."
There's nothing Fp related in the system log but in the App log "Microsoft FrontPage Server Extensions:
Received empty response from Microsoft FrontPage Server Extensions"
This is in addition to the normal warning message FP gives when publishing to a site where Extensions are not found.
Any thoughts or suggestions?
| |
| Stefan B Rusynko 2004-03-25, 2:39 pm |
| See my response in client (general) newsgroup
--
________________________________________
_____
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
________________________________________
_____
"KCL" <anonymous@discussions.microsoft.com> wrote in message news:13F31993-47B4-4911-A542-9E89171AC280@microsoft.com...
| This was originally posted in the Frontpage General Group, but after further troubleshooting this appears to be an Extension 2002
issue.
|
| The file path is incorrect for the images that do not show.
| http://www.melco-service.com/_borde...ges/Samples.jpg
| is the incorrect path
| http://www.melco-service.com/images/Samples.jpg
| is the correct one.
| Looks like the Extensions are making changes that should not be made?
|
| The real problem is that FrontPage 2000 can open the web just fine, and looks "normal" as it should. However after publishing to a
webserver running EXT '02 the web looks like this www.melco-service.com
|
| Any thoughts or suggestions would be most appreciated!
|
| Orginal Post:
| Our Technical support site needed revamping, so I setup an area on our FrontPage Intranet for them to redesign a site using a
subweb on the Intranet. Things are great on the intranet site, the service dept can open the web directly and make any changes
create forms, modify, etc. My plan was to then take this sub web and publish it to our webserver. The webserver is an NT4sp6a and I
installed 2003 Ext without a problem. I deleted the old web in IIS, created a brand new web which I then converted to a FP web. Then
I opened the Intranet subweb and published to the new blank FP site. The website publishes successfully according to FP 2000 (which
we are using to develop the web).
| Now check out the bizzare result:
| www.melco-service.com
| the bizzare thing is that if you refresh the website as FP is publishing it looks good! it is not until is "publishes
successfully" does it get hosed up.
|
| I have already reinstalled the extensions twice, as well as deleted and recreated the website. I have also recalculated links and
republished, as well as deleted the files on the server (using webfolders) and republised. One thing that I did run into a problem
with is that I read an article about pubishing to a local folder first, then publishing from the local webfolder up to the
webserver. I get the following error when this is attempted: "An error occurred accessing your FrontPage web files. Authors - if
authoring against a web server, please contact the webmaster for this server's site. WebMasters - please see the server's system log
for more details."
| There's nothing Fp related in the system log but in the App log "Microsoft FrontPage Server Extensions:
| Received empty response from Microsoft FrontPage Server Extensions"
| This is in addition to the normal warning message FP gives when publishing to a site where Extensions are not found.
|
| Any thoughts or suggestions?
|
|
|
|
|
|
|