Upgrade from 1.8.007 - recur_exception column problem

novak 2024-11-06 17:55:54 UTC #1

Hi,

I have made an upgrade from the very old version 1.8.007.
I have followed the instructions from Installation using EGroupware docker RPM DEB package and Running own apps in standard Docker installation.
I have solved some problems using Update recommendations and troubleshooting.

The update ended with a “504 Gateway Time-out” message, but when I go into settings and the main configuration menu, everything has a green check mark except Application Management.

I updated everything possible and installed new apps that required it.
Infologs, Addressbook and Calendar are the most important for us.
Addressbook was marked as OK from the begining.
It required an update of the Infologs and it went well.

Unfortunately, the Calendar update is needed too, and it ends with the following:

AlterColumnSQL('egw_cal_dates','recur_exception',Array ( [type] => bool [default] => [null] => [comment] => date is an exception ) ) sql=Array ( [0] => ALTER TABLE egw_cal_dates ADD recur_exception TINYINT DEFAULT 0 ) 
Duplicate column name 'recur_exception'
api/src/Db.php (861) 
Database error
Invalid SQL: SELECT egw_cal_repeats.cal_id AS cal_id,egw_cal_repeats.recur_exception AS recur_exception,MIN(cal_start) AS cal_start,MIN(cal_end) AS cal_end FROM egw_cal_repeats JOIN egw_cal_dates ON egw_cal_repeats.cal_id=egw_cal_dates.cal_id WHERE egw_cal_repeats.recur_exception IS NOT NULL GROUP BY egw_cal_repeats.cal_id,egw_cal_repeats.recur_exception
Unknown column 'egw_cal_repeats.recur_exception' in 'field list' (1054) (1054)

Could you help?

What about all the other applications signed as “deleted”? We used only eTemplates, all the others no. Should I uninstall them only?
What about the message “504 Gateway Time-out” at the and of the update. Where should I look for more info (some log file? which one?).

RalfBecker 2024-11-06 18:17:27 UTC #2

Probably, thought it’s tough through the forum.

My suggestion would be to buy some support budget, and I do the update for you. Price depends it bit on the amount of data and which apps. Typically it’s done in 1-3 hours.

Yes, all but phpbrain/KnowledgeBase no longer exist and you can either delete or keep them. It does not matter either way.

Probably just means that it took to long. I would not worry about it, as long as setup shows the application updated.

Ralf

novak 2024-11-07 06:58:55 UTC #3

Thank you Ralf,

I will have to make some changes to new version of EGroupeware. We have same eTemplates customized in the old version 1.8.007 and changed some functionality. So first I have to customize EGroupware to be usable for us and than I will pay some support, to transfer the data.

Is there any tutorial or info how to transform old eTemplates to ETemplate2?
Or how to use eTemplate in new version (in docker)?

Thanks

RalfBecker 2024-11-07 09:49:00 UTC #4

There is an example app showing how to use eTemplate2: https://github.com/EGroupware/example/

In general you only have to use the new Api\Etemplate class, instead of the old etemplate one.
It get’s more complicated if you used JavaScript with you eTemplate app …

There is nothing special in term of eTemplate, if you use Docker.

Ralf

novak 2024-11-07 15:12:02 UTC #5

Thank you Ralf,

but there was an eTemplate application in the old EGroupware.
Now I do not see any possibility to edit the eTtemplates…

Where should I look?

And where are the files of the whole EGroupware? I have to find eTemplate file for an app (for example if I want to change the look of infologs row in the list - /usr/share/egroupware/infolog/templates/default/index.xet) and change it, or make a copy and rename it? It was quite obvious in the old version of EGw, now I am little bit confused
Should I directly log into the container?
What if I make an update of EGw in the future, will my eTemplates survive the upgrade?

Pavel

RalfBecker 2024-11-08 07:11:17 UTC #6

The eTemplate files are now in the filesystem under $app/templates/default, like when you exported them in 1.8. If you have not exported the templates of your app, you need to do so BEFORE migrating.

The template will be in the old, pre-web-component format, which get transformed on the fly by api/etemplate.php, which you can (and should!) also use as cli-program to transform your eTemplates to the new syntaxt (et2-prefix and different attribute names).

As an editor you can use every XML editor and use our DTD to get them syntax checked and a help on possible attribute-names.

There is also a website describing the new widgets and their attributes, plus links to other resources: https://etemplate.egroupware.org

The where are the templates I already answered.

Remaining question is: how to customize EGroupware’s stock applications like e.g. InfoLog?

There are two ways:

the most easy is with our EPL version, there you can mount a virtual layer over the eTemplate in the container and use EGroupware’s filemanager to update them.
the hard(er) way is to update them in the container by e.g. mounting the changed template over the ones delivered with the container (just placing them in /usr/share/egroupware/$app/templates/default will NOT work!):

Merge e.g. the following into your /etc/egroupware-docker/docker-compose.override.yml:

services:
  egroupware:
    volumes:
    - /usr/share/egroupware/infolog/templates/default/edit.xet:/usr/share/egroupware-sources/infolog/templates/default/edit.xet:ro

Both described ways survive regular EGroupware updates.

Ralf