Closed (fixed)
Project:
TinyMCE
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
21 Jun 2005 at 04:03 UTC
Updated:
15 Dec 2005 at 11:20 UTC
I installed the quotes module, and I didn't really want TinyMCE formatting on the quotes, since I use them in my site theme instead of as a block. I hacked together this patch to give me what I want, and it seems to work. Maybe someone else is looking for the same thing.
I tested it on a number of different paths with positive results. I added a setting -- access_excludes -- through the _settings page. Regex befuddles me, so I just copy/pasted what already worked and modified the one little part that contains path expressions. I moved around some things to reduce code redundancy in the parts I modified.
Smack me if I'm an idiot.
Thanks,
-t-
| Comment | File | Size | Author |
|---|---|---|---|
| tinymce-4-6.path-render-exclusions.patch | 2.74 KB | Travis |
Comments
Comment #1
matt westgate commentedThe other way to do this is by creating a new tinymce theme in your theme file or disabling tinymce by default.
Comment #2
Travis commentedActually, the result is not the same. I already have TinyMCE disabled by default, but I wanted to be able to *selectively disable* for paths for which I would normally want it enabled. Take for instance the following pattern:
Enabled: node/add/*
Disabled: node/add/quotes
Disabled: node/edit/quotes
This patch allows me to implement the above without having to *selectively enable* all node/add/ paths execpt the two exclusions.
Comment #3
matt westgate commentedAnybody else have feedback on this?
Note: this can currently be achieved by overriding the tinymce theme, although it's not a very friendly way. Just do a check for node/add/quotes and unset($init);
Comment #4
Travis commented*raises hand*
I had another idea. The default TinyMCE profile could be enabled for select node types as part of the "content types" (admin/node/configure/types) configuration. Looks like a simple enough hook to use. Otherwise, each TinyMCE profile could grab a list of node types and allow the admin to select which of the node types TinyMCE should be enabled for.
I'd really like to hear what anyone else has to say.
Thank you,
Travis
Comment #5
macdoggie commentedIt is highly desirable to be selective of which content types utilize Tiny MCE IMHO.
For example, setting
node/*
Tiny MCE shows up in the forum topics and then when the mail is sent, it contains junked up HTML code along with it. I have a similar need to specify the content type as I would like to turn Tiny MCE off per content type - i.e forums. Hooking Tiny MCE to the content types is highly desireable IMHO.
thx in advance.
Comment #6
m3avrck commentedGreat idea! This has been added to the 4.7 release of TinyMCE module (and available in CVS right now). Thanks!
Comment #7
Wesley Tanaka commentedhow cool is that. I started looking for this feature just now, and it was checked in yesterday.
Comment #8
(not verified) commented