We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

LG TinyMCE Multiple Configurations

Development and Programming

Poccuo's avatar
Poccuo
22 posts
16 years ago
Poccuo's avatar Poccuo

I wonder if anyone has had any success at setting up two installations of LG TinyMCE on one website.

This would be helpful if, for instance, you wanted to have two different configurations on one system. One TinyMCE field type could allow h1, h2, h3, p, bold and italic while the other only allows P, bold, italic.

       
Robin Sowell's avatar
Robin Sowell
13,160 posts
16 years ago
Robin Sowell's avatar Robin Sowell

I’m going to shift this to the extensions forum as it’s extension specific and I haven’t tried that one. LG can likely help you out with it, though.

       
Poccuo's avatar
Poccuo
22 posts
16 years ago
Poccuo's avatar Poccuo

Thanks Robin, I appreciate you being kind enough to move this to the right place. I’ll keep a better eye out next time for this.

I have PM’d LG so I think he’ll probably hit this thread soon enough.

       
james Brown's avatar
james Brown
492 posts
16 years ago
james Brown's avatar james Brown

i too would love to be able to do this!

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
16 years ago
Leevi Graham's avatar Leevi Graham

I have thought about implementing this, and it would be a cool feature, although I’m not sure of the best solution yet.

It’s on the roadmap but don’t expect it any time soon 😊

       
james Brown's avatar
james Brown
492 posts
16 years ago
james Brown's avatar james Brown

Maybe have a default setting like you do now. And then when you add a custom field and select WYSIWYG, you get a text area where you can override the default settings.

Just an idea.

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
16 years ago
Leevi Graham's avatar Leevi Graham

Yep that’s exactly how I was going to approach it… The only problem being the possible extra overhead of including all the scripts in the head and how to assign a specific script to a specific field. I’m sure I can figure it out tho.

My development roadmap is pretty simple, unless I need it for a project or someone supports the development I generally won’t add a feature. It might sound a bit rough but as the saying goes “time is money” 😊

I hope you understand if this doesn’t get implemented in the near future.

Cheers

       
james Brown's avatar
james Brown
492 posts
16 years ago
james Brown's avatar james Brown

No worries… I understand that!

       
Adrienne L. Travis's avatar
Adrienne L. Travis
213 posts
16 years ago
Adrienne L. Travis's avatar Adrienne L. Travis

Leevi, how much are we talking for development? I mean, i am not made of money or anything, but i’d be pleased to contribute to a “bounty” on this feature.

I can think of two ways to handle it. First, i figure the easiest way to do it is the way some other extension writers have handled custom field types: set the field to a dropdown list, paste in the config info in the “list maker” that appears, then save, then set it back to a TinyMCE field. But i suppose that might be too clunky.

Second, you could set up “config packages” in the Extension settings, and be able to assign any one of three or four custom field types to a field. All would be TinyMCE fields, but you could set up and name the “simple”, “advanced”, “barely-there” and “absolutely-everything” configs, and let people customize those.

       
Poccuo's avatar
Poccuo
22 posts
16 years ago
Poccuo's avatar Poccuo

We would also be happy to contribute to funding this feature… very very happy…

Please let us know.

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
16 years ago
Leevi Graham's avatar Leevi Graham
First, i figure the easiest way to do it is the way some other extension writers have handled custom field types: set the field to a dropdown list, paste in the config info in the “list maker” that appears, then save, then set it back to a TinyMCE field. But i suppose that might be too clunky.

I think this is the best way to move forward. Raher than use the drop down box I would just add another field config box like LG Data Matrix. If the box was left blank the extension would just use the default extension settings otherwise it would use the custom field settings.

Second, you could set up “config packages” in the Extension settings, and be able to assign any one of three or four custom field types to a field. All would be TinyMCE fields, but you could set up and name the “simple”, “advanced”, “barely-there” and “absolutely-everything” configs, and let people customize those.

This is another option which does have less flexibility but more maintenance overhead if you want to change one setting.

A combination of both these ideas would be the best approach. Create “tinymce profiles” in the extension settings and then display the profiles in the the custom field settings. You would also add “custom profile” as an option which would show the extra per field config box.

I’m thinking development time would be about a day / day and a half for this. I’d love to get it done but client work comes first. I’m guessing the forum rules forbid me to add a dollar figure to how much this will cost to update, but if you’re interested in contributing send me a PM.

Cheers Leevi

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.