dynamicweb / DynamicWeb

Make feature requests for Dynamicweb in Issues section of this repository
https://doc.dynamicweb.dev/documentation/fundamentals/support/feature-requests.html
GNU General Public License v3.0
1 stars 0 forks source link

Keep front end alive (don't kill the license) when entering licence configuration screen #145

Open ivaigor96 opened 2 weeks ago

ivaigor96 commented 2 weeks ago

Currently if we want to change the license on a live site, the only way to do it is outside working hours, because the solution will redirect the front end to the license configuration screen until the license file is created. This is no good in scenarios where a live solution requires change of license. This could happen for example when a partner changes or when the physical path of the solution changes like we have now and we need to install a new license since it's running on trial.

It's ok if /admin redirects to the license configuration screen, but the front end should either show some sort of other placeholder page like "under maintanace" or something similar or just be available.

Additionally, maybe there should be a warning message when changing license that the site becomes inaccessible ? Because most people will not realize this and make the mistake.

nicped commented 2 weeks ago

I think we could remove the license check from the frontend middleware - I think it was made like this because too many sites runs with no license :-). But I understand this issue.

ivaigor96 commented 2 weeks ago

I think we could remove the license check from the frontend middleware - I think it was made like this because too many sites runs with no license :-). But I understand this issue.

I hope that you can find a solution where you can still control people running a solution without a license and allow entering a license configuration screen without killing the front end. In my mind there should be an explicit difference between a license configuration process being initiated manually by a user and a license actually being missing or expiring. This could be that if a license file (E.g. a trial license file, already existed before entering the screen - then the front end should still stay alive at least VS a license not existing at all or expiring / invalidating). We could then at least solve some of the cases.

I am looking forward to seeing how this is solved in the future