amdoolittle

Yes, snark is great from a support team.

My response wasn’t in spite, it was to help others avoid the same problem I encountered: trying a plugin that didn’t work.

Best of luck to you and your efficient method of responding to negative feedback.

A better way to have responded to the initial one star review would have been:

“Hi, we’re sorry to hear you had issues with our plugin. We appreciate your feedback, and want you to know that the issues which led to your low rating have been corrected in the latest release.

We’d love it if you’d download the latest version and give it another try!”

But hey, what do I know? After all, “who would know better than” you, right?

Thanks again for the code correction.

I don’t need “programmer speak”, I can see it for myself in your Trac changelog.

I did give you a single star, and for good reason. You released a product that did not work. Until the 2.2.1 update/fix was pushed, it didn’t deserve more than that.

Could I have asked for support? Yes, if for some reason it were your plugin that I needed specifically. Was I attached to your plugin? Not at all, that’s why I reviewed it based on the experience and moved on.

You’re still ignoring the fact that without the woocommerce capabilities specified for a user in the database, which your plugin did not add, but woocommerce did, then the menu items would deny access. That seems like a requirement to me, even if not an intentional one.

Did you miss the “or at least failed to work” comment? Installing 2.2 alone gave the permissions error. Upon installing WooCommerce, it “automagically” worked! Amazing! While it may not have been a strict requirement, it most certainly was a bug prior to the push of 2.2.1.

If you’d like, I can give you access to a barebones WP install with just the 2.2 version of the plugin installed, unless you can figure that out for yourself too. But who am I to say, you would know better, wouldn’t you?

Heck, it’s even in the changelog.

“Fixed menu access error that sometimes results in “You do not have permission to access this page””

This whole conversation does not bode well for your support team.

It was required (or at least failed to work) prior to the 2.2.1 update without WooCommerce; however, I appreciate that you corrected that issue rather quickly.

Thanks.

Nevermind, you pushed the update earlier today.

Testing again…

Perhaps the prerequisite installation should be put in the installation notes if it was already made known that this was an issue?

I’ll re-rate after getting the plugin to work; however, the lack of complete installation instructions is a bit disheartening. Nowhere in the installation notes or FAQ is “woocommerce” mentioned. Only after a user reported a problem was it brought to light.

You simply need to modify postformat.php under the montezuma editor.

Just replace:

bfa_excerpt( 55, ‘…’ );

with:

the_content();

and your posts will display in the manner specified by the normal options, including displaying the entire post unless trimmed with the “more” tag.

Try the following in your /blog/ subdirectory .htaccess:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_URI} ^/blog/([0-9]{4})/([0-9]{2})/([a-z0-9-]+)/
RewriteRule ^(.*) /$1? [R]
</IfModule>

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>
# END WordPress

The end result is your same query line, without the querystring (? and beyond).