edit menu on Main.dwt.php

I'm trying to edit the menu on the main template, and have followed these instructions:


To edit your PowerStore navigation in CSS Menu Writer, you will need to follow these steps:

1. In your PowerStore files, navigate to the CSSMenuWriter\cssmw_admin directory.
2. Select menustyle.xml and press Ctrl (Cmd) + C to copy.
3. Navigate to the CSSMenuWriter\cssmw_home directory.
4. Press Ctrl (Cmd) + V to paste this file to this location.
5. In Dreamweaver, open the Main.dwt file from the Templates directory.
6. Click once on the menu, choose Edit from the CSS Menu Writer Properties inspector.



When I try to edit the menu, CSS Menu Writer displays splash screen, then this window:


"The database connection(s) required for this content preset do not exist in this site. Please create the following connections to use this preset:

Connection: toJSONString

Table: prototype
Columns:

Table: toJSONString
Columns: prototype"


When I press OK on this window (dialog box), I am in a loop of this window reappearing. I then have to shut down dreamweaver with Ctrl-Alt-Del.

Any ideas?

Thanks,
Robert

This appears to be a problem with the connection settings. Try creating a blank page and adding a DW recordset using that connection. Maybe that will give you a better error rather than crashing.

Ray:

Thanks for the reply.

At this moment, there is no connection to "toJSONString". The only connection that I have established is the localhost connection that is included with the powerstore files. I don't know what "toJSONString" is, and, more important, why it is being asked for when I try to edit the menu on the template file.

The only databases available to me are the database created for powerstore, and the two other default databases with my mysql server. There is no "toJSONString" database to connect to, much less those tables.

To be clear, the localhost connection is fine, I can see all of the tables, etc.

When you ask me to create a DW recordset using "that connection", do you mean the localhost connection or the non-existent "toJSONString"?

In the interest of clarity, I can edit the menu styles, but can't edit or change the menu itself.

Was I supposed to set up this "toJSONString" at some point in setting up the files for powerstore (I have pored through the documentation, and can find nothing)? And if so, how do I do it now?

I'm obviously in over my head and any help will be appreciated. I'm having no problem editing the css and other html elements, but the database work is new to me, which is why I chose Powerstore as an option for our new online store. At this point, I can't edit the menu in powerstore.

Again, thanks for your help.

Robert

I've never seen this error, so I was assuming toJSONString was something you had added. As far as I know that is never used in our extension, so I'm at a loss as to where that error is coming from. Do you have other extensions installed that might be causing a conflict?

I just did a search on the web for "Dreamweaver toJSONString error" and found some posts implying this might be another winfilecache .dat error. Try deleting your winfilecache with DW closed and it may correct this problem.

Resetting the winfilecache didn't change anything.

I then disabled the greater majority of my installed extensions, leaving only those from Webassist and PVII.

At this point, I'm happy to report that I can edit any menu.

Before I disabled the other extensions, I could create a "new" menu and edit it with no problem. When that editing window opened, it also listed the other two menus included in the powerstore2 installation. I could edit the first powerstore menu listed, but clicking on the second menu brought up the "toJSONString" loop, and I was done.

So, bottom line, evidence points to another extension, and if I ever have a half a day to do nothing but open and close dreamweaver and the extension manager, then I'll do the research. If you are curious about the list of now disabled extensions, I can list them for you. As to how the "toJSONString" problem is triggered, I have no clue. You're the coder, not me.

I really appreciate your input.

Thanks,
Robert

If you see the error again, then you will know by the extension you installed that triggers it. I don't think it is one of ours, but be sure to let us know if it turns out to be somehow.