error when modifying custom menu

7 posts by 2 authors in: Forums > CMS Builder
Last Post: February 1, 2008   (RSS)

By loccom - January 31, 2008

hi

I created a custom menu, renamed the custom "Section Name" and "Table Name" I then went to edit "Content" label so that i have a WYSIWYG instead of a ordinary content text box and got a mysql error

see screenshot.
Attachments:

cmsscreenshot.jpg 84K

Re: [steveo] error when modifying custom menu

By loccom - January 31, 2008

to add to this it only seems to happen if you haved edited the table name and title.. then try and edit the content field.

Also to add to that.. when i try and edit the "field height" to say 150 then go and create the page the WYSIWYG field stays at default and not set to 150

hope this makes sense

Re: [steveo] error when modifying custom menu

By Dave - January 31, 2008

What did you rename table to?

And with the wysiwyg field height, do larger values (eg: 400) work?

These are both working locally for me so if you can help me recreate them locally we can get you fixed up asap.
Dave Edis - Senior Developer
interactivetools.com

Re: [Dave] error when modifying custom menu

By loccom - January 31, 2008

hi dave

i renamed the table to "porterhouse-index"

i cannot change the values on the on the wysiwyg anymore as i get the errors.

Re: [steveo] error when modifying custom menu

By Dave - January 31, 2008

Try "porterhouse_index" with an underscore instead of a dash. I think 'index' is a reserved mysql keyword and it's getting confused with the dash.

If that's the case I'll add some extra error checking or other code the next version to avoid that in future.
Dave Edis - Senior Developer
interactivetools.com

Re: [steveo] error when modifying custom menu

By Dave - February 1, 2008

Ok sounds good. The wysiwyg (tinyMCE) may have some minimum sizes or other restrictions. We're just passing the height value to tinyMCE. Feel free to post again if it gives you more troubles.

As for the dashes in tablenames, I'll either add some error checking code for that to the next version or find a way to allow it so it doesn't produce an error.

Thanks for the error report!
Dave Edis - Senior Developer
interactivetools.com