leslie1019wp

Hi C!

I replied back privately, but I’ll post here for sake of posterity.

The info you provided on the plugin and Appticles not being interdependent was incredibly helpful. I was confused about that.

As for the technical items, we’ll watch and thank you for connecting me with A. I’ll notify her if something technical occurs.

And for anyone who may read this, Appticles is clever technology. Delivering a mobile app through the browser instead of publishing in the App Store or Google Play is time-saving at the least and easier for the reader’s experience.

If people weren’t to leave reviews, then there’d be no review section for us. I’m completely permitted to review a plugin I’ve used and experienced, as well as the support of it. They are candid opinions based on experience.

I get it. You don’t like negative reviews. I don’t like being dismissed when I give you information. You never offered support for an hour or two. Ever. When I offer information back, you get mad. You also told me I had to pay for expanded functions. I presumed you meant like the ones AAM promotes in the plugin. Did you mean something different? There was literally no offer for other support made to me. You left it at that with me.

I work with many other plugin devs, starting on their free version, and then moving to their paid version or other paid services, I’m well in the position to speak on this. Truly any customer who is using your plugin is. Any feedback is good feedback, at least that’s how you should look at it. I think you have a very odd definition of who a customer is. We’re all customers. The plugin is part of a strategy to converting customers of the AAM into other areas you offer. Remember when we emailed on that?

The site takes 2.42 seconds to load. Speed tested and verified. And it uses W3TC + CDN. Now, you may be in a part of the world which isn’t close to a CDN version of the site. But, there’s nothing I can do about that. I’m on a dedicated server which is a large, powerful container. Mute point on the plugins. And everyone loves my websites, all of them. I don’t need luck, I create my own success.

I never said I can’t handle dev language. I don’t walk around speaking it random strangers on the street. I think it would be helpful if devs, such as yourself, found better ways of explaining themselves, especially when there are language barriers. That’s not a slight, that’s an observation, and it’s one I think you can benefit from as I had difficulties understanding what you were trying to communicate. But, I do acknowledge your effort, though, in trying to communicate.

W3 Total Cache is not some weird plugin. That made me laugh when I read you wrote that. My site isn’t remotely complicated, but understanding you think it is explains your context of understanding to me. It sounds like it’s over your head.

And yes, I do understand the word “hooks.” I have coding experience. I prefer to use regular language with others rather than make them use mine. I happily shared with you I created a hook in Edit Flow to at least hide the publish option from writers so they didn’t inadvertently hit it, when saving drafts. How is it you think that’s horrible I shared a workaround, I have no idea. That’s a positive!

Alas, I still stand by my review. Poor support, modifications in hook action (see your changelog notes for version 2.7- one can also compare the files visually to observe the changes.)And you were very dismissive of a sincere concern which suddenly occurred. Please recall, I said all was working great on 2.6. That last update has caused some issues in a few areas. Trying to sell me on other things, though, when it’s already not working just isn’t going to work with me. And an offer for other suport was never made.

If things change, and you figure something out about the plugin, or decide to take another crack it, I will absolutely consider modifying my review. Until then, we’ll just keep on keeping on with the workaround I told you about. Let’s just take a break from this back and forth, for now. Let’s see what develops. If you want to know about the Edit Flow hook, you are welcome to email me and I’ll share it with you privately.

Have a good week, Vasyl 🙂

As an update, I added a hook to Edit Flow to at least keep the “PUBLISH” button from appearing to writers. This way they won’t inadvertently hit PUBLISH when the mean to hit SAVE.

I look forward to updates on those hook issues with AAM which began in 2.6 🙂

Oh Dean,
What dishonesties you tell.

OIR was provided the information it was posts, not pages, where the issue was occurring. Nice try at being deceptive, but your are busted. You’re proving my point for me.

You wasted a lot of time with nonprofessional nonsense instead of actually providing support. WPMU’s SLIDE IN plugin works perfect, and they have great support and community around their products.

Now, I get to post all of my screenshots.

