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.
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
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.
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
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.