Fiddlesticks. I just noticed that, when you press on Flag It, the javascript doesn't show the flagging reasons and doesn't allow you to flag. (Curses javascript under his breath.) Is anyone who's on 1.5.2 have this working? As always with javascript, I'm at a loss as to where the problem is.

Fiddlesticks. I just noticed that, when you press on Flag It, the javascript doesn't show the flagging reasons and doesn't allow you to flag. (Curses javascript under his breath.) Is anyone who's on 1.5.2 have this working? As always with javascript, I'm at a loss as to where the problem is.

Today, Google sent me a visitor to a post (thank you Google), but the URL it sent the visitor to ended in /alert/2. I assume that means Google is spidering links from the function show_post_extras in this plugin. We might want to change the code in this function to:

Today, Google sent me a visitor to a post (thank you Google), but the URL it sent the visitor to ended in /alert/2. I assume that means Google is spidering links from the function show_post_extras in this plugin. We might want to change the code in this function to:

Do you think we should remove the alert flags to be a separate plugin. They seem to be quite different to the voting system itself?

Click to expand...

You're asking the wrong guy My preference is always to have less plugins - not more. There are standard features that all CMSs should have, and if a user is logged in, I think flagging is one of them. So, to me, it should be part of core

The only time flagging wouldn't be appropriate is if you don't allow users to login. But, as long as this is core functionality and the admin is the only one who logs in, it wouldn't make a difference as they aren't going to flag anything.

There are a few reasons why you might get an "err" with this plugin but probably the most common is simply upvoting twice. The plugin checks to see if a vote was already recorded and, if so, responds with "err." If you refresh the page and the upvote shows, it was just a double-clicking problem. If it doesn't, let me know and we can troubleshoot the Javascript error together.

Attached Files:

Just to confirm I understand what you're saying: you have a post that had enough votes to be considered "top" (post_status in hotaru_posts = 'top') and appears only on your Popular/Top Posts page. Then you downvoted below the top threshold (which, according to your settings = 2 so the vote count now = 1) and the post doesn't show on the Latest page - it remains on the Popular page?

The code that does this is lines 133-136 in /content/plugins/updown_voting/libs/UpdownVotingFunctions.php. Please look at the post_status on the post in the hotaru_posts table while the post in on the Popular page. Confirm that the post_status = 'top' and the post_votes_up >= 2.

Then downvote the post and look again at the post_status - did it change to 'new' from 'top'? Also look at the post_votes_up column - did it change to the correct number?

I set post 2 vote to popular.
post get 2 votes, then it shows in front page.
now post_status top
then i remove vote, and put a down vote also. now post vote is 0 still not hide from popular page.
still post_status top.

I set post 2 vote to popular.
post get 2 votes, then it shows in front page.
now post_status top
then i remove vote, and put a down vote also. now post vote is 0 still not hide from popular page.
still post_status top.

Click to expand...

Can you please replace line 98 of /content/plugins/updown_voting/updown_voting.php with the following and try again?

That's what I suspected - your settings aren't being either retrieved or brought over. Please put line 98 of \content\plugins\updown_voting\updown_voting.php back to the way it was. Next add the following code to line 99 of \content\plugins\updown_voting\updown_voting.php: