• Theunknown1

    (@deexgnome)


    There are a lot critical things missing. You cannot close a bug, you cannot edit it.. yust senseless

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author jquindlen

    (@jquindlen)

    Thanks for trying out my beta software. I can close and edit bugs just fine, just click on an issues status and change it to closed. Edit an issue? Just click on it. It’s all real time ajax editable, just click and edit, then save. Maybe you have a javascript conflict or something preventing you from accessing those features, but instead of going straight to a 1 star review how about you instead help me work out what your issues are on the support forum so that this software can get better? Thank you.

    Justin Greer

    (@justingreerbbi)

    I want to chime in real quick. I have downloaded your plugin and did a real quick run down. The plugin seemed to work but I can see why the plugin would not work for all.

    Check out this screenshot when adding a component
    https://postimg.org/image/61v0rva05/

    This notice comes up all through your plugin. I would advice that you update your $wpdb:escape() calls to use $wpdb:prepare(). Depending on the server configuration of your users, these errors could cause it not to work ??

    Plugin Author jquindlen

    (@jquindlen)

    Justin, thank you for the specific and valuable feedback. I removed the depreciated $wpdb->escape() calls. This notice would only cause issue on testing servers, and even on mine the notice did not stop the plugin from functioning correctly. However, you are correct that in some debugging situations those notices can cause the ajax calls to totally fail. Easy fix though for an easy problem. Another user pointed out another minor display issue as well. Both issue are patched in beta version 0.9.13 available now. Thank you for your feedback.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Mostly not working’ is closed to new replies.