Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: WYSIWYG editor
> When I clic on the html or preview tab, I lost my modifications in TinyMCE…
Yes, I saw that happen sometimes…
> Is it a way to insert CSS style?
Not sure I understood what you want, but maybe this comment could help you.
Offline
#17 2005-03-29 12:12:33
- marios
- Archived Plugin Author
- Registered: 2005-03-12
- Posts: 1,253
Re: WYSIWYG editor
> marios wrote:
> > jpdupont wrote:
> Interesting …
I just try it … without success, on an empty RC3 installation (with last week source code).
In the page code source, I see the tinyMCE script call, but nothing in the textarea.
Same here,on RC1,this thing ain’t workin(Firefox here).
Thought to give it a try for some pontential windows spoiled future custumers.
May be need’s some work (after fridays,I mean Saterday’s &Sundays?)
What hadened to this thread ?
⌃ ⇧ < ⎋ ⌃ ⇧ >
Offline
Re: WYSIWYG editor
Ah, I had an older version (~ two weeks) that it wasn’t working with. Upgraded to the most recent build and it works like an absolute charm. Nifty script.
One horrid issue though. It uses font tags to colorize text.
Offline
Re: WYSIWYG editor
> micampe wrote:
> Beacuse if you didn’t the HTML code would be parsed by Textile and might cause problems.
Ok so it use plain XHTML (I hope it’s not pure HTML, that was a typo). That’s worth telling, because in theory he’s not obligated to do so.
So I guess the B I U buttons and so on are really bold, italic, etc. ? That’s just plain wrong, an anthor doesn’t really need theses (and on some sites doesn’t need them at all) but definitely need the strong, emphase, cite, h1-h6, ul, ol and so on.
Can you edit the toolbar to reflect semantic XHTML used by the authors ?
Offline
Re: WYSIWYG editor
It is XHTML standard code. It uses strong, em, cite, etc, and not b, i, u, etc. I tried it, and I didn’t much care for it. It’d be fine for someone new that was afraid of Textile, or something, but, I didn’t like that it didn’t allow for a preview or the HTML it was going to output. Granted, it’s WYSIWYG, but, when I tried it, it added a few extra peices of code to the em tag that italizised my entire site. Not sure why, but, it did.
Still, it’s alright, if people aren’t into the DIY kind of code, and would prefer WYSIWYG.
The following is true
The above statement is false.
Offline
Re: WYSIWYG editor
Ok, that’s one thing.
But if it doesn’t use Textile, it’s an issue. If we have some silly authors afraid of Textile and wanting to use wysiwyg ok, but what about the others ? If we set up a workflow, people proof-reading and validating the article have now to use the same tool/language as the author, and not the one they want to use.
Offline
Re: WYSIWYG editor
> Can you edit the toolbar to reflect semantic XHTML used by the authors ?
Can you please read some docs or at least give it a give it a quick try?
TinyMCE allows you to filter the tags however you like it, you just have to edit the options in <tt>tinymce/txp.js</tt>. B means strong and I means em but those are the buttons people are expecting.
Last edited by micampe (2005-03-30 07:49:32)
Offline
Re: WYSIWYG editor
Hey I am trying to install the pluging, copying that install code but I keep getting “install plugin failed” message from TxP?
Any ideas? I’m running the latest version of TxP and I haven’t customized or installed anything else yet.
Hmm…
Offline
Re: WYSIWYG editor
Hello Folks,
I have just release a new version of the plugin wich should address most of Jeremie’s concerns
You don’t need to download the TinyMCE code again, just update the plugin.
Offline
Re: WYSIWYG editor
Thanks to alicson, I can confirm the plugin doesn’t work in Internet Explorer. Any JS/IE wizards can have a look at 10 lines of code and tell me where’s the problem?
(oh, how I wish there was a Javascript Console for IE too)
Offline
Re: WYSIWYG editor
I tested it myself on Internet Explorer 6 SP2 and it worked just fine.
Which browser/version are having problems?
Offline
#27 2005-04-06 20:36:00
- starzabove
- Member
- Registered: 2004-04-13
- Posts: 76
Re: WYSIWYG editor
I can confirm that an entry with an image worked here, in IE6 svc pack 2, as well.
I am also curious as to what isn’t working.
90+ Textpattern installs and still going…
Offline
#28 2005-04-07 00:43:18
- Vitruvius
- Plugin Author
- Registered: 2004-09-21
- Posts: 125
Re: WYSIWYG editor
Before I start let me state that I love Textile. BUT, I still think this has the potential to be a great plugin for a number of reasons
- It will help sell TXP to some of my clients who would otherwise be scared off by Textile (esp for images)
- It has a very good image tool which IMO is better than the one built into TXP
Having tested it on a new install, I think it needs the following (which may or may not be a big ask):
- The Toggle Editor function is great – but on testing it destroyed a post that had originally been entered with Textile. From what I can see it:
- added line breaks all over the place
- added strange ASCII code around some Textile tags – notably em
I order for the editor to be of proper use in TXP we should be able to switch between editors without mixing the formatting up.
- The image tool is very good – it seems easier and more powerful than the std TXP image tool (although other admin / image plugins add quite a few new features) – but again it would be better if the it logged the images in the TXP db so they could be managed with the TXP image tool if needed. Otherwise I’d be afraid of having authors using either system and having two ‘sets’ of images.
Just my comments. But well done micampe – it is a good addition.
Offline
#29 2005-04-07 00:45:47
- Vitruvius
- Plugin Author
- Registered: 2004-09-21
- Posts: 125
Re: WYSIWYG editor
aghh – punbb has fallen over again – can’t edit my post above – but take point 3. and turn it into point 2. and nudge it to the left :)
Offline
Re: WYSIWYG editor
> Before I start let me state that I love Textile. BUT, I still think this has the potential to be a great plugin for a number of reasons
These are the same reasons for which I implemented it.
Having tested it on a new install, I think it needs the following (which may or may not be a big ask):
> # The Toggle Editor function is great – but on testing it destroyed a post that had originally been entered with Textile. From what I can see it:
The problem is that the “Toggle Editor” function is not meant to switch between formatting languages, but only activating/deactivating the editor.
Let me exmplain it better: if you have a Textile post and switch on WYSIWYG, the text is not converted to HTML, it’s still the original Textile, but TinyMCE tries to clean it up for correct HTML presentation, this is what’s causing your problems.
In short you can’t use the WYSIWYG editor for a post wich was previously created in Textile. Maybe I should remove the “Toggle editor” link in this case, what do you think?
> # The image tool is very good – it seems easier and more powerful than the std TXP image tool […] but again it would be better if the it logged the images in the TXP db so they could be managed with the TXP image tool if needed.
This can be done by modifying TinyMCE’s image browser plugin. Will look at some day.
> Just my comments. But well done micampe – it is a good addition.
Thank you
Offline