EGroupware docker 20.1

IT07 2021-04-01 08:57:15 UTC #1

Hi,

I have installed EGroupware 20.1 with docker installer in Ubuntu 18.04, but I have some problems:

After restart, changes done in docker are not saved, how can i save them in docker image without loosing any information?
date.timezone in php.info is not changed, i have changed all php.ini files, but as i read in you posts i have to change it in EGroupware db.

Please i need a lot your help.

Thank you

StefanU 2021-04-01 10:39:04 UTC #2

Hi IT07.

Why did you change anything in the docker container?
Docker containers are not meant to change anything in them. This will be gone with the next update at the latest.

Why do you want to do that? What is wrong?

Is your default timezone wrong?:

/Admin/Admin/PHP-Informationen

grafik

Stefan

IT07 2021-04-01 10:48:01 UTC #3

It is utc and I want to change it to gmt+2

RalfBecker 2021-04-01 10:50:46 UTC #4

You should change the timezone in your users or the default preferences, no need to change the timezone of the container itself!

Ralf

IT07 2021-04-01 11:04:57 UTC #5

I have changed it, but when new ticket is created in tracker “Created on” time sent by email is not correct.

If created time of ticket in EGroupware system is Created on 2020/12/15 10:02, in the email notification is shown as Created on 2020/12/15 11:02.
This time is not correct ‘tr_created’ => $this->datetime($data[‘tr_created’])
also:
‘tr_startdate’ => $this->datetime($data[‘tr_startdate’]),
‘tr_duedate’ => $this->datetime($data[‘tr_duedate’]),
and the comments time.
I want that the time of default preferences to be the same with email notifications in all of their fields where time is displayed, because for Ticket modified by User, Admin at 2021/04/01 12:27 the time is displayed correct.
Europe/Berlin and /Europe/Rome is ok for me.
Please give me any advice, because it is very important for me.

IT07 2021-04-02 12:39:42 UTC #6

@StefanU and @RalfBecker sorry for disturbing you.
Please do you have any suggestions for my case?

RalfBecker 2021-04-02 16:42:27 UTC #7

It could be a bug, thought you need to document is better for us to understand, reproduce and then fix it.

You have a containerized system with MariaDB running in a container and PHP using UTC as default timezone?

What user-timezone have the sending and receiving user set in their preferences?

All times, but the modified time, are wrong by how many hours?

Ralf

IT07 2021-04-06 07:54:33 UTC #8

You have a containerized system with MariaDB running in a container and PHP using UTC as default timezone?
Your MySQL connection id is 3889
Server version: 5.5.5-10.4.18-MariaDB-1:10.4.18+maria~focal mariadb.org binary distribution
mysql> show variables like ‘%time_zone%’;
±-----------------±-------+
| Variable_name | Value |
±-----------------±-------+
| system_time_zone | UTC |
| time_zone | SYSTEM |

What user-timezone have the sending and receiving user set in their preferences?
Europe/Berlin

All times, but the modified time, are wrong by how many hours?
If real created time is Created on 2020/12/15 10:02, in email notification is show as Created on 2020/12/15 11:02
One hour in advance.

In the system Created on is correct, this happens only in email notifications.

Thank you very much,

Amarilda

RalfBecker 2021-04-06 08:42:41 UTC #9

@bbegw That seems to be an other of this timezone errors, which we have not yet fixed. Can you open a ticket with the information from here please.

Ralf

bbegw 2021-04-06 09:30:58 UTC #10

Ticket created and delegated to Nathan for fixing

IT07 2021-04-07 12:29:04 UTC #11

Please can you inform me if this bug will be fixed?
Thank you

bbegw 2021-04-07 13:15:28 UTC #12

sure, i let you know when its fixed

IT07 2021-04-08 11:38:30 UTC #13

@bbegw and @RalfBecker

Today ticket

Ticket created on 2021/04/08 13:00 and reported with email notification as Created on 2021/04/08 15:00

Before the change of time from GMT+1 to GMT+2 for our country, the difference was 1 hour, now in email notification the time of Created on is 2 hours in advance.

Thank you

IT07 2021-04-14 21:17:29 UTC #14

Please, do you have any update?

bbegw 2021-04-15 08:07:48 UTC #15

sorry not fixed yet

IT07 2021-05-05 07:07:37 UTC #16

The problem still persist.
Tracking ticket opened 2021/05/04 16:11
and in email displayed Created on 2021/05/04 18:11
Please do you have any update?

bbegw 2021-05-05 12:48:10 UTC #17

still not fixed, but i wrote Nathan and set a higher priority.

Birgit

ngegw 2021-05-13 21:16:02 UTC #18

Currently in progress

ngegw 2021-05-21 16:46:42 UTC #19

Fixed & backported.
Should be in the next package.

RalfBecker 2021-05-21 17:30:41 UTC #20

There is currently no new 20.1 package planned, thought you can change the tag 20.1 to 21.1. and update to the new 21.1 release containing the fix:

cd /etc/egroupware-docker
sed 's/:20.1/:21.1/g' -i docker-compose.override.yml
docker-compose up -d

The container you get is (most likely) identical to the final 21.1 released on Tuesday.

Ralf