Clash with FrontPage Webbots?

[Murray]

I tried to set up the Upcoming Events script and ran into a few challenges with FrontPage.

I have had some challenges getting the scripts to work with FrontPage. It will not allow me to use <ul> tags; they are changed to <table> tags, and moves the script code aroung for me.

The calendar works great other than the "500" error when creating or updating calendars after I synchronized with my hard drive, but the changes still take place. I presume that this is a FrontPage issue as well.

Thanks,

Murray

[cbuckmore]

I use Frontpage for building our websites and have never encountered that problem. What version of Frontpage do you use? I use FP 2003.
Take a look at http://www.bgcwf.org

Thanks,
Craig

[Murray]

Hi Craig,

I use FP2003. I ended up frustrated with it, and completely baffled as to why it kept changing the tags to table tags. I can't figure any setting in FrontPage that would cause that. I am using a template that I purchased, but can't figure anything there that should cause it either.

I will be really busy the next couple of weeks. I may give it another try when I get some free time. There are a couple of other anomalies I can't figure either, such as the settings for users in calendars, so I may reload everything and start over.

I will let you know if I find anything.

Thanks,

Murray

[cbuckmore]

Hi Murray,

I just though of something that might be causing your grief. FP 2003 has a very good compression system built in. When you publish your work it can actually do a lot of things like HTML Tidy such as whitespace removal and comment removal. It seems to do a quick syntax check too and if it finds anything it attempts to fix it. If you have the settings too aggressive it can actually remove things such as javascript in a commented section. I have seen other interesting behaviors caused by new coding techniques not around at the time the compression program was made. I suggest when you try to publish try different settings for the Remote Website properties Optimize HTML tab. First try with no optimization to see if that solves the problem initially and then you can tweak it from there.

Also don't use the synchronize setting when publishing if you are optimizing the code. I had a few choice words when I killed my FP webbots by synchronizing. FP will remove it's own comments for webbots during publish to go with the minimum required. If it gets synchronized back all of the sudden you can edit your webbots any more because FP doesn't understand then. I have optimization turned on with the option All Other HTML Comments unchecked and I only publish one way keeping my master copy on my system clean.

One other thing you can do to check code is in FP code view right click and choose Reformat HTML. This will restructure the code so it is easier to debug the code and maybe find a out of place tag that is causing your grief.

All in all the FP code optimization works very well, and works completely transparent, when tweaked for you.

Good Luck,
Craig