Rtf editing

emmanueljames · Joined: 14 Jan 2005 Posts: 16

In a recent post I suggested that one could manage multiple blogs [that is using more than one registered username] at the same time through using multiple browsers. But were there any snags?

When testing I used Opera with Firefox; Firefox is my default browser.

After posting, I got to Edit Article, in blogharbor, and got a warning that rtf editing was not supported, so only basic editing was offered.

This morning I have tried the same trick with Netscape 7.1. This time I find the basic editor loaded and without any warning.

That's the background.

Could the blogharbor team do two things:

1. say whether there is anyway round this restriction, eg options within individual browsers that might be changed

2 Post a list of those browsers that do, and those browsers that do not support full editing?

EJ

emmanueljames · Joined: 14 Jan 2005 Posts: 16

Further to my previous post, this is what I think is happening.

When I logged on in Opera, because of problems with rtf and that browser, blogharbor switched off rich text editing and that switch off was 'sticky'.

In terms, when I reloaded in any browser I was in basic editing. To add to the confusion, when rtf editing is switched off then the editing help message (below the edit window and pointing to settings) gets switched off too.

So I have had to dig out how to change back to rtf directly. Settings & Security | Advanced and the next to last option on that page?

Teach me to push the envelope.

Meanwhile, back at the ranch, when rft editing is switched off , can the user be given more help about the consequences, and the cure, please?

EJ

john · Site Admin Joined: 16 Mar 2004 Posts: 3434

john · Site Admin Joined: 16 Mar 2004 Posts: 3434

emmanueljames · Joined: 14 Jan 2005 Posts: 16

Sorry, I think we crossed in the posting, here. You cover the point made below in your next post!

Thanks again for the quick, helpful response.

A loose end, if I may.

There is the point that, when I hit Opera during testing, blogware detected that and switched off rich text editing.

Can you take on board the thought that the user should be advised that this switch off is sticky. In terms, that when the user returns to another browser, the user has to actively swtich rt edit on again.

[Also, its a pretty long road to that switch. Perhaps too long for some users...?]