Hello Am 20.10.2015 um 17:13 schrieb Aurélien Minet: > On 10/20/2015 03:51 PM, Christian Mack wrote: >> http://www.sogo.nu/bugs/view.php?id=3344 >> >> Solution: >> Upgrade to SOGo 2.3.2, then open the events in this week and store them >> again. > > Hi tanks for the information, > > updating to 2.3.2 is ok (and done) but opening all the events of this > week and save them again for every user isn't :( > sogo-tool can't help ? or an sql update in database ? >
There is no such thing AFAIK.
We solved it by informing the users after upgrade, which had events in
this week.
You can get those with something like this:
---------------
#!/bin/bash
export DB_SERVER=databasehost
export DATABASE=sogo
export DB_USER=sogo
rm calendarTables.txt
rm betroffeneTabellen.txt
echo "select c_location from sogo_folder_info where
c_folder_type='Appointment'\g calendarTables.txt"|psql -d ${DATABASE} -h
${DB_SERVER} -q -t -U ${DB_USER} -w -A
cat calendarTables.txt|while read
do
export DB_TABLE=${REPLY##*/}
export NUMBER=`echo -e "select count(*) from ${DB_TABLE} where
c_content like '%DTSTART%:20151018T%' or c_content like
'%DTSTART%:20151019T%' or c_content like '%DTSTART%:20151020T%' or
c_content like '%DTSTART%:20151021T%' or c_content like
'%DTSTART%:20151022T%' or c_content like '%DTSTART%:20151023T%' or
c_content like '%DTSTART%:20151024T%';"|psql -d ${DATABASE} -h
${DB_SERVER} -q -t -U ${DB_USER} -w -A`
if [ ${NUMBER} -ne 0 ]
then
echo ${DB_TABLE} >>betroffeneTabellen.txt
echo -e "select c_path2 from sogo_folder_info where
c_location like '%${DB_TABLE}';"|psql -d ${DATABASE} -h ${DB_SERVER} -q
-t -U ${DB_USER} -w -A >>popIDBetroffen.txt
fi
done
--------
betroffeneTabellen.txt will contain the users.
But yes, there are always some, who can not read emails :-/
Kind regards,
Christian Mack
--
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
