By Zeosing on Saturday, 14 January 2017
Posted in General Issues
Replies 23
Likes 0
Views 243
Votes 0
Differentiate between support and upgrade domains

From our point of view it is logical that the post was restricted to 5 domains because it is clear that it is unfeasible to provide unlimited support without any kind of cost, it is clear.

But what does not make any sense is that automatic updating (via web) is restricted to 5 domains, because it is understood that when a subscription is purchased for 1 year, the updates are included, and eye do not talk to speak, I put several Example: RegularLabs, Akeeba, Yootheme, etc.

It would be logical to limit the support, something that I see logical and at least for our part has never been mistreated, but the web-based updates should be unlimited. This has to be seen from the perspective of design and communication agencies like ours, when we have to make a blog for a client, it is easier to go to Wordpress, but we see the virtues of EB being done in EB, but That can not be is that after the maintenance is "a headache"

And we repeat that we totally agree with the limit of support, but that of the updates seems to us something that goes against the logic.

Finally, he wants this to be seen as a constructive criticism, not as a simple complaint, since we have since 2013 with its products, and helping (as long as the studio and our clients allow) to translate the extensions.

Thank you.
I agree 100%. Nobody wishes to challenge the concept of the limited / excellent support policy of EB but by not enabling automatic update for non-supported installations leaves the security of all EB customers' Joomla/EB sites in jeopardy. I highly doubt that this is the intention of Stack Ideas but, given that thought, it would appear that this is the unintended outcome of such a policy.
Tom
·
Saturday, 14 January 2017 20:53
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey guys,

Thank you for your constructive criticism and I appreciate this very much. I have been thinking this over and over for many weeks now before we decided to restrict domain updater services but it seems like people are taking too much advantage over this.

Having said that, I do admit that I am now having second thoughts for developer accounts like you guys who have been supporting us all these years and perhaps these restrictions should only be applied to people who truly abuse their Pro / Club license.

Developer plans are often web agencies and companies that implement websites and most of the time do not require much support apart from updating the software to the latest version.

I will post an official blog post about this shortly.
·
Saturday, 14 January 2017 22:11
·
0 Likes
·
0 Votes
·
0 Comments
·
By the way, the primary reason this policy came into play was because some of these developer / pro / club accounts are installing our products on over 100 domains. Some even went to the extend of over 1,200 domains. All these domains are pinging us non stop and on top of that, it is requesting for updates that takes up enormous amount of bandwidth.

Instead of restricting every single developer account, we are looking at a fair use policy where if you have more than 100 sites and tries to use the over the air updater, we will need to upgrade you to an enterprise plan.

Does this sound fair?
·
Saturday, 14 January 2017 22:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark, the idea that you propose, ie if the agency has more than 100 domains have to pay for a superior plan I see it correct and correct, to me as director of the agency I appreciate that if we are making money with your products In a massive way you have to charge more, both for infrastructure costs and for software, but of course putting a logical limit.

To us 100 domains for the developer plan seems logical and successful, and I understand that the business plan would have a lot more.

To us it does seem a good idea and certainly improve our experience with the issue of updates, which to this day is what most questions poses us when it comes to renewing the extensions.
·
Saturday, 14 January 2017 22:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for your input Zeosing but I am a little lost sorry. In your post, you mentioned that it is correct but not a good idea? Or am I misunderstanding you?
·
Saturday, 14 January 2017 22:42
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for your input Zeosing but I am a little lost sorry. In your post, you mentioned that it is correct but not a good idea? Or am I misunderstanding you?


Original post corrected, I missed a "not"
·
Saturday, 14 January 2017 22:50
·
0 Likes
·
0 Votes
·
0 Comments
·
I think the 100 level is a reasonable point to require an increased membership level to a more substantial plan. It helps developers who are likely individuals without staff to assist them, like myself. I am a sole developer and do not have the benefit of having a staff to assist in daily maintenance.
Tom
·
Saturday, 14 January 2017 23:03
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for your input on this, and the restrictions has been lifted altogether for developer / agency bundle contracts.
·
Saturday, 14 January 2017 23:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Mark
Tom
·
Saturday, 14 January 2017 23:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark

I use EB as the next best thing to WordPress as I prefer developing in Joomla.

Maybe look at the EasyBlog Pro structure and remove the unlimited installations - something like:

5x Domain Installations (registered)
12x Months Auto Updates for 5 Domains (registered)
12x Months Support (72hrs response time) for 1 Domain (registered)
18x Professional Blog Themes

This could heavily reduce the abuse of individuals installing EB for free.

Just a thought……
·
Saturday, 14 January 2017 23:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for the input on this Steve! By the way, EasyBlog 5.1 will be even better, I am super excited for the new composing experience and hope that it would surpass the user experience than what Wordpress has to offer.
·
Sunday, 15 January 2017 01:02
·
0 Likes
·
0 Votes
·
0 Comments
·
That sounds great , when are you looking at the RC (release candidate)?
·
Sunday, 15 January 2017 01:10
·
0 Likes
·
0 Votes
·
0 Comments
·
We don't have an ETA for it yet but do check out our blog often as we do post updates there
·
Sunday, 15 January 2017 14:05
·
0 Likes
·
0 Votes
·
0 Comments
·
I am extremely disappointed that your website has not been updated to reflect the change in your policy. I only purchased EB yesterday and am now finding myself with an outdated version on our live server (we run our project via a Stage and Live server) - it seems that every time I need to update EB I need to backup my Live site to my Staging server, do the update and then move it back again ... which is totally ridiculous!!!

I purchased EB with the understanding that I could install it on unlimited domains (as stated clearly on the site) ... I do not intend to abuse this by installing it on thousand (or even hundreds ... or even tens of sites) but I feel that you have misrepresented the agreement and left me and my clients project with a somewhat inconvenient (I would say 'unworkable') upgrade solution.
·
Friday, 17 February 2017 08:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Chris,

We are not misleading you with anything. You can still install EasyBlog on as many domains as you want using the full package, http://take.ms/SghjO . There are no restrictions in the full package. Only the launcher package is restricted to your licensed domain.

If you are setting up a staging / development site, you would just need to access the site with a subdomain of the main licensed domain.
·
Friday, 17 February 2017 11:31
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Mark,

But the 'full package" installer also fails for me ... I have followed the instructions re: PHP setup and it fails to initialise the database.

My main gripe is that you really should make it clear on your website that there are restrictions with installations - I purchased your product in good faith and now I find myself battling with the installation on a domain that is not my registered 'support' domain. I typically use a different domain for staging than my live sites.

As I mentioned earlier, I have no intention of abusing the system - but it would have been nice if I was made aware of the restrictions BEFORE handing over my money.

See attached images for what is happening on my server when trying to install EB update via the 'full package" method.
·
Friday, 17 February 2017 11:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Chris,

Thank you for getting back to me on this. If the full installation package fails for you, it is unfair that you are accusing us for restricting you from installing it on multiple domains eh?

We did provide the full source and it works for the rest of our customers. Why it doesn't work, we will need to check your site and I have replied you on your other thread
·
Friday, 17 February 2017 12:33
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post