Can't save shared menus!

[Dennis P. Harris]

AAARGH! Prototyped a web site for the boss on my Windows 2000
machine at home using Frontpage 2000. Everything worked fine,
including the shared menus (navigation bars). Uploaded to the
site, it worked OK, he liked it, said it was a great start but
needed more content and more pages.

Since I need to work on it at the office during the workday, I
burned a copy of the entire Web to a CD, along with the
customized theme file, and installed in the "My Webs" directory
created when I installed Frontpage 2000 in my WinXP machine at
the office.

The shared menus all went to hell. Deleted shared menus from all
the pages, removed all the pages from the Navigation view,
unlinked all style sheets, changed to "No theme". Saved
everything, exited, deleted CMDUi.prf file, and started over.

Added shared menus back in and it looked OK in "Normal" view ---
used graphic buttons from my custom theme, etc. But...

Even when I save the page, recalc links, and publish it, the top
banner displays OK, but there is NO MENU.

I reopened the page file on my local machine, and MENUS HAVE
DISAPPEARED. So I went back to only index.htm in the Navigation
view, recalculated links, added one child page, and set up the
menus first on index.htm, saved it, looked at the source in my
favorite text editor. The Javascript code for the menu buttons
was there. Opened the child page, set up menu buttons there by
right clicking and editing nav bar properties, saved, it, checked
the code in text editor, nav bar Javascript was there. Re-opened
index.htm AND THE NAV BAR JAVASCRIPT HAD DISAPPEARED. I had
never re-opened the index.htm file after saving it, so how could
it have been changed, and why?

This is driving me nuts! I have spent 2 days googling Google
Groups Usenet archives, googled various FrontPage support sites
for "FrontPage menus/navigation bars/shared menus" and have not
been able to find out why in the hell this is happening. It
can't be a file or directory rights issue on my local hard drive
because I have administrator equivalent rights to the whole
machine.

In the meantime, my boss is getting annoyed that I can't get a
simple 10 page web site up and running. I'm in an small town in
Alaska, and can't just go to a big box computer store and buy a
copy of Dreamweaver instead, or I probably would have already
done so.

Is there some kind of incompatibility between XP & Frontpage
2000? Would an upgrade to FP 2003 fix it? Any ideas on what is
causing this? AAAGH!

A pox on whichever idiot at Micro$oft designed this non-standard
kludge of a website editor!

================================================================
If this was Linux, we'd be there by now!

 

[Rob Giordano \(Crash\)]

You should order Dreamweaver right away, after a few months you'll get the
hang of it.
'Tis a poor craftsman who blames his tools.

oh, btw...all you have to do from home is open the online website with FP
(from home) then Publish it down to your machine...piece o'cake.


| AAARGH! Prototyped a web site for the boss on my Windows 2000
| machine at home using Frontpage 2000. Everything worked fine,
| including the shared menus (navigation bars). Uploaded to the
| site, it worked OK, he liked it, said it was a great start but
| needed more content and more pages.
|
| Since I need to work on it at the office during the workday, I
| burned a copy of the entire Web to a CD, along with the
| customized theme file, and installed in the "My Webs" directory
| created when I installed Frontpage 2000 in my WinXP machine at
| the office.
|
| The shared menus all went to hell. Deleted shared menus from all
| the pages, removed all the pages from the Navigation view,
| unlinked all style sheets, changed to "No theme". Saved
| everything, exited, deleted CMDUi.prf file, and started over.
|
| Added shared menus back in and it looked OK in "Normal" view ---
| used graphic buttons from my custom theme, etc. But...
|
| Even when I save the page, recalc links, and publish it, the top
| banner displays OK, but there is NO MENU.
|
| I reopened the page file on my local machine, and MENUS HAVE
| DISAPPEARED. So I went back to only index.htm in the Navigation
| view, recalculated links, added one child page, and set up the
| menus first on index.htm, saved it, looked at the source in my
| favorite text editor. The Javascript code for the menu buttons
| was there. Opened the child page, set up menu buttons there by
| right clicking and editing nav bar properties, saved, it, checked
| the code in text editor, nav bar Javascript was there. Re-opened
| index.htm AND THE NAV BAR JAVASCRIPT HAD DISAPPEARED. I had
| never re-opened the index.htm file after saving it, so how could
| it have been changed, and why?
|
| This is driving me nuts! I have spent 2 days googling Google
| Groups Usenet archives, googled various FrontPage support sites
| for "FrontPage menus/navigation bars/shared menus" and have not
| been able to find out why in the hell this is happening. It
| can't be a file or directory rights issue on my local hard drive
| because I have administrator equivalent rights to the whole
| machine.
|
| In the meantime, my boss is getting annoyed that I can't get a
| simple 10 page web site up and running. I'm in an small town in
| Alaska, and can't just go to a big box computer store and buy a
| copy of Dreamweaver instead, or I probably would have already
| done so.
|
| Is there some kind of incompatibility between XP & Frontpage
| 2000? Would an upgrade to FP 2003 fix it? Any ideas on what is
| causing this? AAAGH!
|
| A pox on whichever idiot at Micro$oft designed this non-standard
| kludge of a website editor!
|
| ================================================================
| If this was Linux, we'd be there by now!
|
|

 

[Dennis P. Harris]

'Tis a poor craftsman who blames his tools.

"tools" kludged by micro$oft are not usually craftsman-level
tools, in my experience. compilers made by other companies
generate smaller executables without all the M$ bloatware, and
they comply with the language specs. only M$ keeps trying to
come up with proprietary languages (C#? gimme a break!) and
tools that lock you into their OS and tools.

frontpage was not my choice, i was told i had to use it.

oh, btw...all you have to do from home is open the online website with FP
(from home) then Publish it down to your machine...piece o'cake.

did you actually read my post? the *original* website was done
on my home machine, it's the office XP machine that seems to have
the problem.

next time, read the entire post before jerking your knee.

 

[Dennis P. Harris]

oh, btw...all you have to do from home is open the online website with FP
(from home) then Publish it down to your machine...piece o'cake.

actually, i did the opposite, uploaded the original website from
my home machine and then downloaded to my office machine.

uploading and downloading the site is NOT the problem. the
problem is on my office machine where the menus are NOT being
saved when i create shared menus after they have been added to
the navigation page.

 

[Rob Giordano \(Crash\)]

Are you Publishing via the http:// method?

The easiest way is to publish it to the online server from your home or
office machine (whichever web is working correctly) drive to the office and
Publish it from the server to the office machine (or vice versa). This
requires that the server have FP extensions installed and working.

Otherwise you would Publish locally to a folder outside of the local web,
then burn that to CD, then copy it off the CD at work and remove the
read-only attributes from the files.


| On Thu, 14 Sep 2006 16:15:02 -0700 in
| microsoft.public.frontpage.client, "Rob Giordano \(Crash\)"
|
| > oh, btw...all you have to do from home is open the online website with
FP
| > (from home) then Publish it down to your machine...piece o'cake.
| >
| actually, i did the opposite, uploaded the original website from
| my home machine and then downloaded to my office machine.
|
| uploading and downloading the site is NOT the problem. the
| problem is on my office machine where the menus are NOT being
| saved when i create shared menus after they have been added to
| the navigation page.
|
|