invalid licence - rc 4.1

[Dugi]

i already submitted a ticket but wanted to see if anyone else is getting invalid licence page or just me

really don't have luck with this vivvo thing

Originally Posted by Dugi

i already submitted a ticket but wanted to see if anyone else is getting invalid licence page or just me

really don't have luck with this vivvo thing

I have the same problem.

[boccio]

Unfortunately, this problem is purely technical (due to licensing software) and couldn't be avoided.

If you install RC1 on separate domain/IP then your current live Vivvo site is, the system will detect IP change and flag your license. As you can see, we solve this issues momentarily via Support Help Desk, but I definitely agree it is a nuisence.

Two easiest workarounds:
1. Contact support if your license is flagged
2. Install RC1 on same IP/domain where your current site is

[Dugi]

i have a developers licence boccio. This shouldn't be happening full stop
do i need to request a new key file every time I build a new vivvo site or is the one that was sent to me this morning going to work on all of my sites??

[boccio]

I believe the support engineer already addressed these questions you have, but for the benefit of others, I'll post publicly as well.

For Developer license holders licensing mechanism is changing (only technically speaking), and you need to contact support only once to reflect all changes. So no worries, you won't need to request new key for every website you have.

Until now developers deployed websites with their own key, but now they (you) will have a separate one for every website deployed. Of course, for your convenience these keys will be distributed in sets of 10 keys, so you need not contact us for each site you deploy.

[RichII]

I had a license with another company and they went to this model. Pretty soon they started monitoring licensed sites and were dictating what type of sites the software could be used for. No hate, no porn, no warez, etc... at first but then they started screwing with users that had sites representing opposing political and religious views. After that it went right in the toilet. A user could only create sites that they personally owned the domain name for, then they could only have so many personal sites of a matching type. The vendors would just kill the license for any site that didn't fit their mood that day. Anyone here who used that software will know what I'm talking about.

Vivvo can now selectively kill any site that I build. That's more vendor control than I signed up for. Guys, I apologize for being so blunt but this truly sucks.

Rich
________
CANNABIS SEEDS

[boccio]

Rich, don't you think you're being just a little bit paranoid

If you think about it for a little bit, the licensing model changed only for Developer license holders. Standard and Professional remained the way it is. Logical conclusion to this is that we already monitor domains our Standard and Professional licensees use.

Is single one of them closed/banned for three years we're in the business? Don't you think you'd already know about it, somewhere on some forum?

The pure reason behind shifting to this OEM-style for our Developers and Corporate license holders is their security. We have been approached by Dev's which expressed concern about deploying websites with their own license, and possibilities of misuse to that license by a client. Now, this is solved. And this is the only reason behind it, we really have better things to do in our lives than to play the Big Brother game

[RichII]

When things got bad I had to rebuild 4 sites on a new platform. I ended up owning a license that I couldn't trust and ultimately just had to eat. I wouldn't call myself paranoid, just experienced.
________
Vapir Oxygen Vaporizer

[Alex]

I assure you there won't be such problems with us As previously said, all Standard/Professional licenses are bind by domain/IP, and not a single one in three years had any problems. I suppose that counts for something.

[RichII]

From the latest Developers license:

Developer License:
For the version(s) you are licensed for, you are granted a license as a single individual to install and run the SOFTWARE PRODUCT royalty-free with an unlimited number of different solutions to an unlimited number of web servers, provided they are developed solely by you. The term "different solutions" is understood to mean non-identical, non-"shrink-wrapped" applications to be resold or re-licensed by you. You may not distribute the product with more than 10 copies of an identical or similarly-functioning ("shrink-wrapped") solution or application.
At no time may the SOFTWARE PRODUCT be used by more than one individual at the same time for development purposes - nor may the SOFTWARE PRODUCT be distributed for use with applications other than those developed by you.

We must apply for sets of keys now with a limit of 10 at a time. We can only create 10 sites of any similar functionality now. 10 news sites, 10 magazine sites, etc... and then we have to ask for more keys. If we have already created 10 news sites then according to the wording of the license and the new keys limitations you can legally say "No more keys for news sites". That would make the license useless if it was purchased for the purpose of developing news sites. So then what, purchase a new developers license? Promise to never develop another news site? This whole switch up basically turns the developers license into a '1/2 off for 10 sites' deal.

Call me paranoid all you like guys but this doesn't look right to me.


Rich
________
BUY VAPORIZERS