[Plugin: Custom Content Type Manager] WYSIWYG problems

  • I recently added this lovely plugin to my site, and thus far it’s doing everything that I want except for the WYSIWYG option, and I’m not sure if I’ve missed something. I selected the WYSIWYG option for one of my Custom Fields and finished making my content type, but when I went to the post for that content type to add the information to it, the WYSIWYG editor was not there. There’s a blank space (not even a box, really) that I can add text to, but there are no text-editing options. Do I need to do something else besides just add the WYSIWYG custom field?

    https://www.ads-software.com/extend/plugins/custom-content-type-manager/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Contributor fireproofsocks

    (@fireproofsocks)

    Please provide details: which version of WordPress are you using? Which version of the plugin? And verify that the name of your WYSIWYG field uses ONLY letters: no spaces, no underscores, no numbers, no dashes. WordPress’s support fo the WYSIWYG editor is incredibly poor, so the features there are severely limited, but it should be working at least. I’m guessing that the name of your custom field includes characters that WP considers “unacceptable” in a WYSIWYG field. Can you check? Or attach your exported .cctm.json definition file here (export it under the tools menu).

    Thread Starter ChristyMcD

    (@christymcd)

    I am using WP version 3.3 and CCTM version 0.9.4.5-pl. I gave it the name full_bio, following what I know of WordPress database field name conventions. I can’t do that for a WYSIWYG field?

    Thread Starter ChristyMcD

    (@christymcd)

    I went in and changed the name of the field to take out the underscore, and the WYSIWYG editor worked briefly and now isn’t again. I know very little about WYSIWYG, so I wonder if I’m still missing something.
    It looks like the WYSIWYG editor stops working if I deactivate the main post content box so that only the custom fields show.

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    WP thankfully rewrote the WYSIWYG stuff in WP 3.3 — it’s pretty disasterous prior to WP 3.3, and I had a lot of rewriting to do to make it even remotely functional in WP 3.2. WP’s implementation makes me so mad because it’s so arbitrary.

    Glad it’s working! You need WP 3.3 for the latest version of the CCTM (currently 0.9.5.2), and it does remind users about the problem with the names of the WYSIWYG. I didn’t realize that WP 3.2 was also vulnerable to the “underscore problem”, but I’m glad you got it working. If WordPress starts driving you as crazy as it drives me, MODX is the best PHP CMS that I’ve come across.

    Thread Starter ChristyMcD

    (@christymcd)

    It looks like the WYSIWYG editor stops working if I deactivate the main post content box so that only the custom fields show. I only want my custom fields, so that’s a bit inconvenient.

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    Yep, that’s a known problem with WP’s implementation of TinyMCE in WP version 3.2 and CCTM 0.9.4: you MUST Include the main content block. You’ll have to upgrade to WP 3.3 and CCTM 0.9.5.x to avoid that.

    Thread Starter ChristyMcD

    (@christymcd)

    Oh, I see. If I upgrade to the latest CCTM version, what will it do to the content types I have created? Will it overwrite them so I have to recreate them?

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    No, it won’t overwrite them, but it’s a good idea to export your definitions prior to an upgrade (under the CCTM’s Tools menu).

    Thread Starter ChristyMcD

    (@christymcd)

    Lovely. Thanks for the help! Your plugin is wonderful.

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    Thanks. If you’ve found the plugin useful, donations are always appreciated ??

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘[Plugin: Custom Content Type Manager] WYSIWYG problems’ is closed to new replies.