Hi @ahmed.maxamed,
I solved this problem as follows, before starting the update I made this select:
select email_id, email_key, assoc_id from email_templates order by email_id asc;
So, with the result, I put it in excel and for each row of the result in this table, I edited it to update it during the installation process.
For example, in the first and second lines row:
'1', 'COPYEDIT_ACK', '7'
'2', 'COPYEDIT_ACK','9'
I updated it like this:
UPDATE email_templates_data SET email_id = 1 WHERE email_templates_data.email_key = 'COPYEDIT_ACK' AND email_templates_data.assoc_id = 7; COMMIT;
UPDATE email_templates_data SET email_id = 2 WHERE email_templates_data.email_key = 'COPYEDIT_ACK' AND email_templates_data.assoc_id = 9; COMMIT;
I did this for all the rows in the table.
Right after starting the update, I ran all these lines and this problem was solved.
I did this, because line 34 of the file
ojs-3.2.0-1/dbscripts/xml/upgrade/3.2.0_preupdate_email_templates.xml:
<query driver = "postgres7"> UPDATE email_templates_data SET email_id = email_templates.email_id FROM email_templates WHERE email_templates_data.email_key = email_templates.email_key AND email_templates_data.assoc_type = email_templates.assoc_type AND email_templates_data. email_templates_data.
it didn’t seem to be generating the correct result. Everything was still null, but the information was there.
Detail, in my table all records had the same value in the email_key column, so I ignored this data. Checks if you have more than one value in that column as well.
Hope this helps.
Regards,
Adriano Moreno