In addition to the link I initially provided, OIR was told it was a post, not a page issue. What I thought was just laziness, has been replaced by outright dishonesty.

When I sent it over to Ruel, I was polite about it, even used emoticons. And now you’re telling a false story. But, the response was lackluster. Apparently it is terribly painful for you to spend 15 seconds to read, or to click, or to even be honest. But you have no problem wasting my time will rubbish that doesn’t resolve anything.

http://www.manofsteelfanpage.com/wp-content/uploads/2014/05/oir-2.jpg
http://www.manofsteelfanpage.com/wp-content/uploads/2014/05/oir-1.jpg

Ruel’s response was polite, but it was incorrect and shortsighted. The ms slider isn’t an issue impeding function. If it were, the screen cap you post would reflect that. So, thank you for proving yourselves wrong.

Dean’s response. Apparently he doesn’t read.

http://www.manofsteelfanpage.com/wp-content/uploads/2014/05/oir-2.5.jpg

If you’re going to take the time to respond, respond correctly and with professionalism, instead of like an insolent toddler throwing a temper tantrum. And make sure you are correct, otherwise, you look like a fool.

I encouraged Dean to be professional about it. OIR had been given the info it was a post, not a page, issue. Instead, he wished to spend time not providing support, being hostile, and never furthering the advancement of understanding.

http://www.manofsteelfanpage.com/wp-content/uploads/2014/05/oir-3.jpg

There’s not other information to be given. So what’s his excuse for not providing support? Oh, that’s right, he’d rather insult customers because that’s what he considers a good business practice.

http://www.manofsteelfanpage.com/wp-content/uploads/2014/05/OIR-3.5.jpg

See that? He admits to acting unprofessional. 14 hours before receiving his temper tantrum email, I had uninstalled the plugin. It was clear he values hostility and fighting over actually supporting the product. He asked me to send it to ZenDesk. He asked. Then, this is what happens.

Yep, they are running a racket. It doesn’t work with every theme. They don’t provide support.

I stand by my final words, at least I thought this was finalized until I saw the support forum where he was having a conversation as a party of one (some schools of thought are that represents paranoia and deception. Now, we see why.) It was very clear this guy isn’t capable of meeting the representations they make for OIR.

I installed WPMU’s SLIDE IN Plugin. It works great with WSIJA/ Mail Poet via form shortcode.

While OIR is making a mess of themselves and ruining their brand (something they have no control over,) the competition in the marketplace has cemented themselves.

15:39 reviews are negative for this plugin; That’s 2.6/5, half of them. There’s a reason why. Now, we see what that reason is.

Two things are very clear to anyone who reads this: 1) OIR doesn’t do what they say they will do, and 2) WMPMU has better plugins.

You are out of gas.

Vasyl,
I’m updating this support post to correct what you’re responded with and to reflect what is factually occurring.

There isn’t anything “weird” occurring with caching. W3TC is optimally configured to exclude the AAM path. I feel like you aren’t remotely familiar with W3TC.

With the last update, it negated the exclusion. The issues I’m experiencing with users who are restricted to accessing things, being able to access them is due to changes you had to have made in the hooks. That’s the only way it can be occuring. This is evidenced by the fact it worked until the last update.

It doesn’t require “deep investigation,” it’s actually pretty straight forward. If a user isn’t checked to be able to publish posts, s/he shouldn’t be able to publish posts… but yet s/he is. That’s a hook issue which has occurred with the last update.

Telling me you can’t provide support isn’t the same as telling me you won’t provide support, and then telling me I have to buy premium if I want AAM to address their own bug. Like I said, I won’t test drive a car without the tires, so don’t expect me (or anyone) to purchase the car without the tires, either.

The free version of the plugin should work correctly. Premium would expand the functionality and features available. But to expect a customer to have to buy premium, when the problem is the hooks in your last update (and I know you made them, you had to in order for this to occur) is pretty poor. Ultimately, this reflects on you. Not me.