[2.18.2.1] Unable to classify user, an exception is thrown in console

[tobias-g1]

Expected behavior

After clicking on the classification button for any user you should be able to classify a user as either a bot, human or spammer. Upon click of a classification, you should be shown a prompt to indicate the user has been classified.

Actual Behaviour

When you click on the classify button for any user and then click on either bot, human or spammer the classification is not successful and an error is thrown in the console.

Steps to reproduce

1. From a fresh install download SteemPlus here
2. Complete the on-boarding flow and sign in via SteemConnect
3. You will be redirected to Steemit.com (if you're already on the site, refresh to ensure the SteemPlus extension is working as expected)
4. Go to the busy home page, you should be shown the "feed".
5. Wait for SteemPlus to load and you should be shown a label next to the user which indicates if they're a bot, spammer or human. In the event that you don't see this either refresh or ensure that you have the option enabled within your settings.
6. Click on the classification button.
7. When the 3 options for either human, bot or spammer have loaded click on the human option, note that it doesn't work and an error is shown within the console.
8. Repeat step 7 for the option for bot and spammer and note the same issue.

Environment

• Browser: Google Chrome (Version 65.0.3325.162 (Official Build) (64-bit))
• Device: MacBook Pro (Retina, 15-inch, Late 2013)
• Operating system: MacOS HighSierra Version 10.13
• Application Version of Testing: 2.18.2.1 (Updated: July 26, 2018)

Error & Resolution

I assume that there is a new endpoint for this based on the error provided, adjusting this to the new endpoint would resolve this issue. The error provided with the console is as follows:

jquery.js:4 POST https://multi.tube/s/api/classification-report/post 0 ()

You can see the error occurring with the video provided within the next section.

Recording of issue

The following video shows this issue in more detail:

https://www.youtube.com/embed/1bj9x4_kJAk