css conflict bug version 1.23

Hi brownleather,

Thanks for reporting that (and getting to the cause of it). It's definitely an interesting challenge because the fieldnames need to have id's but can't conflict with other divs on the page with the same id's.

What I've done for the next version is to add a "field_" prefix to the id value for wysiwygs in the html so it won't conflict. This won't change anything else but will let you name your field "main" without it conflicting with the CSS (because the wysiwyg will use the id "field_name" to reference it).

So, short answer is: fixed for the next version.

Hope that helps, let me know if you need anything else! :)

wonderful,
on a different note, when will cms builder be able to accept content from site visitors? ie though a feedback form

Hi

Glad that worked out for you :).

We actually have a simple little comment form that could work for you. It's your basic run of the mill script that lets you enter your name, email and the comment. It has a captcha to help with spam and an admin that lets you ban IP's.

It's pretty simple but it could work. Let me know what you think :).

Hi brownleather,

There's no ETA for when that will be part of the code generator. If you know a little PHP, though, I'd attached a sample add form that lets you add records. You can use it as a base to build what you want.

Hope that helps!

thanks