The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Hello,
Just noticed something, you have banned text of over 60 characters with no spaces, presumably because it's probably meaningless spam or long URLs as plain text...
But the filter also picks up URLs in the
(I needed to edit that, putting spaces in so the "[ link = (something really long in here) ]" bit didn't get picked up as an actual Link... You might also want to make sure any of the special Freeola tags between the CODE tags are treated as plain text too)
I noticed when I replied quoting a message that had links in it and because of the length of the links it stopped me posting the message. I wondered how the original poster had made the original post with the links, so altered them, then edited the post to change them back to the 'proper' links, and it worked, so it also seems you have some issue with the filter not being the same when editing posts as it is when you initially make them...
Anyway, you should probably ensure anything inside a
Have fun!
[EDIT] - Gah, further testing and I can't figure out why it wouldn't accept it before... It was definitely giving me errors to do with the URLs I was posting (see my reply), but now it seems to be accepting long URLs fine... So dunno what I did :S
But still, the thing I mentioned about making everything between the CODE tags plain text, you might want to look at! :|
Just noticed something, you have banned text of over 60 characters with no spaces, presumably because it's probably meaningless spam or long URLs as plain text...
But the filter also picks up URLs in the
[LINK] tag, eg. [ link = (something really long in here) ] would get picked up and not allowed.(I needed to edit that, putting spaces in so the "[ link = (something really long in here) ]" bit didn't get picked up as an actual Link... You might also want to make sure any of the special Freeola tags between the CODE tags are treated as plain text too)
I noticed when I replied quoting a message that had links in it and because of the length of the links it stopped me posting the message. I wondered how the original poster had made the original post with the links, so altered them, then edited the post to change them back to the 'proper' links, and it worked, so it also seems you have some issue with the filter not being the same when editing posts as it is when you initially make them...
Anyway, you should probably ensure anything inside a
[LINK] isn't counted when searching for words of 60 chars, as it will prevent people from posting certain URLs, and you might also want to look at why there's a difference between what is allowed when posting and editing...Have fun!
[EDIT] - Gah, further testing and I can't figure out why it wouldn't accept it before... It was definitely giving me errors to do with the URLs I was posting (see my reply), but now it seems to be accepting long URLs fine... So dunno what I did :S
But still, the thing I mentioned about making everything between the CODE tags plain text, you might want to look at! :|
click here
click here
Hmm, the thing I was having trouble posting was these, but I just tried again and it worked... :S
Test
click here
Hmm, the thing I was having trouble posting was these, but I just tried again and it worked... :S
Test
Hello,
Just noticed something, you have banned text of over 60 characters with no spaces, presumably because it's probably meaningless spam or long URLs as plain text...
But the filter also picks up URLs in the
(I needed to edit that, putting spaces in so the "[ link = (something really long in here) ]" bit didn't get picked up as an actual Link... You might also want to make sure any of the special Freeola tags between the CODE tags are treated as plain text too)
I noticed when I replied quoting a message that had links in it and because of the length of the links it stopped me posting the message. I wondered how the original poster had made the original post with the links, so altered them, then edited the post to change them back to the 'proper' links, and it worked, so it also seems you have some issue with the filter not being the same when editing posts as it is when you initially make them...
Anyway, you should probably ensure anything inside a
Have fun!
[EDIT] - Gah, further testing and I can't figure out why it wouldn't accept it before... It was definitely giving me errors to do with the URLs I was posting (see my reply), but now it seems to be accepting long URLs fine... So dunno what I did :S
But still, the thing I mentioned about making everything between the CODE tags plain text, you might want to look at! :|
Just noticed something, you have banned text of over 60 characters with no spaces, presumably because it's probably meaningless spam or long URLs as plain text...
But the filter also picks up URLs in the
[LINK] tag, eg. [ link = (something really long in here) ] would get picked up and not allowed.(I needed to edit that, putting spaces in so the "[ link = (something really long in here) ]" bit didn't get picked up as an actual Link... You might also want to make sure any of the special Freeola tags between the CODE tags are treated as plain text too)
I noticed when I replied quoting a message that had links in it and because of the length of the links it stopped me posting the message. I wondered how the original poster had made the original post with the links, so altered them, then edited the post to change them back to the 'proper' links, and it worked, so it also seems you have some issue with the filter not being the same when editing posts as it is when you initially make them...
Anyway, you should probably ensure anything inside a
[LINK] isn't counted when searching for words of 60 chars, as it will prevent people from posting certain URLs, and you might also want to look at why there's a difference between what is allowed when posting and editing...Have fun!
[EDIT] - Gah, further testing and I can't figure out why it wouldn't accept it before... It was definitely giving me errors to do with the URLs I was posting (see my reply), but now it seems to be accepting long URLs fine... So dunno what I did :S
But still, the thing I mentioned about making everything between the CODE tags plain text, you might want to look at! :|