For both the Quote and Requests for Quotation workflows, after pressing the [Send by Email] button, instead of presenting the mail.compose.message.form Odoo appears to hang, displaying...
Loading...
Still loading...
Still loading...Please be patient.
...etc....
...and eventually it times out, and returns to the same quotation screen.
I don't think it is an Inbound or Outbound email servers problem as both pass connection tests and emails to customers for eCommerce abandoned carts are successfully sent.
If I open a previous email under Settings / Technical / Emails, for example a "You left items in your cart!", and click [Reply] the mail.compose.message.form is displayed and the email is able to be sent and is successfully received.
However there does look to be some kind of permission problem as I can't open up previous "Your Odoo Periodic Digest" emails that failed prior to getting the Inbound or Outbound email servers setup properly.
Odoo 14 was originally installed via the nightly repository as per the below article onto Ubuntu 20.04 LTS (Focal)
https://www.odoo.com/documentation/14.0/administration/install/install.html#repository
A refresh / upgrade of the repository has been performed. Maybe that broke it? i.e...
sudo apt-get update
sudo apt-get upgrade -y
Kind regards,
Anthony
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Księgowość
- Zapasy
- PoS
- Projekt
- MRP
To pytanie dostało ostrzeżenie
A good exercise in problem investigation. The Odoo log file was showing a delay and time out error when trying to complete the PDF creation of the PDF quote. So not an email compose problem at all..
odoo.addons.base.models.ir_actions_report: wkhtmltopdf: b'Exit with code 1 due to network error: TimeoutError\n'
...which lead me to this helpful article...
https://github.com/odoo/docker/issues/238
...and then...
https://www.odoo.com/forum/help-1/how-to-change-the-value-of-web-base-url-to-get-the-correct-header-footer-css-82516
...which resolved the problem.
However, I was thinking why was this needed when my other VM was ok and didn't need it.
After re-checking the network configuration of the VM, there was an incorrect configuration that was corrected, solving the problem!
Cheers,
Anthony
Podoba Ci się ta dyskusja? Dołącz do niej!
Stwórz konto dzisiaj, aby cieszyć się ekskluzywnymi funkcjami i wchodzić w interakcje z naszą wspaniałą społecznością!
Zarejestruj się| Powiązane posty | Odpowiedzi | Widoki | Czynność | |
|---|---|---|---|---|
|
1
gru 25
|
398 | ||
|
3
wrz 25
|
3816 | ||
|
0
sie 25
|
1222 | ||
|
1
sie 25
|
3626 | ||
|
2
lip 25
|
9250 |
My test system, built the same way, and has had the repository refreshed / upgraded and the mail.compose.message.form is displayed for Quote and Request for quotation. The test system does also error when trying to open old failed emails.
I've done a quick compare between all the XML and PY files between the two servers and all Odoo files are the same size and owner etc. The working server is on Hyper-V and the failing server is in Azure based on the focal-server-cloudimg-amd64-azure.vhd.zip file from here...
https://cloud-images.ubuntu.com/focal/current
Not sure what to check next?
It's not a nginx issue, as the problem is still present if I revert back to default 8069 port etc.
The mail.compose.message.form presents fine, on a fresh install of Odoo on a new Azure VM.
How does one perform a re-installation of the Odoo Sales App on a broken system?