Support is poor. An update included changes in hooks, which affected the capabilities. Upon contacting support, Vasyl told me it requires too much work to fix the bug in his own plugin, but yet tried to tell me to buy premium. He also referred to it as a “weird” caching problem with W3TC, when it’s not. The plugin path is excluded from W3TC. This is a straightforward issue with the hook. He also wants to dismiss it because I’m the only one so far who’s told him of this issue. Perhaps I’m the only one who’s contacted him so far, who uses the plugin in the way I do, and is experiencing this issue. Terribly dismissive and washed his hands of it.
- The topic ‘Poor Support’ is closed to new replies.