Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Arul

    (@arulpr)

    While using content filter dont use shortcodes as it is very inefficient way to do stuff

    http://kovshenin.com/2013/dont-do_shortcode/

    Just yse the following code and not the do_shortcode

    function mage_get_review_average() {
        return mage_reviews_average();
    }
    Plugin Author Maximilian Ruthe

    (@maximilian-ruthe)

    Hi Arul,
    I was unable to reproduce the error you mention, but I did remove the do_shortcode() from the content filter with your above suggestion, hoping that may help your issue.
    This fix is in the new version 1.0.8, which I updated today, which also contains new display options.
    Please let me know if that helped –

    Best Regards,
    Max

    Thread Starter Arul

    (@arulpr)

    I installed it on fresh install and it went through. I think it might have clashed with other plugins I am testing right now.

    Anyway I have another suggestion here.

    When calculating average you forgot to round off averages, so right now it will have ratings like 2.66666 or 1.33333

    In mage_reviews_average function I changed the following code

    $value = round($value/$divident, 2);

    I also suggest that you change comment meta and post meta keys into something a bit more unique

    _mage_rating is according to wordpress developers rule book.

    Thread Starter Arul

    (@arulpr)

    Found another small bug in function mage_update_rating

    instead of using comment approved as string

    $comments = get_comments(array(‘post_id’ => $parent, ‘comment_approved’=>1));

    Use the inbuilt function
    get_approved_comments($parent)

    so it is checked against a boolen. Much safer when comment statuses changes.

    Plugin Author Maximilian Ruthe

    (@maximilian-ruthe)

    Thanks again for the suggestions –
    I implemented most of them in the new version, 1.0.9, as well as with localization compatibility. The custom meta key transition functions are just temporary and won’t be included in the next update.

    Cheers,

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘V 1.0.7 is broken’ is closed to new replies.