| 2:51 pm on Apr 19, 2006 (gmt 0)|
Hello CKilishtof, welcome to WebmasterWorld!
Are you using FrontPage to make the changes?
If not, that is the problem. FrontPage borders function only within a FrontPage environment. I'm sure you probably saw the _vti folders while browsing around the site structure? Those folders contain files that control what is happening with the borders and the FP Extensions on the server.
Which leads me to my next question, are the FrontPage Extensions installed on the hosting server?
One of the things you could do if the above requirements have been met, is to login to the administrative home of that web (at the server) and recalculate the web which should push the changes across all pages.
While you have the web open in FrontPage, go to...
Tools > Server > Administration Home
Under Server Health, select Recalculate the Web.
Is it also possible that your local cache is interferring and you are not seeing the updated pages? An F5 should clear this up.
| 4:29 pm on Apr 19, 2006 (gmt 0)|
Thank you :)
No, I am not using FrontPage to edit the file. I used Visual Interdev to edit the file. (The majority of the pages I work with are ASP.) I guess I will have to see if we have a copy of FrontPage anywhere.
Will openning the file in FrontPage and saving it be sufficient to fix the problem?
I am assuming that the host server is properly configured and has FrontPage Extensions installed since the previous version of the bottom border was working fine. Also the current version of the border is displayed on some pages and the old version is displayed on others. So I am seeing the bottom border just not all pages have the updated information.
| 4:44 pm on Apr 19, 2006 (gmt 0)|
You could try Recalculating the Web. I'm not sure how to get to that area outside of FrontPage. I've outlined the process above while in the FP environment.
Since I've never used Shared Borders, I cannot be 100% sure why you are only seeing some pages being updated. My guess would be is that those pages not being updated maybe reference a different file? I don't know.
Usually a recalculation of the web will clear most, if not all problems with files not updating correctly.
| 4:59 pm on Apr 19, 2006 (gmt 0)|
P.S. My understanding is that for those Shared Borders to work properly, you should be publishing the changes through FPs Publishing interface. Without the Publishing routine, all those _vti files that are utilized to update changes are bypassed and I believe you will have problems.
| 5:14 am on Apr 24, 2006 (gmt 0)|
|My understanding is that for those Shared Borders to work properly, you should be publishing the changes through FPs Publishing interface. |
I haven't found that to be true. I got rid of the FP extensions a while back and now do all my publishing with WS_FTP Pro. My procedure is to:
1) Open the border file and edit it. (For example, the top.htm file or the left.htm file in the _borders directory.)
2) Ftp the edited file and all files that use that border to the server.
It's really pretty simple, and I've never had a problem with shared borders on a site with multiple subwebs totalling 5,000+ pages.
| 5:27 am on Apr 24, 2006 (gmt 0)|
|2) Ftp the edited file and all files that use that border to the server. |
But, doesn't that defeat the purpose of using the shared borders?
I would think just making the change to the shared border and publishing to the web via FPs interface would be much more productive? One file as opposed to however many files are being reference by the borders?
P.S. I believe in this instance, the best way for CKilishtof to make the change would be to follow your #2 advice. ;)
Without the Extensions, the Shared Border concept is null.
| 2:37 am on Apr 27, 2006 (gmt 0)|
|But, doesn't that defeat the purpose of using the shared borders? |
It may not be quite as efficient, but it certainly doesn't defeat the purpose of shared borders. The benefit of shared borders is the ability to change page headings, navigation bars, etc. without doing a search-and-replace on dozens, scores, or hundreds of pages.
|I would think just making the change to the shared border and publishing to the web via FPs interface would be much more productive? One file as opposed to however many files are being reference by the borders? |
When I had the FrontPage server extensions installed, the only way I could reliably update a Web or subweb with FrontPage (short of editing on the server) was to publish all files. So I actually had to publish more files than I do with ftp, because image files (of which I have thousands) were also being republished. (Maybe that's not how things were supposed to work, but they're how things did work.)
I was also concerned about FrontPage exploits after my site got vandalized by a freeBSD hacker in South America.
In any case, I don't change my shared borders terribly often, and when I do, it's normally just on one or two subwebs (not my entire 5,000-or-so-page site). It's no big deal to upload a few hundred html files through my broadband connection, and in some ways it's easier than using FrontPage if I'm changing several subwebs, because I can queue uploads for multiple directories in WS_FTP Pro.