Hello, after the last next gen update the single vote menus where moved into the single gallery managers (when you click on a gallery and where you can sort the pics etc)
Today I updated the voting plugin and now it’s like before, the voting menu is next to the gallery selection and it doesn’t work, which is bad, I was so happy that it worked yesterday.
Plugin Author
shauno
(@shauno)
I screwed up with a change to 1.6.1 that I didn’t test. 1.6.2 should work again.
Sorry, I’m, currently on some strong pain meds that makes me make stupid mistakes from time to time. I will try to test better next release (which may or may not have ajax voting…)
3 cheers to pain killers, time off work, and wordpress!
thanks for the reply so I know whats the reason 🙂
Get well soon.
Hey no worries shauno. Your voting plugin is awesome, and you’re appreciated for your contributions to the WordPress community.
Have you considered merging it with Alex Rabe on this? It might be a good idea for you 2 to work together, so that the integration would be better, and it won’t be so taxing on you as well.
You only live once, so take good care of your health!
yeah think so too. Thank you so very much for the quick fixing. Your Plugin is great. Thanks Thanks Thanks.
I found a bug.
In image browser mode for nextgen gallery, and like/display mode for nextgen voting.
Problem Description:
After I “thumbs up” an image, the url is amended with a “&r=1”. The links for the “Previous” and “Next” buttons of the image browser would also include the “&r=1”, and what happens is that all subsequent images will automatically be “liked” the moment the “Previous” and “Next” buttons are clicked.
I found this bug in 1.5 as well, and had to clear the database entries manually to reset this.
I am currently using a modified version of the dropdown to serve as a workaround. Instead of having 10 drop-down options, I reduced it to only 1 option, with a hidden value of 100. Therefore reducing the 10 options to just 1 “Like” option.
Starting from Line 1046:
}else{
/* dev note. you can set any values from 0-100 (the api will only allow this range) */
$out .= '<div class="nggv-image-vote-container">';
$out .= '<form method="post" action="">';
$out .= '<input type="hidden" name="nggv[vote_pid_id]" value="'.$pid.'" />';
$out .= '<input type="hidden" name="nggv[vote_image]" value="100" />';
$out .= '<input type="submit" value="Like!" />';
$out .= '</form>';
$out .= '</div>';
Plugin Author
shauno
(@shauno)
Good catch macnetis, and elegant work around (not too many people even look at the code, let alone understand and alter it!)
When the plugin was written, it was written to a simple spec. Since then I’ve expanded it, kind of haphazardly 🙂 It was never meant to have anything other than drop down ratings.
I am in the process of ajaxifying the voting processes, and that will solve this problem.
It’s good to know that you back into active development.
Feature request: being able use custom thumbs up images per child theme. I currently hard-coded the image link into the plugin directly. Not a huge priority though.
Take care, and hope you have a speedy recovery.
Plugin Author
shauno
(@shauno)
I’m back at my parents place for the Christmas / New Year break. Which means I will be avoiding extended family and holiday guests by hiding behind my laptop quite a bit over the next 2 weeks or so 🙂
That hopefully means more coding on side projects like the plugins.
You could possibly point the img urls for the thumbs up to the themes directory, maybe with an {else} catch back to the plugin dir if none found in the themes. Just as a hack for now?
