Roadmap for wp-reactions

I have already had some feedback on wp-reactions, which is great! The plugin was downloaded more than 50 times in the first 12 hours of being online, which I’m really pleased about. What I want to do is share with you guys the direction I will be taking the plugin in. I will link to this post from the plugin page and keep it up to date as new releases come out.

Current Features (version 0.6.6)

Features that are working in the current version:

  • Add reactions to new posts. 100% complete
  • Manage reaction descriptions for future posts. 100% complete
  • Ability to apply reaction updates to all existing posts (not just new ones). 100% complete
  • Add CSS classes to the generated markup to allow authors to style the form as they see fit. 100% complete
  • Include an option to add ‘question’ text before the reaction form. 100% complete

Upcoming Features

Features that I am currently working on:

  • Have different sets of reactions for posts in different categories. 0% complete
  • Add a cookie/IP based filter to prevent users from posting the same reaction multiple times. 0% complete

Future Features

These are features that I want to include in the plugin at some point, but do not have a concrete plan for yet:

  • Stats Tracking. 0% complete
  • Give authors the option of making the reactions mutually exclusive (i.e. Users can only check one reaction per post). 0% complete
  • Internationalize plugin. 0% complete
This entry was posted in wp-reactions and tagged , . Bookmark the permalink.

8 Responses to Roadmap for wp-reactions

  1. baron says:

    hi. Thanks for plugin

    perfect.

    Regards

  2. Carterpants says:

    I’m curious if this action is intended or not: A user is able to click all three options (on your Test blog), effectively “responding” in all three ways.

    Great work! I’ve been trying to implement something like this for a while, glad to see someone has taken this and ran with it.

  3. David says:

    That is the desired behavior. My reasoning is that the options aren’t necessarily mutually exclusive. Using my current setup as an example, a post can be both ‘interesting’ and ‘cool’. It’s not a perfect system, as users could select conflicting responses. A possible ‘solution’ would to include an option on the admin page that toggles whether a user is allowed to select more than one option. Thanks for the feedback, I will keep it in mind!

  4. Carterpants says:

    Ah yes, it would all depend on the options you present the readers.

    ie: options are Fun, Thought Provoking, and Dull

    Something could be Fun and Thought Provoking, or even Thought Provoking and Dull.

    In that case, kudos on letting admin’s tailor the options to fit their blog’s needs!

  5. Geoff says:

    Where is the “post template” that I am supposed to paste the php code into?

    thanks,
    Geoff

  6. David says:

    Open the ‘Appearance’ and click the ‘Editor’ link. Select the ‘Main Index Template’ link from the list on the right. Look for the line that reads ‘< ?php while (have_posts()) : the_post(); ?>‘ . you can paste the code snippet anywhere between that line and the ‘< ?php endwhile; ?>‘ line that appears further down the page. Similarly, you can do the same for the ‘Single Post’ template which is also listed on the right. Hope that helps!

  7. Ales says:

    Are there any plans to develop this plugin further? It seems that the development has stopped…

    Also, will this plugin work well on bigger sites with over 11,000 posts?

  8. David says:

    Thanks for the interest!
    Development on the plugin has admittedly stalled, but I’ve definitely not given up on it entirely.
    I have not tried it on a large number of posts, but I imagine it would cope quite well. If you try it, I’d be interested to know how it performs!

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">