Community mailing list archives

community@mail.odoo.com

Re: SV: SV: Odoo EE database expired

by
Andi Becker
- 10/17/2016 21:54:04
absolutely right Eric. That is why we don't recommend customers to stick with 8 and instead have since months some who already started using 10 and before 9 which will convert to 10 community with custom development.

Fortunately we don't rely so much on mrp and other only enterprise stuff. And the accounting part really needs even in Enterprise Edition a lot of customization to make it even usable for the market here. In that point Version 8 was much better adjusted to the market here.

Actually people will get stuck either way.

Using Version 8 they will run lifetime on more or less than outdated stuff.

Using Version 10 Enterprise they will get stuck if they need for whatever reason away to a more affordable solution - which is often the case with NOGO organizations when funding does not work as good as before to run an enterprise solution. For usual companies it is pretty similar especially in times of recessions or uncertainty like right now!

Version 9 we don't recommend anymore since months as it would be again outdated, even it has meanwhile more modules. But as development for community modules in Version 9 was very very slow and by far did not reach what was available in Version 8, a lot of custom stuff had to be done already und LGPL which won't get shared if the customer does not want to share it, which is unfortunately often the case but understandable as they paid for it. This was much much better with Version 8 AGPL where this question was simply not existing share or not share - and this was for the benefit for all who use Odoo.

I guess that also the development with Version 10 will be pretty similar in puncto custom modules or community modules even we have realized that a lot of companies already published versions for Version 10 even they had skipped the Version 9. Which means in Version 10 are community modules available which aren't in Version 9 probably. Mostly because they started using the new API and are still using the old Version 8 one probably in Version 9.

And again the roadmap for 11 12 etc is not very clear and predictable - also for the fact when the move to Python 3 will come!

But our devs said that most of the Version 10 code will already work with python 3 so that is a very good sign!

Concerning the Latin America contributions actually you don't need to talk about that as this is why we have customers meanwhile. So we with our partners in SA are actually in some way the beneficials that they got stuck and often still don't see that regular updates would bring them much further. It is actually sad as they were - were - great contributors in the past and brought in good ideas which now unfortunately often won't work anymore and companies are looking for other places to get their stuff developed and mostly get it updated than on a regular base.

I am sure if Odoo themselves would provide a much better way to do a version upgrade without breaking basic stuff (which means even their own module stuff) than many more companies would have already switched from 6 or 8 to the latest versions, which would create lots of jobs and opportunities for odoo themselves too.

On Tue, Oct 18, 2016 at 8:12 AM, Caudal Eric <caudaleric@gmail.com> wrote:
You can do that and get stuck forever in v8... Spanish contributors have learnt it the hard way with a similar decision in 6.0 or 6.1

Given how powerful has become v10, this is a move that you need to think carefully. Not saying that v8 is not good enough for most of the business but you need to think as well about evolution.

On Tue, Oct 18, 2016 at 8:57 AM Andreas Becker <andi@lisandi.com> wrote:
I guess all are logged out according to the vendor login structure of the enterprise agreement everybody who uses the enterprise version knows actually before - if they read it!

This fact is one main reason why some customers - who read and understand the enterprise agreement - refrain from using the Enterprise Version and instead use either still Version 8 which is the last fully available Version or who hire developers to implement their additional features, which than often duplicate more or less the Enterprise features by - what is called - rewriting the code of Enterprise Version and adding one or 2 custom features the enterprise Version does not have - As it is LGPL it won't need to be released either and that is than the reason why those additional developments which probably even come from partners won't be visible for the community either, unless the customer releases it.

The database won't expire but the customer won't be able to use it unless he does the custom development described for an enterprise like feature.
For sure customers are very happy to have all their data in a huge database which they can't use and which actually also won't even work in a community version without those additional customizations.



On Tue, Oct 18, 2016 at 6:38 AM, Scott Saunders <ssaunders@asphaltzipper.com> wrote:

Are all users restricted from logging in at this point or will the administrator still be able to log in? Rather than being completely locked out of one's own data it would seem more reasonable to fail gracefully while any licensing mishaps are being resolved.

Scott Saunders
Asphalt Zipper, Inc.
IT/Systems Analyst
(801) 785-0706 x116
On 10/17/2016 06:09 AM, Visti Kristensen wrote:

Users will not be able to log in.

If you want to move it down to community they say it can be done, but I’m sure it’s not that easy as you have to export everything and import it again in community version.

Someone asked that question in one of the XP16 events

 

Med venlig hilsen / Regards

cid:image001.png@01D1D2E1.FE09E170

Visti Kristensen
Direktør / IT-rådgiver

visti@vkdata.dk
Skype: VistiK
Mobil: +45 40452191

cid:image002.gif@01D1D2E1.FE09E170

cid:image003.gif@01D1D2E1.FE09E170cid:image004.gif@01D1D2E1.FE09E170

cid:image005.gif@01D1D2E1.FE09E170cid:image006.gif@01D1D2E1.FE09E170cid:image007.gif@01D1D2E1.FE09E170cid:image008.gif@01D1D2E1.FE09E170

 

VK Data ApS • Bønderbyvej 21 • DK6270 Tønder • Telefon +45 7373 8888 • Fax +45 7373 8878

cid:image009.gif@01D1D2E1.FE09E170

 

 

Fra: Stefano Sforzi [mailto:stefano.sforzi@agilebg.com]
Sendt: 17. oktober 2016 13:59
Til: Community <community@mail.odoo.com>
Emne: Re: SV: Odoo EE database expired

 

so in this case the db will not expire but the customer lost the Odoo EE functionality?

Correct

 

