search

bishop335 / subtext

Automatically exported from code.google.com/p/subtext
0 stars 0 forks source link

FTB Editor is not working #191

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Modify the web.config entry <BlogEntryEditor
defaultProvider="FCKeditorBlogEntryEditorProvider"> to <BlogEntryEditor
defaultProvider="FtbBlogEntryEditorProvider">
2. Edit any one of the posts
3.

What is the expected output? What do you see instead?
The richtext box should appear. The richtext editor instead is replaced
with a plain textarea. In debug mode, the errors as reported in
http://groups.google.com/group/subtext/browse_thread/thread/130e4404e6ad9911?hl=
en
appear.

What version of the product are you using? On what operating system?
XP Prof, I believe this is the latest unreleased code, without IIS.

Please provide any additional information below.
The POST button is also not working when switching over to FTB Editor (with
actually plain text editor showing up for editing, but this also does not
work). I get a validation error message stating "Your post must have a body."

Original issue reported on code.google.com by shankarkrupa@gmail.com on 9 Mar 2010 at 7:18

GoogleCodeExporter commented 8 years ago 
This sounds bad. We should investigate.

Original comment by haac...@gmail.com on 9 Mar 2010 at 9:29

GoogleCodeExporter commented 8 years ago 
Definitely a bug, but I can't seem to figure out why it's broken. Is there any 
reason 
you don't simply want to use the default FCKEditor?

Original comment by haac...@gmail.com on 30 Mar 2010 at 10:29

GoogleCodeExporter commented 8 years ago 
Of course I use only FCKEditor. Either that or Live Writer. I just thought of
checking what would be the iframe/textbox id when switching to other editors. I 
was
trying to write implement the "live-blogging" feature (issue 60) and thought of
testing the code with other editor controls.

Original comment by shankarkrupa@gmail.com on 31 Mar 2010 at 5:23

GoogleCodeExporter commented 8 years ago 
Oh, good. Well I do think we should fix this. But I'm stumped and it's a low 
priority 
right now.

Original comment by haac...@gmail.com on 31 Mar 2010 at 6:37

GoogleCodeExporter commented 8 years ago 
I had this same problem, and worked around it by posting from Firefox Mac OS 
from Chrome Mac OS.

Original comment by iamchu...@gmail.com on 2 Jun 2010 at 1:42

GoogleCodeExporter commented 8 years ago

Original comment by haac...@gmail.com on 20 Nov 2011 at 5:16