My support chap has stated this: "Quotes add on, it doesnt seem to work at all on some browsers and on the ones that it does work on it quotes the highlight text in blue but your reply to it will also be indented and blue, which doesnt look right.see the here for example http://forum.djkit.com/discussion/comment/360#Comment_360
First of all, it doesn't seem to be playing well with your WYSIWYG editor. These editors are nice if you want to allow some formatting of comments, but they are all slightly buggy in that they make it difficult to know where your cursor is as you select where to type in the box. In your case, I found that it would put my cursor inside the quote box, so as I entered my response, it is doing it right inside the quote.
The only way I could make sure that I wasn't inside the quote when I was typing was to click the "Show Source" button on the WYSYWYG editor and start typing below the last blockquote, and then click it again to go back to the non-code view. This is just going to happen with any WYSIWYG editor. Like I said, they're all a bit of a pain. This one is so much of a pain and we find so many little problems like this one that we're considering removing it from our offering completely in favour of something simpler that isn't prone to user/browser problems.
Second, you have a TON of javascript loading on your pages, which means that on some browsers, and definitely on slower computers, you're going to run into problems. The more javascript you have, the more you rely on your end users to have computers & browsers that can handle all of the fancy stuff on your pages. If they don't, they're going to start reporting bugs to you as their browsers fail to do things properly. We can help you address each of these problems as they come up, but we'd need to know exactly what browser & version the people are using, and have detailed descriptions of what is going wrong. Finally, in the end, we may end up just recommending that you turn certain javascript-based plugins off so they don't wreak havoc on your user's browsers. But we won't know for sure until we tackle them one at a time.
That's strange. I've tested it locally in Chrome and it worked fine. It's got to be something to do with your forum. I'm going to have to ask @Tim - who wrote the plugin - to take a look.
Comments
after the close would do it?
Chrome and Safari doesn't work with quotes can you see what is going on there?
Cheers
James
The only way I could make sure that I wasn't inside the quote when I was typing was to click the "Show Source" button on the WYSYWYG editor and start typing below the last blockquote, and then click it again to go back to the non-code view. This is just going to happen with any WYSIWYG editor. Like I said, they're all a bit of a pain. This one is so much of a pain and we find so many little problems like this one that we're considering removing it from our offering completely in favour of something simpler that isn't prone to user/browser problems.
Second, you have a TON of javascript loading on your pages, which means that on some browsers, and definitely on slower computers, you're going to run into problems. The more javascript you have, the more you rely on your end users to have computers & browsers that can handle all of the fancy stuff on your pages. If they don't, they're going to start reporting bugs to you as their browsers fail to do things properly. We can help you address each of these problems as they come up, but we'd need to know exactly what browser & version the people are using, and have detailed descriptions of what is going wrong. Finally, in the end, we may end up just recommending that you turn certain javascript-based plugins off so they don't wreak havoc on your user's browsers. But we won't know for sure until we tackle them one at a time.
Cheers
James
Cheers
James
I just checked your forum with the following browsers:
OS X - Firefox, Chrome, Safari
Win - Chrome, IE 9
It seemed to work as expected in all of them. Can you confirm for me that this problem is still happening for you? Thanks.
Tim
Seems to be working now, weird...... ah maybe when we had another issue which we fixed it then fixed this
"Your custom theme was missing one very important line:
{asset name="Foot"}
I put the line back in your theme and things should be okay now. "