Il 17.10.2016 13:49, Visti Kristensen ha scritto:

Hi.

 

Not really that complex…

Just read the Odoo Enterprise Subscription Agreement.

Newest version is here: https://www.odoo.com/documentation/user/9.0/legal/terms/enterprise.html

 

 

Visti Kristensen

CEO VK DATA ApS

visti@vkdata.dk

+45 40452191

 

Fra: Stefano Sforzi [mailto:stefano.sforzi@agilebg.com]
Sendt: 17. oktober 2016 13:37
Til: Community <community@mail.odoo.com>
Emne: Re: Odoo EE database expired

 

Hello everybody,

I have another use case to solve:

a customer subscribe Odoo EE for 1 year (or 2) after that he didn't renew the Odoo EE.

In this case at the end of period the database will expire?

 

thanks

Il 14.10.2016 17:03, Bassirou Ndaw ha scritto:

+1

 

 

From: Andreas Becker [mailto:andi@lisandi.com]
Sent: Freitag, 14. Oktober 2016 10:35
To: Community <community@mail.odoo.com>
Subject: Re: Odoo EE database expired

 

Very good comment Dominique!


 

With kind regards,
Mit freundlichen Grüßen,
Con un cordial saludo,
Cordialement,
с сердечным приветом,
เรื่อง ที่เกี่ยวกับชนิด,
與親切的問候,

 ANDI BECKER

CEO/General Manager LisAndi Co., Ltd.

--------------------------------------------------

LisAndi Co. Ltd., Phuket, Thailand (lisandi.com)

15/21 M.2 Viset Road, Rawai, Muang, Phuket, Thailand 83130

VoIP:   +49 (0)711 50 88788 50

Fax:     +49 (0)711 50 88788 50

Skype:          lisandi

Facebook:     andibecker

Google Talk/Facetime/eMail:  andi@lisandi.com

--------------------------------------------------

 

On Fri, Oct 14, 2016 at 3:07 PM, Dominique Chabord <dominique.chabord@sisalp.org> wrote:

hi,

 

to be legally ethically acceptable, the server should have prevented
you to create more users, or should block extra-users.
This is forced sale because the admin who manages users is probably
not the one who manages the contract.
Providing a possibility to block the contract will certainly be
discovered as an obligation in the near future.

 

2016-10-14 7:27 GMT+02:00 Fabien Pinckaers <fp@odoo.com>:

 

> Here is the process:
>

 

 

 

> If a customer go above the maximum limit of users he purchases:
> - he gets a message in the home with a link to upgrade his subscription for
> 30 days.
> - if he doesnt upgrade his subscription within the 30 days, the system will
> stop
> - if the system shutdowns, he can still contact us to reactivate it
>

 

 

 

> To avoid any issue, we recommend to: respect maximum number is users or
> contact us to extend if you want more. If the message appears because you
> have more users than purchased, don't wait to much before payment. (Write
> transfers can take a few days to be processed)
>

 

 

 

> --
> Fabien
>

 

 

 

>

 

 

 

> On Oct 14, 2016 5:22 AM, "Kitti U." <kittiu@ecosoft.co.th> wrote:
>

 

 

 

> Dear community
>

 

 

 

> One of my client is using EE, for some valid reason, they have used more
> users than the bought license being registered in the system (now they are
> sorting out how to resolve this with Odoo SA).
>

 

 

 

> As nowadays, Odoo SA have mechanism to ping every server and set database
> expire in the server which will show on the screen (which is not yet
> critical).
>

 

 

 

> Technically, what will happen after passing the expiry date? Will Odoo force
> shutdown the server or something. Anyone have such experiences?
>

 

 

 

> >From system point, it is a critical system and can't be shutdown.
>

 

 

 

> Thank you very mcuh,
>

 

 

 

> --
> Mobile: +66-(0)8-1841-7480
> Your ERP Partner => www.ecosoft.co.th
>

 

 

 

> _______________________________________________
> Mailing-List: https://www.odoo.com/groups/community-59
> Post to: mailto:community@mail.odoo.com
> Unsubscribe: https://www.odoo.com/groups?unsubscribe
>

 

 

 

>

 

 

 

> _______________________________________________
> Mailing-List: https://www.odoo.com/groups/community-59
> Post to: mailto:community@mail.odoo.com
> Unsubscribe: https://www.odoo.com/groups?unsubscribe

 

 

 

-- 
Dominique Chabord - SISalp
Logiciel libre pour l'entreprise Tryton et open-source Odoo, OpenERP
18 avenue Beauregard 74960 Cran Gevrier
145A rue Alexandre Borrely 83000 Toulon
tel(repondeur) +33(0)950274960 fax +33(0)955274960 mob +33(0)622616438
http://sisalp.fr
http://openerp-online.fr
https://twitter.com/SISalp l'actualité de vos services en temps réel.

_______________________________________________

_______________________________________________
Mailing-List:
https://www.odoo.com/groups/community-59
Post to:
mailto:community@mail.odoo.com
Unsubscribe:
https://www.odoo.com/groups?unsubscribe

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

 

-- 

 

Sforzi Stefano
Tel (CH): +41 91 210 23 40
Tel (IT): +39 011 198 25481
http://www.agilebg.com 

_______________________________________________
Mailing-List:
https://www.odoo.com/groups/community-59

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

-- 

 

Sforzi Stefano
Tel (CH): +41 91 210 23 40
Tel (IT): +39 011 198 25481
http://www.agilebg.com 

_______________________________________________
Mailing-List:
https://www.odoo.com/groups/community-59

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

--

Eric  Caudal (from my mobile)

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe