The disappearing content trick | FP2002/2003 comments

[Sue Smith]

I have experienced this on FP2002/2003: after publishing,
the body content of the page has been deleted. Not just a
display problem or refresh problem or a coding error - the
code has been deleted from the page on the local drive and
the remote server. I think I have discovered that the
culprit is shared borders, because when I completely
remove the shared borders, I can hold on to my content.
This has occurred on 3 different webs over a period of a
few months.

Hasta la vista shared borders - I published a new website
last week using the dynamic template feature and found it
to be much more reliable and I think I am going to cross
my fingers and convert the most recent problem child site
over to the new templates. (After backing it up a few
times, that is.) The new FP2003 site was a simple one and
I was able to create an attractive menu bar with the
interactive buttons and place that with some graphics and
stuff in the non-editable region of the page. Works well
and very reliably. Not flakey or touchy like the custom
link bars based upon the navigation view.

I was very disappointed that there was no easy way to do
JS drop down expanding menus in FP2003 as I thought from
all the hype. I took a look at the how-to article. I will
keep my AllWebMenus designer/compiler, thank you, very
easy to setup, update and very reliable. And cheap.

Cheers
Sue Smith

 

[Stefan B Rusynko]

Agree the Dynamic web templates are more powerful than shared borders

But your problem w/ shared borders was probably broken html tag pairs which prevented FP from creating and saving the tables
required for the shared borders - validate your html on your pages
--




| I have experienced this on FP2002/2003: after publishing,
| the body content of the page has been deleted. Not just a
| display problem or refresh problem or a coding error - the
| code has been deleted from the page on the local drive and
| the remote server. I think I have discovered that the
| culprit is shared borders, because when I completely
| remove the shared borders, I can hold on to my content.
| This has occurred on 3 different webs over a period of a
| few months.
|
| Hasta la vista shared borders - I published a new website
| last week using the dynamic template feature and found it
| to be much more reliable and I think I am going to cross
| my fingers and convert the most recent problem child site
| over to the new templates. (After backing it up a few
| times, that is.) The new FP2003 site was a simple one and
| I was able to create an attractive menu bar with the
| interactive buttons and place that with some graphics and
| stuff in the non-editable region of the page. Works well
| and very reliably. Not flakey or touchy like the custom
| link bars based upon the navigation view.
|
| I was very disappointed that there was no easy way to do
| JS drop down expanding menus in FP2003 as I thought from
| all the hype. I took a look at the how-to article. I will
| keep my AllWebMenus designer/compiler, thank you, very
| easy to setup, update and very reliable. And cheap.
|
| Cheers
| Sue Smith