Issues With Both Editors

We have been experiencing problems for more than a week now when posting in WYSIWYG.  People cannot post below the quote box when quoting a message.

A new issue developed yesterday in source code mode where the BBCode for text size disappears if you preview, edit or quote a message.

Is anyone else having these same issues with their editors?  Please advise if this is an issue with all forums and not just mine.

We had issues when the new editors came into being but I thought all had been resolved.  The "quote box" issue is a reappearance of a problem that was occurring initially.

The BBCode problem for text is brand new.

Thanks in advance for any help.

Edited to add that the BBCode for text size also disappears in WYSIWYG.

@RedMomma5 wrote:We have been experiencing problems for more than a week now when posting in WYSIWYG.  People cannot post below the quote box when quoting a message.

This issue should be fixed now.

@SLGray wrote:

@RedMomma5 wrote:We have been experiencing problems for more than a week now when posting in WYSIWYG.  People cannot post below the quote box when quoting a message.

This issue should be fixed now.

Yes, I just tested it and it works to type below the quote box now.  Thank you.  I'm not sure what you did to fix it but thank you.

However, the problem with the disappearing BBCode is still happening.  When I type something and add the BBCode to enlarge the text, it stays in place as long as I don't edit, preview or quote the post, otherwise, it disappears.  This happens in either editor.

Can you fix this as well?

Is this occurring in all browsers or just one?

@SLGray wrote:Is this occurring in all browsers or just one?

It is happening in my browser which is Firefox.  I usually do not have any issues with this browser when others do.  I have not gotten any reports from my members that they are having text problems but that is probably because many of them do not use the BBCode for text and just type in the default mode.

I can ask if anyone else is experiencing this but I assumed that it might be related to the other problem with the quote function which you have now apparently fixed.

I did have one member that said she was having trouble responding to PMs but she uses IE and this is not related to the editor issues.

Try this:

Clear your browser's cache and delete your forum's cookies.

@SLGray wrote:Try this:

Clear your browser's cache and delete your forum's cookies.

Okay, I did that and the problem still exists.  I can tell you that I noticed that the text size was changing in other people's quoted posts.  For example, a member might use size 24 to type in but when someone quoted their post, the size would switch to the default (i.e. the BBCode tags would disappear).  So, I know this is not just happening to me but people have not been complaining about it.  This started happening yesterday.  I prefer to type in a larger size so that my members can read the text better and I don't like the disappearing BBCode.  Something is not right and I am pretty sure it has nothing to do with my browser since as I explained I can visually see it happening in the posts of others.

I have the last issue also in http://msntvcommunity2.4rumer.com/u2 . I'll go delete cookies . 

@JUST HENRY wrote:

@JUST HENRY wrote:

@JUST HENRY wrote:Tfor Bill . that stayed big till I edited ! # 18

In quote I do not see size tags

Help

Hello,

May I ask if the issue is still appearing? We don't know have any reported bugs about this as off now. Thanks

@Jophy wrote:Hello,

May I ask if the issue is still appearing? We don't know have any reported bugs about this as off now. Thanks

Hi, I just tested it this morning in both editors and when I quoted and previewed a message, the existing size tags did not disappear.  I don't know why they were disappearing before but both editors appear to have stopped removing the tags (at least for now).

There was another person who posted to this thread that they were having the same trouble (just above) but as for myself, the issue has been resolved.  Perhaps a temporary glitch.

Thanks again.