Thread: Editor Box Problems

Originally Posted by sharptonn

So can you tell me how to do that, Jimmy?

Been away from the computer. If what Max said works for you great. I upload photos to a free account with Photobucket. There are other hosting sites but PB is the only one I've used.

The photo, once uploaded will have a menu to the right. IIRC 4 options depending on what you are going to post it in.

I copy and paste into the PM and click on 'preview post' to make sure I selected the correct url choice. That is how I do it.

you can also put pics in a PM if they were attached to a forum post.
Each attachment has a number, so if you copy paste the 'attach' block of the forum post into your PM, you get the same effect.

If you use photobucket use the bottom link to attach a picture to a post or pm. That's what I do

Originally Posted by Bruno

you can also put pics in a PM if they were attached to a forum post.
Each attachment has a number, so if you copy paste the 'attach' block of the forum post into your PM, you get the same effect.

That's a good tip - cut and paste the attachment code block in PM's....been looking for a solution to do that - thanks, and of course, makes perfect sense when you think of it.

Originally Posted by Bruno

you can also put pics in a PM if they were attached to a forum post.
Each attachment has a number, so if you copy paste the 'attach' block of the forum post into your PM, you get the same effect.

Why didn't I think of that ??? ...........

Great tip Bruno, thanks for that.

Originally Posted by Bruno

If you refer to the wysiwyg editor (what you see is what you get) I disabled that on purpose because it was causing issues for anyone using it to post pictures, as well as for other actions that some of the staff are using.

Since I cannot fix that editor nor do I know what caused this behavior (not for certain) my only 2 options were to keep it alive and be bombarded with people having issues that I can't solve, or disable it and have people us the standard editor

I noticed that the desired behavior was no longer available, and figured that it had been disabled. I, too, miss the real-time WYSIWYG editing feature.

The alternative is to work in the (now) default "source" mode, then click on "Preview Post" to verify what's-what. To be sure, it's an extra step, but "it is what it is." FWIW, I figure that the users who weren't "bombarding" the SRP staff with their issues are probably in the majority; as they say, "it's the squeaky wheel gets the oil."

PS: The issue with posting pictures while in WYSIWYG mode is that you can't do "fancy" stuff, such as placing a picture within a link (or vice-versa). Oh, well. That's why clicking on the icon toggles between WYSIWYG and source modes -- "wax on, wax off".

"Wax on, Wax off ! ,,,

Originally Posted by JBHoren

I noticed that the desired behavior was no longer available, and figured that it had been disabled. I, too, miss the real-time WYSIWYG editing feature.

The alternative is to work in the (now) default "source" mode, then click on "Preview Post" to verify what's-what. To be sure, it's an extra step, but "it is what it is." FWIW, I figure that the users who weren't "bombarding" the SRP staff with their issues are probably in the majority; as they say, "it's the squeaky wheel gets the oil."

PS: The issue with posting pictures while in WYSIWYG mode is that you can't do "fancy" stuff, such as placing a picture within a link (or vice-versa). Oh, well. That's why clicking on the icon toggles between WYSIWYG and source modes -- "wax on, wax off".

Precisely, JB! Oh well.....Seems by the time I finally learn something, it has changed or is obsolete!
A propellerhead, I am NOT!

I know many people used it. But absent a solution for the problem, it was either that or keep getting problem reports.
It took me quite a while to figure out that the editor was the issue, because I never used it (it wasn't standard or perhaps available when I registered).

Additionally, we're run on a volunteer basis, with all hours that we spend here being hours subtracted from time spent on things like family, or actually doing fun stuff. Figuring out where the problem was located took long enough, and being able to provide a workaround counts as a win. Sure, I would have preferred actually finding the root cause and fixing it, but at the moment there is no one in the staff who has both the skills and the time needed to fix it.

Personally I hope that when we upgrade to 5 the issue will be gone.

Not that that is going to happen in the very near future because of the same reason. So if there are people with some Linux server skills, php or vbulletin we could always use an extra hand to help us manage.