Error initializing menu object (wa.generate.getMenuSettingsObject)

[Nathon Jones]

When I click "Finish" the following error pops up about halfway through build process:

Error initializing menu object (wa.generate.getMenuSettingsObject):
TypeError: includesFolderArray[1] has no properties

Once ok'ed it takes me back to the page with none of my updates implemented.
Has anyone seen this error before?

Thanks.
Nathon

[Ray Borduin]

Have you tried deleting your winfilecache .dat file?

I am not familiar with this error. Please post a support incident so somebody can investigate this with you further.

[Nathon Jones]

This is the full error, Ray:

Error initializing menu object (wa.generate.getMenuSettingsObject):
TypeError: includesFolderArray[1] has no properties

It seems to appear, at random, whenever I make any changes to the menu. Whilst it "builds" the changes into the menu, the error pops up. I usually end up having to start from scratch!

EDIT: I've just rebuilt this menu from scratch. Closed, reopened DW, and I'm getting the same error again! This is clearly a bug in the software.
I've tried deleting the WinCache file, but it didn't make a difference. This is really starting to slow my workflow down. Any ideas?

[Nathon Jones]

Can anyone help me with this?

I've just completed a third rebuild of this menu and I'm just going round in circles now.
I've deleted the WinCache file, I've renamed "Configuration" to "ConfigurationOLD" and restarted DW...I'm all out of options!

Can anyone, at least, identify what this error means?

"Error initializing menu object (wa.generate.getMenuSettingsObject):
TypeError: includesFolderArray[1] has no properties"

Hope someone can help. Cheers.
Nathon.

PS. I have submitted a support ticket, but this update might be useful, anyway, should anyone else be experiencing this error.

[Ray Borduin]

Make sure you include your files so they can reproduce the error since this is not a known issue.

You will have to wait for support since it will require reproducing and debugging to find the cause. Does it happen with a new menu on a new page? What about when adding the same menu to a new page?

[Nathon Jones]

Hi Ray,

Yes, I included my files, at the time of the error. I've since rebuilt the entire menu, following yet another reinstall, although I simply couldn't uninstall CSSMenuWriter at all, it just wouldn't let me.

Anyway, I completely reinstalled over the top, this being about the 4th time I've done that, and, touch wood, the error isn't back yet.

I am finding CSS MenuWriter to be quite unreliable, at the moment. I'm hoping that some clarification on what that error is will pin-point what my problem has been.

Thanks again.
Nathon.

[Ray Borduin]

Unless they can reproduce it they probably won't be able to tell you. See if it comes back up and what you are doing when it does. The key to discovering the way to fix any problem is discovering the cause, which means being able to reproduce it reliably or at least semi regularly following a series of steps.

[nickj]

I'm having the same error , I've read both forum items and find tha there is no clear answer. Has anyone solved this issue? I don't want to have to re-load every extension, re-activate and then find that was not a solution!

Did the support people solve this issue??

[pizzicaluna381282]

I'm having the same error!

[Ray Borduin]

I have created a support incident so that we can work with you directly to diagnose the problem. Please update the support incident with your contact information and we will contact you directly.

If anyone else is currently experiencing this problem and has time to work with our support staff, please reply to this thread and I will open an incident for you. Once we can contact you and reproduce the problem we should be able to find a solution.

[mgreg378555]

Using CS5 i have the same problem.

I am unable to insert menu from custom layounts when using either SiteAssistPro108 or SiteSculptor100

The error is as described above

Error initializing menu object
(wa.generate.getMenuSettingsObject):
Error: getDocumentDOM: Argument number 1 is invalid

[Ray Borduin]

I have created a support incident so that we can work with you directly to diagnose the problem. Please update the support incident with your contact information and we will contact you directly.