Feb 28, 2019 07:53 AM
(This post was last modified: Feb 28, 2019 07:58 AM by phlex.)
Hello,
I reported this bug when I first got here, but reported it slightly incorrectly.
First, let's take a look at what happens...
So, what's the problem?
Well, full reply & full edit mode does this just fine. It pops up the anti-spam check, you check it, and your post goes through.
However, quick edit does NOT trigger the anti-spam check.
If you want to test, you can. Include this in your post and then try to quick-edit it. Your edit will not go through because anti-spam is not triggered! :)
Then you can try FULL edit, and your edit WILL go through. The [code] tags are not required for this bug to occur. It happens regardless of whether code tags are used or not. Please note: This is only true if the forum wants an anti-spam check for you. As a new user, all code triggers anti-spam for me. I am not sure if long time members are exempt from anti-spam checks. If full-edit doesn't trigger anti-spam for you, then quick edit will work for you. If full edit DOES trigger anti spam for you, quick edit will definitely not work :)
The problem? It appears that the forum checks for the anti-spam measures to be validated when it receives 'iffy code' in a post.
This is problematic because there is no anti-spam measure on quick reply or quick edit meaning the post never gets edited.
A user can spend a large amount of time editing a post with code in it (with quick edit) and then submit it, just for all of their changes to be discarded.
Quick edit needs to have the anti-spam measure added to its protocol so that the post edit controller can receive the anti-spam validation code & correctly edit the post.
This also occurs any time anti-spam is triggered, or SUPPOSED to be triggered.
If the site thinks you should be spam-checked, it will show the Google captcha box. However, if you use quick edit/reply, it doesn't pop up and your post is discarded. This is not independent to including code in your post - This will occur with the quick feature any time anti-spam is required. So, this will happen a lot for new users, fast typers, and for including code.
Thank you for taking the time to read this bug report. It is easily replicated & has probably led many people to lose their quick edits without them even noticing.
I reported this bug when I first got here, but reported it slightly incorrectly.
First, let's take a look at what happens...
- You make a reply with code in it
- HackForums requires an anti-spam check because of the code in the text
- You click 'I am not a robot' and your post goes through
So, what's the problem?
Well, full reply & full edit mode does this just fine. It pops up the anti-spam check, you check it, and your post goes through.
However, quick edit does NOT trigger the anti-spam check.
If you want to test, you can. Include this in your post and then try to quick-edit it. Your edit will not go through because anti-spam is not triggered! :)
Code
<?php
header("Location: $url");
echo "<script>window.location.href = $url"; ?>The problem? It appears that the forum checks for the anti-spam measures to be validated when it receives 'iffy code' in a post.
This is problematic because there is no anti-spam measure on quick reply or quick edit meaning the post never gets edited.
A user can spend a large amount of time editing a post with code in it (with quick edit) and then submit it, just for all of their changes to be discarded.
Quick edit needs to have the anti-spam measure added to its protocol so that the post edit controller can receive the anti-spam validation code & correctly edit the post.
This also occurs any time anti-spam is triggered, or SUPPOSED to be triggered.
If the site thinks you should be spam-checked, it will show the Google captcha box. However, if you use quick edit/reply, it doesn't pop up and your post is discarded. This is not independent to including code in your post - This will occur with the quick feature any time anti-spam is required. So, this will happen a lot for new users, fast typers, and for including code.
Thank you for taking the time to read this bug report. It is easily replicated & has probably led many people to lose their quick edits without them even noticing.
