magdamunro

It’s all very touching to see wangguard.com being up again and that satisfied people show their gratitude, but may I suggest that some of you help José market the Wangguard plug-in as well as the indiegogo campaign? I do not think the slogan “Make a donation no matter how small it is. In other case, I will be forced to close down WangGuard” is a winning strategy even if this may be true.

No matter if you’re a current user or a new one what you want is to know if the service is reliable and you need to know what good it does if you use it as well. Only José can guarantee that of course, but by lifting up the central attraction points that make people realize why they need Wangguard people might want to back this.

27 backers? I think there could be a lot more than that.

Thanks for the link!

• This reply was modified 8 years, 1 month ago by magdamunro.

Actually that should read: “If there are 10 000 users of Wangguard and 3000 that feel like signing up for server checks and each pays $3 a month, that’s $9000 a month. Best paid annually I guess.

Wait a minute… Wangguard is donation-ware? I think I missed this detail. I’m not sure how. I just saw the levels of traffic you need to reach to have to pay a fee and thought that was the business model. Maybe the donation bit should have been bolded.

I haven’t seen the value of Wanguard so far as i just installed it, but it seems unique.

I still don’t get why a developer would stop service before even attempting to change communication or installing a new scheme. I distrust anyone doing business this way, however frustrated they may be.

Having basic functionality in a freemium version and server checks at a fee would maybe be a more viable model. But maybe sharing info is central to the workings of Wangguard?

If there are 10 000 users of Wangguard that feel like signing up for server checks and pays $3 a month, that’s $9000 a month. Best paid annually I guess.

I think a problem with this product space is that it’s hard to see the real value of something that is removed. Maybe built-in statistics could be a help here communicating this value?

• This reply was modified 8 years, 1 month ago by magdamunro.

@tjdurden, No, this is not correct. You can use Anti-Splog as is (if running in multisite mode), but without server checks for free according to the makers. Granted the latter is what it takes to achieve something like Wangguard, so you’re correct on that level of usage.

• This reply was modified 8 years, 1 month ago by magdamunro.

This seems well-intended and is yet very confusing. If the income was a problem did anything stop the developer from setting up a different pricing structure? Was it the competition? If so, how are donations going to change anything?

I just don’t get it.

I understand if you supply something that is basically freemium and the premium version doesn’t take off for some reason. In this case it would seem it’s the amount of requests that maybe were priced too generously? Or the competition was better or the need wasn’t as ongoing as thought? But if a model doesn’t work you need to change it and communicate the need of the changes to your users. Right?

I don’t see how users with needs greater than the license has set could circumvent the given pricing structure. All of which (the tool and the presented pricing structure) attracted me in the first place as it seemed reasonable.

To claim your product isn’t appreciated enough, with 10.000+ installations according to www.ads-software.com and 4.6 out of 5 stars in ratings, seems just odd to me.

Maybe, what’s really needed is a community communication how much wangguard is actually appreciated? Personally, my trust has eroded in just a few hours. I rather pay more for something else.

• This reply was modified 8 years, 1 month ago by magdamunro.
• This reply was modified 8 years, 1 month ago by magdamunro.

Anti-Splog seems like an alternative but is

“only compatible with Multisite installs”

so I can’t use it. I’m not sure what a Multisite installation means in this context. Also it is untested with the current wordpress version.

You can get it for free I think but to get wangguard like server checks you need to pay for an API. I’m not sure if it’s available separately or only as part of the WPMU DEV Membership.

• This reply was modified 8 years, 1 month ago by magdamunro.

What does

don’t see that people appreciate WangGuard

even mean?

The plug-in has 4.6 out of 5 stars and the author sets his fees himself based on usage.

If the author decides to call it quits for whatever reason, then why not delist the plug-in from wordpress as a first step? To just do it out of the blue seems quite odd to me. There must be more behind this story.

So what are you migrating to? I just got on board less than a week ago.

• This reply was modified 8 years, 1 month ago by magdamunro.

ZenCache was actually a better name. Just installed Comet Cache and it’s noticing changes, though is maybe not so much faster than no cache yet. I need to look into Gzip and tweaks.

I’d like to know this too.

Nope, the spelling of variables as “enquirey” is in widespread use in this product.

I forgot to mention we are using the “Product Enquiry for WooCommerce” plug-in. The entire plug-in is using the wrong language.

It’s unclear to me if “translate the plugin” means “Product Enquiry for WooCommerce” isn’t ready for displaying forms in other languages or if this is regarding the plugin itself.

So is there localization support for displayed tabs and forms? Or not?

OK, after having turned off caching and back on again, only three instances are in the wrong language.

It’s the woo_cart_emtpty_button on the cart page, the #tab-product_enquirey on product pages as well as the contents of the enquiry form and the cart-contents that says “items” instead of the proper localization term.

Interestingly the first two are spelled oddly. Looking for template errors now.

Most ISPs worth their salt will allow for using PHP 5.4. Check if it isn’t an option in your case as well.

I also renamed plugins prior to that. This world too.

Update:

We solved this issue by upgrading PHP to 5.4.40.