Mautic 5
-
OK, so we decided to publish a new package altogether for Mautic 5 without LDAP. Thing is we are not mautic developers and the upstream mautic ldap plugin has not seen any development for over 4 years. We tried to keep it developed for Mautic 4, but with Mautic 5 there is much more work with the move to Simfony 5 with Twig templates.
Now, before I investigate any further, have you made any other changes in Cloudron that would prevent Mautic 4.4.10 to work back correctly on Cloudron?
Because of the catastrophe caused by the update to version 5 letting us without this critical app functioning, I had to quickly turn around to reestablish it and so I've restored to the last back up made before the update, but now despite the app seems to work correctly it's become totally impossible to access the CONFIGURATION section its NOT loading at all. All other Settings are accessible but the configuration section.
And just to better help there is not a sign of whatever going wrong from the log file. Any clue?
-
I migrated a test install from 4.4.10 to the new version provided here.
There where no immediate issues, but this was an almost empty instance. Only the setting "composer based install" (it is, right?) is disabled, which should be enabled I guess. However - installation from marketplace still doesn't work as in Version 4 of Mautic in cloudron.Also important to know - there is an upgrade to 4.4.11 for people, who want or need to stay with version 4 for a while. This fixes some required upgrades for expected February mail settings (search for Google / Yahoo requirements).
Is there a way to upgrade to 4.4.11 instead of Release 5 as of now?
-
-
@micmc Do you see any errors in the logs when configuration section is clicked? Or in the browser? When you revert to 4.4.10 via your backup, it should definitely have worked. We haven't made any changes to the old package.
All fixed now! Thanks.
Weirdly enough the problem was not even related to Mautic, you know Murphy's law right, so I had to play with some DNSs changes also, while I was recovering to the previous version, and discovered the fact that, when we try to get into the Configuration module, Mautic tries to ping your SMTP server and WAITS 'TIL GOES THROUGH before providing you access to the configuration module. It was just running that ping to no end to finally timing out, while trying to reach the SMTP connection. And then, DNS finally resolved but isn't that strange?
-
Is there a way to upgrade to 4.4.11 instead of Release 5 as of now?
Yes, I have pushed a new package for this now. You have to check for updates again to get this update on top of 4.4.11 . Settings -> check for updates
Only, unless I'm missing something, when trying to update all that is offered is version 5 ?
-
With the Mautic 5 upgrade, has anyone had any issues installing the symfony/amazon-mailer? Since some of the installation in cloudron is read only, it's unable to write the files necessary.
Where should I run the composer command to install this package so I can re setup my AWS SES being sent from Mautic?
EDIT:
Found this update where the mautic cloudron package auto installs this by default https://forum.cloudron.io/post/82820Still getting this error when trying to use ses+smtp
Unable to send emails via "ses" as the bridge is not installed; try running "composer require symfony/amazon-mailer". -
-
@girish
Someone on the mautic forums mentioned that clearing cache in var/cache
https://forum.mautic.org/t/mautic-5-and-amazon-ses-integration-error/30455This tutorial mentioned setting some permissions after the install (not sure if that's relevant).
https://joeykeller.com/mautic-5-composer-install-simplified/#:~:text=Part Four%3A Add your email transportI have also tried both of these but Mautic seems to think the package isn't even install or accessable due to that error message I shared previously.
Not really sure honestly if this is a Mautic issue or a Cloudron issue. Maybe it's permissions related? I'm not very knowledgable with this, sorry.
-
Hi @girish
Just checking in to see if you had discovered any obvious things when checking?
Something that came up in my research is the installation needs to occur at docroot. Right outside the vendor folder. Not sure if this is relevant or not.Thanks!