SteemPlus is a lightweight browser extension adding new features to your Steemit/Busy experience: - Voting slider for minnows - Possibility to filter (by tag/resteem/reputation) and sort ( by date/payout/votes) - Switch between Busy Steemit and Steemd by keyboard shortcuts - Delegation of Steem Power directly from the wallet
GNU General Public License v3.0
27
stars
32
forks
source link
[3.1.0.1] Unable to vote via SteemPlus vote slider on Busy.org #168
Complete the on-boarding flow and sign in via SteemConnect
You will be redirected to Steemit.com (if you're already on the site, refresh to ensure the SteemPlus extension is working as expected).
Go to Busy.org and go to your feed.
Select a post and vote on that post using any vote weight.
Environment
Browser: Google Chrome Version 69.0.3497.100 (Official Build) (64-bit)
Device: MacBook Pro (Retina, 15-inch, Late 2013)
Operating system: MacOS HighSierra Version 10.13
Application Version of Testing: 3.1.0.1
Error & Resolution
The reason this particular issue is occurring is due to SteemConnect depreciation, it looks like this area of the code wasn't adjusted following the switchover in a previous release. In order to resolve this, you will want to switch it over similarly as you have previously. The reason I believe this is due to the following error:
vote_weight_slider_busy.js:158 Uncaught TypeError: sc2.vote is not a function
at HTMLButtonElement.<anonymous> (vote_weight_slider_busy.js:158)
at HTMLButtonElement.dispatch (jquery.js:1627)
at HTMLButtonElement.q.handle (jquery.js:1589)
Recording of issue
The following video shows this issue in more detail:
Expected behavior
When selecting vote on a post and using the SteemPlus slider I should be able to vote successfully for a post.
Actual Behaviour
When I select vote on a post and submit the vote, the vote is not cast successfully.
Pre-Requisite
Steps to reproduce
From a fresh install download SteemPlus here
Environment
Error & Resolution
The reason this particular issue is occurring is due to SteemConnect depreciation, it looks like this area of the code wasn't adjusted following the switchover in a previous release. In order to resolve this, you will want to switch it over similarly as you have previously. The reason I believe this is due to the following error:
Recording of issue
The following video shows this issue in more detail:
https://www.youtube.com/watch?v=_barRi-cR9E&feature=youtu.be
Apologies for the poor video resolution, not sure what happened 😕