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 :)