PDA

View Full Version : MenuWriter2 mess


glmcps295424
04-16-2009, 04:33 AM
Had issues with MenuWriter2 ( newer themes didn't play nice with buttoned up layout) and caused problems on existing site which has two templates and two menus ( separate one for admin area) ....

so removed MW 2 and installed original menu writer.

now if I use data assist to create a set of pages <wasscdeletetemp> is inserted throughout the results page creating a bit of a mess. The other pages fail to work but haven't got into that yet.

Will stay with MenuWriter 1 for the time being but is there something I'm missing when I reinstalled it? do I need to reinstall other WA extensions?

using DW CS3, on Win XP all extensions are latest available

Suggestions?

Gregg

Ray Borduin
04-16-2009, 08:58 AM
I would like to find out more about the problem so that we can address it. Do you have an example of the problem that MWv2 was causing?

I will forward this to the engineer that worked on MWv2. He will probably recognize what would cause this issue and I can get back to you when I hear from him.

glmcps295424
04-16-2009, 09:27 AM
Because it's been removed I don't have an example to show. One of the symptoms was that using the button up theme and one of the new taller menu choices , the left side bar got pushed all the way to the right. CSS issues?

I have since uninstalled Data assist and reinstalled it. ( was and is the latest version)

When I use data assist I get the following error:

Error Inspecting the selection:
Type Error: document. editLayer.document.contentButton has no properties

Obviously am dead in the water at the moment.

Any suggestions appreciated,


Gregg

caricatu310873
04-16-2009, 09:46 AM
Had issues with MenuWriter2 ( newer themes didn't play nice with buttoned up layout) and caused problems on existing site which has two templates and two menus ( separate one for admin area) ....

so removed MW 2 and installed original menu writer.

now if I use data assist to create a set of pages <wasscdeletetemp> is inserted throughout the results page creating a bit of a mess. The other pages fail to work but haven't got into that yet.

Will stay with MenuWriter 1 for the time being but is there something I'm missing when I reinstalled it? do I need to reinstall other WA extensions?

using DW CS3, on Win XP all extensions are latest available

Suggestions?

Gregg

I was afraid of this. Here we go again with CSS Menu Writer problems.
:(

Ray Borduin
04-16-2009, 10:11 AM
It looks like there were files that were not marked as shared properly so removing mwv2 removed a bunch of shared files.

We will be updating MW v2 later today or tomorrow to address this important issue.

You can fix it immediately by reinstalling extensions that exhibit this problem. DataAssit may be the only one necessary to update.

glmcps295424
04-16-2009, 10:29 AM
Sorry, Data Assist can't be the only one since I have already reinstalled it and the problem persists.

Will remove and reinstall all extensions .

Have always wondered if there is a preferred order when doing this.

Suggestions,

Gregg

Ray Borduin
04-16-2009, 10:40 AM
If you are doing all of them... Delete your configuration folder.

It will eliminate 90% of the time which is spent uninstalling.

glmcps295424
04-17-2009, 08:34 AM
I removed all WA extensions , reinstalled and registered each (13 of them)

tried to create a totally new site and on edits to pages I still get this error

Error Inspecting the selection:
Type Error: document. editLayer.document.contentButton has no properties

because of other extensions installed it wasn't practical to remove config folder as suggested.

Suggestions?

Did not install CSS Menu Writer 2.

Regards.

Gregg

Ray Borduin
04-17-2009, 08:36 AM
Post a support incident and include your phone number. Then post back here with your incident number. I'll give you a call and help you debug this issue.

glmcps295424
04-17-2009, 09:59 AM
Ray,

This will have to wait til Monday. I'm gone the rest of the day.
I'll post the incident Monday am , and post number here. I'm on eastern time
so you'll see it when you get in Monday.

Thank you,

Gregg