• <!– wp:paragraph –>
    <p class=””>This review is for the Pro version of this plugin.</p>
    <!– /wp:paragraph –>

    <!– wp:paragraph –>
    <p class=””></p>
    <!– /wp:paragraph –>

    <!– wp:paragraph –>
    <p class=””>I’ve had this plugin on my site for a little over two years. Foremost the support for it is awful. You might get a reply, and it might be helpful.</p>
    <!– /wp:paragraph –>

    <!– wp:paragraph –>
    <p class=””>It doesn’t categorically do everything it says it does, as easily as it implies. I even contacted the devs prior to purchase with specific questions regarding theme interference and customizability, which were all met with affirmations of functions that would meet my needs. But no.</p>
    <!– /wp:paragraph –>

    <!– wp:paragraph –>
    <p class=””>Out-of-the-box, it’s easy to install and integrate into Patreon. However, the documentation is poor beyond those functions. If you use the base editor in WP you will fare better than with a more robust theme. If you don’t have a code-level ability to work with shortcodes, this plugin will be problematic for you.</p>
    <!– /wp:paragraph –>

    <!– wp:paragraph –>
    <p class=””>The post type page functions (buttons) that are added aren’t easily controllable with other themes (Divi), or at least not without editing site code. The hooks added into post types that allow users to login via Patreon to see site contents are not obvious in how to configure. There are options for sidebar widgets, a button lower in the page, sectional prompts. It isn’t clear on initial examination which are automatically placed on post types and which truly are optional, if you have to use the side bar widget, etc. The post type button natively appears at the bottom of the page and theoretically can be moved. It doesn’t move higher on the page when I adjust it, even when I turn off my theme. It’s not my theme causing the button not to move. Also, I can’t troubleshoot my patrons who can’t access the locked content because there’s no sandbox option to see what they are seeing so that I could maybe talk them through it.</p>
    <!– /wp:paragraph –>

    <!– wp:paragraph –>
    <p class=””>Tech support is very quickly responsive, though their answers aren’t thorough and don’t have existing, clear documentation to point to for further depth. There is NO DOCUMENTATION for patrons who can’t access content, and I don’t know how to blindly walk them through their end of it. This plugin is a great idea, but it isn’t there yet for flexibility, ease of use, or thorough documentation. And really, there’s not a better replacement plugin. It’s poor business that you have to purchase this plugin first, and then be stuck with it when it doesn’t work properly.</p>
    <!– /wp:paragraph –>

    <!– wp:paragraph –>
    <p class=””>Also, the big thing that would push this into must-have as far as functionality goes is if it would auto post back to Patreon when new blog posts are available on my site. The devs said the Patreon API won’t allow that.</p>
    <!– /wp:paragraph –>

    <!– wp:paragraph –>
    <p class=””>I can’t say that I’ve lost patrons because of this plugin but it has caused a lot of confusion and explaning on my end to teach folx how to use it. </p>
    <!– /wp:paragraph –>

  • The topic ‘Has potential’ is closed to new replies.