ILLUMINICE

[ILLUMINICE]

I just received notice from Envato that my refund was approved. I’m glad that you chose not to prolong this, and hope you understood my point of view.

Thank you for the refund.

~ Michael

• This reply was modified 8 years, 9 months ago by ILLUMINICE.

[ILLUMINICE]

What company is the “Senior Support” rep with, wpWave or Envato?

My understanding is that the plugin author only needs to approve the refund request at Envato for it to process. I’ve already submitted the refund request two days ago.

I have checked many other tickets related to refund requests (both here and on Envato), and what I saw was a pattern of denying everyone’s refunds unless you agreed that the plugin didn’t function as designed within their websites. The problem with that is you can always say the plugin was working as designed, even when the customer is not satisfied for one reason or another.

I think you’re abusing the refund policies on Envato and are purposefully being evasive. That’s what I see in the many refund requests that have been made.

If a customer is not satisfied with your product and requests a refund within a reasonable amount of time, that request should be honored. So long as you can control/revoke those licenses, there’s no reason to deny a refund.

What you’re really doing here is creating a lot of very unhappy customers, not because your plugin is poorly designed, but because you’re not showing basic respect for their money. It’s good business to have a 100% satisfaction guarantee. Not only does this look good to potential customers, but it shows your current customers respect.

This isn’t honestly about the small amount of money to me. It’s about showing respect for customers. I saw what other customers of yours have been going through to obtain a refund, and I didn’t want to go through the same thing.

~ Michael

[ILLUMINICE]

Suman,

There is no reason to have another person look at my refund request. I requested the refund within 24 hours of my original purchase. I should be refunded without delay.

It seems to me like you are purposefully delaying my refund so that I will perhaps go away. This is not a way to treat customers, and I will not stand for it.

I’ve already reported what is going on here to Envato. All one has to do is look at all the refund requests reported for this plugin and the obvious delay tactics you and your company are using to avoid issuing a refund. I’m wise to this.

~ Michael

[ILLUMINICE]

Suman, please don’t fight me over $21. If anything my previous posts show the fact I wasn’t completely happy with certain aspects of the plugin (despite the fact I’ve been saying your plugin is overall well-designed). As I stated in my refund request, this plugin simply didn’t meet some of my requirements. This doesn’t mean the plugin was necessarily malfunctioning.

A refund should never be denied within 48 hours of the purchase (in my case more like 24 hours). So long as the license key is voided, there’s no reason to deny a refund. More importantly, this would be a show of good customer service and a satisfaction guarantee.

Please also take my word that I have already completely uninstalled the plugin and won’t be using it again.

~ Michael

• This reply was modified 8 years, 9 months ago by ILLUMINICE.

[ILLUMINICE]

I understand your point, but disagree for this reason…

There is an obvious difference between a custom login form and the default login form used by WordPress. If your intention is to hide the fact you’re using WP, then surely you don’t want someone seeing that default WP login page.

You’re correct that someone could technically try to login to the admin using a custom form, but why allow anyone to access the default WP admin login page?

I’ve never felt comfortable making the WP login page public, and have gone through great efforts in the past to hide it, even using htaccess authentication on it (as a secondary layer of protection).

You and I both know that there’s no way to 100% hide the fact that you’re using WordPress, but still, why allow anyone to access the default login page if you don’t have to. I like the implementation of a URL rewrite for the login, but showing that rewrite URL in a view source does partially defeat it’s purpose IMO.

Anyway, that’s my take on it. By the way, I do think you have an overall great plugin here. Please don’t take my response as a complaint. This is just an answer to your question/logic.

~ Michael

[ILLUMINICE]

Just a quick fyi that I submitted an official refund request through Envato for you.

Thanks!

~ Michael

[ILLUMINICE]

Hi Suman,

Thank you for replying to both of my posts…

I had seen this in your FAQ after writing this post. This is just something I don’t agree with fundamentally. If there is a way that URL can be hidden when viewing the source, then it should be. What’s the point of a private URL if anyone can obtain it with a view source? Of course I would understand if there was technically no way to hide this.

The _main is a little awkward, and I’d recommend finding another solution for this. I did notice another plugin similar to yours that uses random numbers for the themes instead of a custom url. Perhaps this solution makes more sense for your plugin as well. I think it would better match how you obfuscate the plugins.

~ Michael

[ILLUMINICE]

Hi Suman,

I appreciate your timely responses to both of my posts.

I didn’t realize that clicking “Undo Previous Settings” would restore back the previous settings in this circumstance. It is a little unusual compared to how other plugins function when deactivating/reactivating.

Regarding the htaccess rules, they definitely were not automatically removed when I deactivated the plugin. I allowed the plugin to add them automatically, so they should have been removed like you mentioned. I don’t know why this didn’t work on my end, but it definitely didn’t.

~ Michael

[Author]

Posts