New TinyMCE Editor (w/ bug fixes!)
July 27, 2009 at 12:20 pm #158657
BUG FIX!!! Links are getting replaced with ../ instead of the domain it was linked to. The fix is using this code on step 3:<pre>/*
elseif (‘desc’ == $coltype)
<textarea class="form desc <?php echo $name; ?>" id="desc-<?php echo $name; ?>"><?php echo htmlspecialchars($value); ?></textarea>
theme : "advanced",
mode : "exact",
elements : "desc-<?php echo $name; ?>",
convert_urls : false,
width : "100%",
height : "250",
}</pre>July 27, 2009 at 2:36 pm #158658
Works for me! Thanks!September 9, 2009 at 3:13 pm #158659
Unfortunately, I’m getting problems with this. Yes, these code changes do let me use TinyMCE with Pods, but at the same time, it ruins the dialog boxes for TinyMCE Advanced on the ‘Edit Page’ page.
The problem is in the changes that we’re making in init.php. I’m not sure how to fix it though.
Does anyone have any idea of a solution?September 9, 2009 at 4:08 pm #158660September 17, 2009 at 2:43 pm #158661
@ctiggerf – I had that issue too, the best I could do so far was to just get the editor itself working. I’ll eventually get into getting the rest going.
@logikal16 – I’ll look into making this an input helperSeptember 27, 2009 at 4:02 pm #158662
Beware, I encountered several problems after going through these steps installing TinyMCE Editor. The same thing occured after deciding to give it a fresh start. I still encountered the same problems.
October 4, 2009 at 7:03 pm #158663
- Any "date" column created will not appear the calendar onclick when adding an item.
- The code column appears as a pick column when adding an item.
- If more than 1 file upload column is in a pod, the second column completes itself with the same value as the first file column when adding an item.
I prefer nicEdit to TinyMCE. It’s thinner and has less mess to go through to fix things. I was glad to see that Pods uses nicEdit by default.
However, while on that topic, nicEdit inside Pods has some quirks. For instance, randomly nicEdit wants to show me a 100px width. I refresh and it displays properly. Also, the font menu is cut off, and the "http" in the Add Image dialog is cut off where I only see the tops of each character. (Note I’m using FF3 on Ubuntu Linux, but I’ve also seen some of these problems on Windows Vista in the various browsers like IE, Opera, Safari, Chrome, and FF.)October 5, 2009 at 3:44 am #158664
Thanks for that code. Is the plan for Pods in the future to move to TinyMCE as the editor of choice?
Also, if I patch my Pods plugin with this code, what would you recommend as the best way to prevent a new Pods update from blowing it away? Or will the next official update contain these patches anyway?October 5, 2009 at 10:54 am #158665
Regardless of which editor is the default, both will be available.
One way to preserve Pods from overwriting local changes is to disable the plugin update check. http://wordpress.org/extend/plugins/disable-wordpress-plugin-updates/December 3, 2009 at 5:33 pm #158666
Hi… has anybody tried this with the latest version of pods? It doesn’t seem to work on later versions at all. Which makes me want to cry like a little girl. Any ideas?January 11, 2010 at 3:38 am #158667
I’m working on a new revision of this, and so far my testing is working out greatly. I’m getting an issue related to multiple editors on the same page though, I’ve posted it to the WordPress Trac:January 11, 2010 at 10:59 am #158668
@scott & @logikal: i´m (still) completely with @volomike. could tinymce stay as input-helper package or might you think about offering an option to choose between nicedit/tinymce?January 13, 2010 at 4:38 pm #158669January 14, 2010 at 12:00 am #158670
WP 2.9.1 definitelyFebruary 25, 2010 at 9:48 am #158671
it isn’t working anymore in the newest version of Pods with the newest version of WordPress, am I right?
The textbox doens’t appear, (the menu do) and the bottons doesn’t do anything.
You must be logged in to reply to this topic.