Tim Reeves
Forum Replies Created
-
Forum: Reviews
In reply to: [TinyMCE Custom Styles] Works greatHi @lorinc,
thanks for the high five! You are right, one can use it change the appearance of standard elements in the editor. But there are other plugins with that as their special purpose, e.g. tinyWYM Editor (also adds editing capability!) or TinyMCE VisualBlocks.
Note that my plugin harmonises well with several others to create a really comprehensive upgrade of TinyMCE. Here is a detailed description of how to put all these plugins together and use the resulting interface (in german).
Cheers, Tim
Forum: Reviews
In reply to: [TinyMCE Custom Styles] StunningThanks so much, @minoglow! I found the original version a few weeks ago, and like you I thought “this is exactly what so many of us need”. Since it did not work properly and the original author had abandoned it, but I needed it to work reliably as a basis for my future WordPress projects, I forked it.
As you can see in the Changelog of the current version, I have noted several TODOs. But I’m afraid I don’t have the capacity to extend the plugin to other editors like CK. If anyone else can help with that, I’m glad to cooperate!
Tim Reeves
Forum: Reviews
In reply to: [TinyMCE Custom Styles] breaking visual editorAh yes, now that very well may be – I have never used MultiSite so have no experience / no sandbox to test with.
I’ll put it on the TODO list. Thanks for the tip!
Tim
Forum: Reviews
In reply to: [TinyMCE Custom Styles] breaking visual editorHi there,
thanks for getting back to me. I’m running the previous plugin version on a customer website with 4.5.3, and have just developed the coming update on a sandbox site, also with 4.5.3. So I’m a bit puzzled as to what your problem can be.
The original author gave some useful tips on the FAQ tab of the plugin details – have you checked them out?
Have you tried TinyMCE Custom Styles with all other plugins deactivated? Which Theme are you using?
Failing all that, I’ll be providing the plugin update in the next hour or so, and it will no longer generate any PHP notices or warnings, perhaps that may help.
Thanks for your help!
Tim
Forum: Reviews
In reply to: [TinyMCE Custom Styles] breaking visual editorHi @nisimjoseph,
sorry to hear it did’nt work for you. I suspect a compatibilty issue here – please answer if you have any other plugins loaded which try to configure TinyMCE in any way. State which and I’ll try to get round to having a look.
I’m just about to release a new update, which has concentrated on improving the settings page (a lot). However, the stored data structures and how they are applied to TinyMCE is untouched, so I hardly expect it will solve your problem.
Would you happen to be in a position to do any debugging to help me solve the problem? As I noted in the description, I did not write this plugin originally, and am still not completely conversant with all it does.
As two other reviews have noted, this really is an important link between TinyMCE and WordPress, which is why I forked it as the original author had obviously abandoned it. But I’m (a) pushing 62, and (b) have a lot of other things to do, so any help / translating / co-authoring would be really VERY much appreciated – I did the fork because it felt like it wanted to be done, for the community, not out of boredom…
Cheers,
Tim Reeves
Forum: Plugins
In reply to: [Custom css-js-php] Use of undefined constant WCJP_CLASSESI have also just noticed the “undefined constant” warning. Since the bug report and suggested fix is 4 months old, it seems that support has gone away, what a pity.
There is another plugin with active support and 4.8 stars offering CSS + JS but not PHP; and several, like this one, for PHP; but I don’t find another plugin offering all 3 types.
So it would be really great if this plugin could be polished to remove those problems. Or would the author prefer that someone else take over the plugin?
Cheers, Tim
Forum: Plugins
In reply to: [Visual Editor Custom Buttons] Add new sometimes fails with PHP errorI have fixed this bug (and cleaned up code typography to make reading it easier).
You can get it here.
I have bumped up the version number to avoid confusion.
Hope this helps!
Forum: Plugins
In reply to: [Preserved HTML Editor Markup Plus] Depress-Key and Click no longer worksI’ve continued working on the tinyMCE topic, and have found out that basically “WP Edit” and “tinyMCE Advanced” are both great plugins – IF you don’t try adding other plugins like tinyWYM or Preserved HTML Editor Markup Plus. Then all goes wonky.
The “others” seem to get on with each other. So what I have just now ended up with is:
- TinyMCE Advanced Professional Styles. This allows you to put own styles into the “Styleselect” dropdown, and to register a stylesheet used by theme and editor (so you get to see the applied styles in both). It’s outdated and buggy (I fixed 2 of 4 bugs) but does the job I wanted.
- Preserved HTML Editor Markup Plus, which allows to toggle between visual and text tabs without any munging.
- Visual Editor Custom Buttons, which allows one to add buttons to tinyMCE toolbars, which wrap the current selection in anything you configure. This gets around the problem that otherwise tinyMCE block level actions always either wrap, or apply to the current block element, i.e. not allowing to wrap a marked selection in a new tag.
- tinyWYM Editor, which shows the block (container) structure.
This is all fine, except that a number of additional features of tinyMCE, those not supplied by native WordPress, are not available. I.e. those activated by the plugins which cause problems with the others I need. To get around that I use Advanced TinyMCE Config from Andrew Ozz. This allows me to directly configure the plugins and toolbars. The only problem was with the missing tinyMCE plugins. As a HORRIBLE hack I simply copied them into the standard WordPress directory for them via FTP, and added them in the “plugins” setting. As I said, horrible – but works a charm. This way you get the plugins loaded and available in the toolbar, without all the well-intentioned but sometimes nasty things that WP Edit and tinyMCE Advanced do.
Marking this as resolved.
Cheers, Tim
Forum: Plugins
In reply to: [tinyWYM Editor] Shortcodes get wrapped in p tagsAndrew,
don’t mind at all, in fact I agree with you, it’s solved. Should have marked it myself, sorry.
I’m also a bit queasy about using 4 plugins to get what I need, especially as two seem not currently maintained. But – for the moment – your comment about “bound to run into conflicts” seems not be happening (yet), all works fine for me now. And I found no other way to get all the features I want active at the same time. If you or anyone else reading this has some ideas, then please speak up!
Many thanks for your diligent work on tinyWYM, and also your prompt and tactful support. Good Karma!
Cheers, Tim
Forum: Plugins
In reply to: [tinyWYM Editor] Shortcodes get wrapped in p tagsHi Andrew,
many thanks for your reply. I’ve continued working on the tinyMCE topic, and have found out that basically WP Edit and tinyMCE Advanced are both great plugins – IF you don’t try adding other plugins like tinyWYM or Preserved HTML Editor Markup Plus. Then all goes wonky.
The “others” seem to get on with each other. So what I have just now ended up with is:
- TinyMCE Advanced Professional Styles
This allows you to put own styles into the “Styleselect” dropdown, and to register a stylesheet used by theme and editor (so you get to see the applied styles in both). It’s outdated and buggy (I fixed 2 of 4 bugs) but does the job I wanted. - Preserved HTML Editor Markup Plus, which allows to toggle between visual and text tabs without any munging.
- Visual Editor Custom Buttons, which allows one to add buttons to tinyMCE toolbars, which wrap the current selection in anything you configure. This gets around the problem that otherwise tinyMCE block level actions always either wrap, or apply to the current block element, i.e. not allowing to wrap a marked selection in a new tag.
- tinyWYM
This is all fine, except that a number of additional features of tinyMCE, those not supplied by native WordPress, are not available. I.e. those activated by the plugins which cause problems with the others I need. To get around that I use Advanced TinyMCE Config from Andrew Ozz. This allows me to directly configure the plugins and toolbars. The only problem was with the missing tinyMCE plugins. As a HORRIBLE hack I simply copied them into the standard WordPress directory for them via FTP, and added them in the “plugins” setting. As I said, horrible – but works a charm. This way you get the plugins loaded and available in the toolbar, without all the well-intentioned but sometimes nasty things that WP Edit and tinyMCE Advanced do.
Forum: Plugins
In reply to: [tinyWYM Editor] Shortcodes get wrapped in p tagsA NEW DAY
The plugin combination:
– WP-Edit
– tinyWYM Editor
– Preserved HTML Editor Markup Plusactually does work – seems like I was tired and maybe holding Ctrl rather than Alt.
BUT with WP-Edit and switching Visual <=> Text modes, Shortcodes are wrapped in <p> tags.
So back to “TinyMCE Advanced” – BUT there is also a problem here switching Visual <=> Text modes:
1. The 1st time I go from Visual to Text I see in the text quite a number of “<!–mep-nl–>” – fair enough.
2. But if I keep jumping between tabs, then each time empty “code” tags are added, like this:
<!–mep-nl–><code style=”display: none;”><code style=”display: none;”><code style=”display: none;”><!–mep-nl–>What can be causing this? Must I really always stay in Visual mode or can this problem be fixed?
Cheers, Tim
Forum: Plugins
In reply to: [Preserved HTML Editor Markup Plus] Depress-Key and Click no longer worksA NEW DAY
The plugin combination:
– WP-Edit
– tinyWYM Editor
– Preserved HTML Editor Markup Plusactually does work – seems like I was tired and maybe holding Ctrl rather than Alt.
BUT with WP-Edit and switching Visual <=> Text modes, Shortcodes are wrapped in <p> tags.
So back to “TinyMCE Advanced” – BUT there is also a problem here switching Visual <=> Text modes:
1. The 1st time I go from Visual to Text I see in the text quite a number of “<!–mep-nl–>” – fair enough.
2. But if I keep jumping between tabs, then each time empty “code” tags are added, like this:
<!–mep-nl–><code style=”display: none;”><code style=”display: none;”><code style=”display: none;”><!–mep-nl–>What can be causing this? Must I really always stay in Visual mode or can this problem be fixed?
Forum: Plugins
In reply to: [Preserved HTML Editor Markup Plus] Depress-Key and Click no longer worksUpdate:
The plugin combination:
– TinyMCE Advanced (rather than WP-Edit)
– tinyWYM Editor
– Preserved HTML Editor Markup Plus
does work!Forum: Plugins
In reply to: [tinyWYM Editor] Shortcodes get wrapped in p tagsUpdate:
The plugin combination:
– TinyMCE Advanced (rather than WP-Edit)
– tinyWYM Editor
– Preserved HTML Editor Markup Plus
does work!Forum: Plugins
In reply to: [Don't Muck My Markup] Seems to be breaking visual/text buttons.I have activated the “disable for all” option, but am seeing that still when changing from visual to text mode in the editor, <p> tags get added.
Any chance of adding an option to prevent markup modification when jumping between visual and text mode, but in such a way that Alt+Click still works?
Cheers,
Tim