Printable View
When you see the little chap with the "oops" sign below, this has been fixed (unless it's the trigger that gets replaced of course):
:oops:
Currently this is clashing with the "embarassment" smiley due to the trigger being a subset of the "oops" one.
(I did PM a mod on this, but it seems to have been ignored - it has been present since the new icons were added.)
It depends on which came first. If the :o smilie was there before the :oops: one then :oops: will probably have to be disabled to avoid messing up all the previous instances of :o. This would be my guess.
Shorty, best suggestion would be to change :oops: to ::oops: which should resolve the issue. Existing :oops: entries will just have to remain as is unless you want to run a SQL update to change :oops: to ::oops:
Paul, thanks for raising this. Our forum webmaster is currently very busy in real life and I'm sure he'll get onto this as soon as he can. If it isn't actioned by the end of the week then let me know and I will do it. In future if you want to pm a mode concerning issues with the site please send it to Az and Shorty if possible
thanks again
Quote:
Originally Posted by Paul Adams