Any reason why TinyMCE cannot or shouldn't be upgraded?
It appears that the RTE does not even render on an iPad and after a little research it seems the reason may be due to the current TinyMCE version in Umbraco and it is by design because of an issue at the time of release which I think is now resolved in a newer version.
So in order to correct the issue I want to look at replacing the current TinyMCE version with a newer version but before I do wanted to find out if there is any reason I shouldn't?
From what I understand, there is some specific Umbraco code in the current TinyMCE implementation that would require you to implement again if you upgrade (not sure what it is, but I believe it is commented in the source code).
There is a task currently on the issue tracker to decouple TinyMCE from Umbraco and use TinyMCE modules for the Umbraco specific bits like we did in v5 http://issues.umbraco.org/issue/U4-20 but there isn't currently any schedule for that right now.
Thanks guys, I don't think I want to go down this route then as it will cause more work in the long run and potentially other problems that I don't need right now. So my questions now is how do people currently work around this issue?
I have a client wanted to blog live from events, due to the nature of the events (Poker) they are very often on the cardroom floor and so it's not practical to walk around with a laptop. The only way I can see out of this is to implement a custom RTE Control?
I was about to say i'm sure someone announced they had fixed this in 4.8 as there was a cheer at Codegarden when they mentioned it? As Tom says, try 4.8 nightly to see.
Any ideas given the recent news when the v4.8 release is planned for? Should it solve my problems I don't think I can afford to put it into production until officially released. I wil pull it down tonight and give it a go though as sounds promising.
Any reason why TinyMCE cannot or shouldn't be upgraded?
It appears that the RTE does not even render on an iPad and after a little research it seems the reason may be due to the current TinyMCE version in Umbraco and it is by design because of an issue at the time of release which I think is now resolved in a newer version.
So in order to correct the issue I want to look at replacing the current TinyMCE version with a newer version but before I do wanted to find out if there is any reason I shouldn't?
Thanks, Simon
http://umbraco.codeplex.com/workitem/30395
Anyway, the tricky part is the custom umbraco code nested in TinyMCE files I guess..
From what I understand, there is some specific Umbraco code in the current TinyMCE implementation that would require you to implement again if you upgrade (not sure what it is, but I believe it is commented in the source code).
There is a task currently on the issue tracker to decouple TinyMCE from Umbraco and use TinyMCE modules for the Umbraco specific bits like we did in v5 http://issues.umbraco.org/issue/U4-20 but there isn't currently any schedule for that right now.
Matt
Thanks guys, I don't think I want to go down this route then as it will cause more work in the long run and potentially other problems that I don't need right now. So my questions now is how do people currently work around this issue?
I have a client wanted to blog live from events, due to the nature of the events (Poker) they are very often on the cardroom floor and so it's not practical to walk around with a laptop. The only way I can see out of this is to implement a custom RTE Control?
I'm assuming you are talking about editing back end content here, so you could have a couple of options.
Use something like Lees MarkDown editor http://our.umbraco.org/projects/backoffice-extensions/markdown-editor, or maybe try something like this app http://itunes.apple.com/gb/app/blogpress/id317799861?mt=8 hooked up to the MetaWeblog API which Umbraco exposes (I've not tested it, but worth a try)
Matt
Oooh MarkDown Editor is a definite possibility, thanks for the ideas Matt.
Hi Simon,
Have you tried the latest 4.8 changeset? Stephan Gay has upgraded TinyMCE to the latest version (3.5) - not sure if that might not solve your issues.
-Tom
I was about to say i'm sure someone announced they had fixed this in 4.8 as there was a cheer at Codegarden when they mentioned it? As Tom says, try 4.8 nightly to see.
Any ideas given the recent news when the v4.8 release is planned for? Should it solve my problems I don't think I can afford to put it into production until officially released. I wil pull it down tonight and give it a go though as sounds promising.
Just a note, I couldn't get BlogPress to work. it would save with no content. Only the node name would be correct.
I'll test a few other apps and see if they work.
-Jason
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.