It should be noted that the TinyMCE for Pods package and plugin only appears to work in 1.9x and up.
However, I have succeeded in getting it to work (sort of) in 1.88 with a caveat which I’m hoping someone will be able to help with.
if wp_default_editor == ‘html’ upon page load, the editor loads in HTML Mode and functions normally.
Upon clicking the Visual button, the wysiwyg editor loads and also works fine, however once you save or even just navigate away from the page while in Visual Mode, nothing works upon the next page load (wp_default_editor == tinymce). Paragraph text does not display in the Visual Editor, you cannot add new text, toggle to html mode, nor save the pod item — however… if you click the HTML and click save, or just refresh, tinyMCE
works functions normally once again (where wp_default_editor == ‘html’).
Insult to injury… this malfunction only rears it’s ugly head in Firefox/MOZ 5x browsers, where it otherwise appears to function normally in others (e.g. Chrome or even IE6). I’m at my wits end with it!
Please, does this ring any bells with anyone out there (Scott?)
In case anyone is interested, this is a bug. While I have been unable to satisfactorily resolve the issue in 1.88, I have discovered that the problem remains in Pods 1.94, under the following conditions…
Given a clean install of WordPress 3.01, where Pods 1.94, and Pods TinyMCE Editor are the only additions/alterations made to the default WP installation, and given the creation of a single pod "Test" with defined fields "Name(txt), File Upload(file), and Description(desc)" TinyMCE will behave as described above IF and when… the file upload field is placed AFTER the paragraph text(desc) field.
Reverse the order, or remove the file upload field and TinyMCE works as expected.
You must be logged in to reply to this topic.