Can't Make Proper NAME field for WYSIWYG section

[GoogleCodeExporter]

What steps will reproduce the problem? (Be specific enough so that someone
else can make the plugin fail for themselves. Remember: if the issue can't
be fixed if it can't be reproduced!)
1.
2.
3.

What is the expected output? What do you see instead?

want to create NAME fields with underscores and numbers like before

I even tried duplicating a WORKING one. still doesn't work it ERASES the 
underscores and numbers. THESE ARE REQUIRED (especially the numbers)

EXAMPLE:
under NAME I want it to be new_detail_01
but it ERASES the underscores and does just newdetail and will ONLY SUBMIT when 
there are NO underscores or numbers. 

WAS NOT A PROBLEM BEFORE.
DOES NOT OCCUR WHEN CREATING NEW FIELDS.

ERROR:

"There were errors in your custom field definition.
    Due to WordPress limitations, WYSIWYG fields can contain ONLY lowercase letters."

Does the problem continue if you disable all other plugins? (Conflicts
between plugins are easily the #1 cause of errors, so it's important to
isolate the issue):

YES STILL AN ISSUE

Please copy and paste the system information that appears in a yellow
textarea when you click on "Report a Bug" on any CCTM admin screen (this
includes the version of the
plugin, the version of PHP, the version of MySQL, a list of other active
plugins etc.):

*SYSTEM INFO* 
------------------------ 
Plugin Version: 0.9.6.7-pl
WordPress Version: 3.4.2
PHP Version: 5.2.17
MySQL Version: 5.5.29-log
Server OS: Linux
------------------------ 
ACTIVE PLUGINS: 
------------------------ 

Original issue reported on code.google.com by ch...@everplexmedia.com on 24 Jan 2013 at 8:45

[GoogleCodeExporter]

I also tried upgrading to the latest one, still does not work
I also tried upgrading to the dev one, still does not work.
If I make a TEXTAREA rather than a WYSIWYG, then it works. BUT I NEED TO BE 
ABLE TO USE THE WYSIWYG SECTION.

URGENT!!!

Original comment by ch...@everplexmedia.com on 24 Jan 2013 at 9:02

[GoogleCodeExporter]

See the notice the CCTM printed for you?  "Due to WordPress limitations, 
WYSIWYG fields can contain ONLY lowercase letters."  I went to the trouble of 
customizing that error message precisely to avoid getting a bug report like 
this, so please read those notices, and please, understand marking a bug report 
as  "URGENT" does not magically make me have more time in my day to deal with a 
problem.  Most features/bugs get implemented inside of paying contracts -- 
that's just the only practical way I can work.

For some reason, underscores and numbers are not allowed as fieldnames for 
WYSIWYG (but only for those fields).  WP made some progress by making a 
function that helped generate the WYSIWYG editor, but for reasons too insane 
for me to comprehend, there are limits on the characters that can be used.  
Supporting WYSIWYG fields has been extremely frustrating for me because WP 
keeps changing the JS libraries used.  It's stuff like this that makes me hate 
WP because on many levels its code is a mess.   

Your options here are to 

1. Use the label field to change the visible label of the field (e.g. 
name=lowercaseonly, label="Low3r-C@s3 Only!!!" 

2. file a bug in the WordPress bug tracker and hope they take it seriously

3. find a different system entirely.  I would recommend MODX or Expression 
Engine as examples of PHP CMS's where the code was sensibly architected.

Sorry I can't help here.

Original comment by ever...@fireproofsocks.com on 24 Jan 2013 at 4:50

• Changed state: WontFix

[GoogleCodeExporter]

 why did you change it??  it worked before! I  have working ones  but now I can't even edit them  because you changed it and now it gives this error!!

Original comment by ch...@everplexmedia.com on 24 Jan 2013 at 5:08

[GoogleCodeExporter]

 IT WORKED  BEFORE AND I EVEN HAVE CURRENTLY WORKING ONES FROM BEFORE YOU BROKE IT AND REFUSED TO FIX.

Original comment by ch...@everplexmedia.com on 24 Jan 2013 at 5:09

[GoogleCodeExporter]

I've had to change this field many times because WP changed their JS libraries: 
these fields have broken repeatedly with different versions of WP. If something 
from before is working, it's only working in a limited sense -- maybe that's 
fine for what you're doing, but I can't keep partially broken solutions in the 
code base.  If you need that particular functionality, then use an older 
version of WP and an older version of the plugin, or find a different CMS to 
use.

Please, do not get upset with me: I do not tolerate it.  This is a bug-tracker, 
not a forum for you to berate me.  I have spent a lot of time writing this 
software and maintaining it for the community.  It's not perfect.  It has bugs. 
 I'm sorry it's not working for your particular case, but the problems here are 
bigger than your particular use case.  If you can't channel your ire into 
something constructive, please find different software to use.  My days are 
stressful enough as it is.

Original comment by ever...@fireproofsocks.com on 24 Jan 2013 at 5:25

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Issue 450 has been merged into this issue.

Original comment by ever...@fireproofsocks.com on 24 Jan 2013 at 5:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Please take the time to read my responses: the cause of this problem is a WP 
problem that I cannot fix.

Original comment by ever...@fireproofsocks.com on 24 Jan 2013 at 5:31

[GoogleCodeExporter]

 can't you get someone to work on it regularly? Or make open-source so people can fix issues that you  simply don't feel like fixing? Or make a donate version so that users can be sure the plugin won't just stay broken one day when you merely decide you don't feel like fixing it anymore?

Original comment by ch...@everplexmedia.com on 24 Jan 2013 at 5:33

[GoogleCodeExporter]

 It's clearly not a Wordpress problem since it IS working on WYSIWYG custom types that already existed before you deleted the working code

Original comment by ch...@everplexmedia.com on 24 Jan 2013 at 5:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

If you want to edit the code, see the save_definition_filter() inside the 
fields/wysiwyg.php file.  As I said, enabling numbers and underscores caused 
problems with the JS code in areas, but you're welcome to make any changes you 
want: the plugin is already open-source (read the license).

Original comment by ever...@fireproofsocks.com on 24 Jan 2013 at 5:45

[GoogleCodeExporter]

Perhaps you can provide better documentation and tell us what JavaScript areas 
it breaks and what exact code to look at, so that we don't have to guess.  
Perhaps you can document to the public any issues you're having trouble with so 
that the plugin can be fully supported.  Thank you.

I would troubleshoot with you but at the moment I have too many things going on.

Original comment by ch...@everplexmedia.com on 24 Jan 2013 at 5:57

[GoogleCodeExporter]

For now I just changed the wysiwyg fields to textarea, but this is not an 
acceptable permanent solution. Looking forward to updates and bugfixes.

Original comment by ch...@everplexmedia.com on 24 Jan 2013 at 6:00