Releases: pixelbart/helpful
Releases · pixelbart/helpful
4.4.37
Enhanced
- You can now use the
helpful_get_most_helpful( $limit, $post_type )
function to output the most helpful content with PHP. It will then return an array with all the necessary information. - You can now use the
helpful_get_least_helpful( $limit, $post_type )
function to output the least helpful content with PHP. It will then return an array with all the necessary information. - You can use
[helpful-feedback]
to output the feedback of the current post.... - You can use
[helpful-feedback post="12345"]
to output the feedback of a specific post. - You can output the feedback of the current post with gravatars using
[helpful-feedback gravatar="1"]
.
4.4.35
4.4.34
4.4.33
4.4.32
4.4.31
4.4.30
4.4.29
Changed
- The deactivation of nonces now also affects the variables that are transmitted to Helpful with wp_localize_script. The helpful_frontend_ajax_vars filter can still be used because it is always executed at the end. The ajax_data variable is not completely removed with unset, otherwise there can be problems if you have not checked in your scripts whether the variable exists. Instead, an empty array is returned if the nonces have been disabled.
- The tag conversion now always checks whether a tag is contained in the string before returning the content of the tag.
- The vote status of the person who voted is now stored in a global variable
$helpful_votestatus
for the one vote and then subsequently checked if the variable exists and the type is determined that way. This should ensure that there are fewer database queries per vote.
Props @verygoodplugins for his feedback in the forum.
4.4.28
Fixed
- Fixed a bug where Helpful did not always detect whether the user voted positive or negative. Instead of passing the type of vote through the feedback form now, the value from the database is used.
- Fixed another bug where the feedback text was always overwritten. This was due to the fact that every time after the text for pro or con was drawn, the text for fallback was drawn. This was due to the order. Now the fallback is always used first and then checked what the vote status is. And then the fallback text is replaced with pro or con. This should eliminate the problem that wrong texts were shown when a user voted.
Props @verygoodplugins who noticed the bug and reported it: view post in forum