Website turned to garbage

[captain]

My customer was making a simple text & pdf file update to a website. greenfield twp (http://www.greenfieldtwp.org)
When he saved it it turned to garbage. repeated text, missing images & borders. He has made many updates without problems. I asked their host to delete the website from their server & reinstall the FP2002 extensions. I republished a "previously saved" copy of the site. It still showed up as garbage. When I bring up the site to edit live it looks just fine in FP. I even brought it up live on my daughters computer in FP to make sure I didn't have cached info and it looks fine. I asked the host to clear the site one more time and I would publish again. Same problem..... Now the host said Tuff Terds, your doing something wrong and don't contact them, call Microsoft FP support. So now I am angry & figured I would see if anybody here could help. By the way the host they use is Advances.

[AMysticWeb]

Looks like most of everything is doubled.

Q . Have you tried going to the site control panel yourself (assuming they have one) and turning the extensions off and back on again?

If not, I would start with this and then republish with the Publish all pages option.

If there is no way to reset the extensions your self, I think, since you have a backup copy of the web, you might FTP into the site and start deleting pages one by one. Also be on the lookout for duplicate files. Then republish all. Just don't delete your index file.

A third option would be to create a dummy site or take another site and publish to this server. Of course using Publish all pages.

This would give you an indication whether it is the website itself or a server related problem.

[justjay]

I have seen this sort of thing happen to me before and what was happening was includes were screwing things up...and repeating...I do NOT think there is a problem with your FPSE --> I grabbed the code that was sent to the NET and published it here (http://www.thejehm.net/look/captain/)

Clean off the files yourself in FP via the Publish window...and then re-publish...see what happens...if you FTP your entire site up -- then you will kill your FPSE...

[captain]

Just Jay,
I am going to give deleting the files. The host server said they did it but when I published the files were still in the right publish window.
I used the new Tutorials to learn the proper way to delete them.:):
My left click on my Presario Notebook just went bad. I am using the touch pad & tapping and it is driving me crazy. I am opening programs when I don't want to.:p:

[captain]

Just Jay,
I just deleted all the files from the server & republished.
I am still missing the borders, navigation, the top border main banner and it is still duplicating info. You said something about includes, how do I check to see if that is messed up? If you to check what it is meant to look like if you bring up the site in live edit, you should see the way it is meant to look. You may be missing the background colors and some nav. buttons because I used a theme from an outside source.
If anybody else has any suggestions please feel free to do so.
Thanks

[Katta]

I've had this problem, but sorry to say, I still don't know what I did to fix it.

[GWDGuy]

Good Morning Captain... (it is afternoon but I always wanted to say that) okay okay


I am not sure what it could be without maybe looking at the code directly on the server.. If you want I can set up a test location on one of my servers and let you publish it there and see if it is a server or something else..



Let me know..

Robert

[captain]

Robert,
Ok, I could give that a try. Tell me where & how you want me to publish.

[GWDGuy]

The log in information is on its way.. Please let us know if the same thing happens.

Robert

[bud]

Make sure that you have Office Sr1 installed.... It fixes that kind of thing... Otherwise you need to make registry changes...

See FP Include Components and Shared Borders Are Displayed Incorrectly on IIS (http://support.microsoft.com/support/kb/articles/Q298/8/27.ASP)

[captain]

Hi, :woohoo: :woohoo:
It's back up and running like a top. A wobbly top, but with a few a
tweaks as suggested by all of you, the problem shouldn't return.
It turns out most of the problem was at the host server. (Client should have picked GWD Hosting) Once they took care of problems on their end, poof, just like magic it was back up.
Thank you everbody for your help and great suggestions.
You went beyond the call. :up:

[Sculptor]

Bill,

I had the same problems. I upgraded FP2000 to FP2002 and my host didn't support the FP2002 Extensions. I reloaded the site
with FP2000 with and without the FP extensions and in either case my site had the identical problems you described.

I spent days atempting to get it back, but I've had to pull my site down and rebuild the whole thing, this time being sure that the FP2002 extensions are turned off from the get go.

Sorry I don't have better news,

Mark Levin

www.marklevin.com
(My site only has an "under construction page now until I rebuild the whole thing)

marklevin@marklevin.com

[bud]

Ok, I'll try this again...

Microsoft has acknowledged this to be a problem in FP 98, FP 2000 and FP 2002...

The fix can be seen here FP Include Components and Shared Borders Are Displayed Incorrectly on IIS (http://support.microsoft.com/support/kb/articles/Q298/8/27.ASP)

This problem can be taken care of in two ways...
(FP2002) install the Office XP service pack #1
The second way is to edit the registry, which the
above article explains...

Note: FrontPage is part of the Microst Office Family of products...
Hence why the Service pack works...

Providers hosting FrontPage Webs with linux need to address this issue
by following this article...
FP: Include Component and Shared Borders Are Displayed Incorrectly on UNIX Servers (http://support.microsoft.com/default.aspx?scid=kb;EN-US;299360)

I know this works for Windows 98 running PWS, Windows NT running IIS 4.0, Windows XP Pro running IIS 5.1 and Windows 2000 running IIS 5.0....

Seen it, been there, dun it...

[Sculptor]

Bud,

Thank you. In a way this was a small blessing. I needed somthing to motivate me to redo my site and this was the catalyst, but I'm glad to know the solution to the problem. This time I have the FP extensions off and am not using shared boreders, themes, ets.

Thanks again,

Mark Levin

[bud]

Mark

I run Windows 2000 with the FrontPage 2002 extensions...

Most of my clients use FrontPage 2000...

Now in todays environment... Finding a piece of wood is getting to be a rareity... So knock on wood... I have never.... I mean Never had to reinstall FrontPage Extensions because a client was not using FrontPage 2002... Nor have I had an instance of a client not being able to maintain there web using FrontPage 2000... Note: FrontPage 2000 will not be able to manage components intended for FrontPage 2002, In the event that another member who does possess FrontPage 2002 publishes to a web that is managed mainly with FrontPage 2000. The components designed for 2002 that were added by the other will not be affected... However this statement does not mean that a client with FrontPage 2000 can't render the component inopperable or remove it...

The FrontPage Webs here are just that... FrontPage Webs...

With the exception of the described anomily... Most upsets to the server comes from publishing incorrectly... My Dedicated FrontPage server (hence: the name FrontPage.Kmoraine.com (http://frontpage.kmoraine.com)) here will only accept FrontPage HTTP posts... It may seem a bit harsh to disallow FTP... But when the restriction prevents the possible corruption and distruction of your hard work, not to mention the time and effort you put forth.... It's a well worth restrcition...

If FTP is needed that badly... FrontPage does allow you to open your site live from the server. At which time you can drag any file from your system to the folder list within FrontPage which will spontaneously upload that file to the server... Giving you trully WYSYWIG control over your web... So the question then is "Why do you need FTP?"

I have been hosting FrontPage Webs since FrontPage's first release... I support everything intended for the Windows Environment with the exception of Team Services and the Office Extensions...

So with all of this... The host chosen makes a difference...