It's like they used a time-machine and preemptively fixed this in their main 2 days ago. LOL. Sorry I didn't notice it was so recent.
We can hang tight and wait till the next release!
It's like they used a time-machine and preemptively fixed this in their main 2 days ago. LOL. Sorry I didn't notice it was so recent.
We can hang tight and wait till the next release!
Sorry, it doesn't seem to be picking up the settings, even though they are in custom_settings.yml. I posted a question to stirling github about that. I'm not sure that it merges custom_settings.yml like you'd assume.
https://github.com/Stirling-Tools/Stirling-PDF/discussions/3058
Thanks for the quick attention, but doesn’t look fixed yet.
I updated, but I don’t see those settings written to the settings.yml, and it still says they are missing (looking in default paths)
Is it hard to allow/run an env.sh? Then maybe we can fix the key problem as well by using environmental variables.
Another question I had. How do I get the API key to persist across restarts? When testing it doesn't save. Under Settings -> Account Settings -> Your API Key'
I poked around seeing if there was an environmental variables env.sh script, but there wasn't on. Otherwise I could try export SYSTEM_CUSTOMPATHS_OPERATIONS_WEASYPRINT=/usr/bin/weasyprint
I think these need to be set in the settings.yml. I can't edit it since it get's refreshed on restart.
system:
customPaths:
operations:
weasyprint: "/usr/bin/weasyprint" #Defaults to /opt/venv/bin/weasyprint
unoconvert: "/usr/bin/unoconv" #Defaults to /opt/venv/bin/unoconvert
Here's the log:
Feb 24 13:08:22 18:08:22.650 [main] WARN s.s.SPDF.config.ExternalAppDepConfig - Missing dependency: /opt/venv/bin/weasyprint - Disabling group: Weasyprint (Affected features: Markdown To PDF, Url To PDF, Html To PDF)
Feb 24 13:08:22 18:08:22.656 [main] WARN s.s.SPDF.config.ExternalAppDepConfig - Missing dependency: /opt/venv/bin/unoconvert - Disabling group: Unoconv (Affected features: File To PDF)
Feb 24 13:08:22 18:08:22.857 [main] INFO s.s.S.config.EndpointConfiguration - Total disabled endpoints: 6. Disabled endpoints: book-to-pdf, file-to-pdf, html-to-pdf, markdown-to-pdf, pdf-to-book, url-to-pdf
Hello,
I just went through fixing my install to the latest 9.0.2. In logs it said "Your EspoCRM version (8.4.2) is not supported. Required version: 9.0.1." I finally realized that since my extensions were not compatible with 9.0, the upgrade script never did it's work.
Steps:
Repair -> Enable Recovery Mode
Terminal
, you'll need to first run the following commands:mkdir -p /run/espocrm/cache/application
chmod -R 777 /run/espocrm/cache
chown -R www-data:www-data /run/espocrm/cache
Terminal
, use button to upload new extensions to /app/data, and then upgrade with php command.php extension --file=/app/data/YOUR-EXTENSION.zip
Recovery Mode
. Upgrade script will now completeEnjoy!