Mautic 7.0.1 works on my side

[stefan-franz]

I updatet to from Mautic 6.0.7 to 7.0.1 and on my first view. all is working.
Thank all for their work.

How updated:

How to update Mautic — Mautic Documentation 0.1 documentation

Log in via the command line, and change directory to the Mautic directory using the command:
cd /your/mautic/directory

In my case: cd /var/www/html/mautic/

sudo -u www-data php bin/console mautic:update:find
sudo -u www-data php bin/console mautic:update:apply
sudo -u www-data php bin/console mautic:update:apply --finish

If rights problems:
Files Permission und Ownership:

File ownership and permissions — Mautic Documentation 0.1 documentation

Owner to Apache
sudo chown -R www-data:www-data /var/www/html/mautic

Files set 644
sudo find /var/www/html/mautic -type f -exec chmod 644 {} +

Directory set 755
sudo find /var/www/html/mautic -type d -exec chmod 755 {} +

Some special rights für Apache auf Cache, Logs, Config, Media

sudo chmod -R g+w /var/www/html/mautic/var/cache \
                     /var/www/html/mautic/var/logs \
                     /var/www/html/mautic/app/config \
                     /var/www/html/mautic/media/files \
                     /var/www/html/mautic/media/images \
                     /var/www/html/mautic/translations

Delete Cache:
sudo -u www-data php /var/www/html/mautic/bin/console cache:clear

[rcheesley]

Thanks for letting us know that it all went smoothly - we don’t often get that feedback and it’s nice to hear that everything worked OK!

[stefan-franz]

You’re welcome.

If you want, add my update process into the Mautic manual. At my beginning i hat no knowledge about an own LInux ubuntu server or how to install Mautic. And you know, i had many questions and problems because of some rights problems.
I invested a lot of time and searched through the internet and now i think i have the right knowledge - with the help of ChatGPT (explained me a lot)

I have a plug and play tutorial for:
→ Update Mautic or
→ Fresh install Mautic on Ubuntu 24.04 (Fresh install, Apache, php, Mariadb, lets encrypt, backup and restore Mautic every night with scripts etc…)

The better the instructions and the easier the maintenance of Mautic is and the more documented it is, the more users, the more donations.

If you want, i can send you the installation tutorial of an ubuntu server from the scratch and you can add it also in the manual als “easy plug and play” installation.
Some experts could check it and can add or change something - of course.

[rcheesley]

Hi @stefan-franz, the Mautic docs are editable by anyone. Look at the top of the page and you’ll see ‘edit on GitHub’. This takes you to the file where you can edit, make changes, and then submit a pull request to be considered by the education team for inclusion.

If you have some familiarity with working with Git, then we have more extensive docs here: Mautic’s documentation — Mautic Community Handbook 0.1 documentation.

Looking forward to reviewing your suggestions!

[stefan-franz]

docs/getting_started/how_to_update_mautic.rst

Do i need to make a fork, right?

Do you have an explanation of the formatting? I can only edit in the raw code format? (no wysiwyg editor?)

And after editing - i have to click the “Commit Changes” button - right?

[rcheesley]

@stefan-franz

Do you have an explanation of the formatting? I can only edit in the raw code format? (no wysiwyg editor?)

It’s all outlined in the documentation guidelines I shared, here’s the relevant bit about the formatting:

< - Mautic’s documentation — Mautic Community Handbook 0.1 documentation

When you click to edit using this button:

it’ll ask you to make a fork - that’s a one-time action. Then you can edit in the GitHub user interface. It allows you to live-preview the changes you make using this toggle:

Once you’re done with your changes, press the green button for ‘commit changes’ and then ensure you start a new branch - I normally name it something that’s relevant to the change I am making.

Then click ‘propose changes’.

On the next screen it shows a preview of the changes. Click on ‘compare across forks’ so that you can propose bringing those changes over to mautic’s upstream repository for the user docs (by default, it tries to make the changes to your own fork).

Update the base reporitory to be mautic/user-documentation. It should look like this with mautic/user-documentation on the left (where you’re merging into) and your fork as the head repository on the right (where you’re merging from):

When you click the green ‘create pull request’ button it makes a pull request using the template that we provide:

Please fill out the template, don’t worry about the part re. linked issue.

The team will then help you by reviewing it and suggesting any improvements that might be needed, we call this ‘PR Review’. Often they will provide a suggestion and you can click a button to apply the proposed changes, but if you need to edit a file, you can use the user interface like this:

Then you just commit the changes again and it applies to the PR.

Hope that helps! There’s docs in the link provided earlier on how to do this locally, if you prefer, which means you can build the documentation and check that it works fine, but for a first time using the UI in GitHub is totally fine!

[stefan-franz]

Ok - i’ll work on it the next days.

Last question: Mautic is recommended, to run compose based. I have still the normal installation, coming from my first Mautic 4.4. installation.

Is the best way really, that the user switch to the composer based installation?
If yes, have to switch first myself to composer and i’ll think in this case, it would make sense, only support the composer system.

Can you writer here some explanation pls?

[rcheesley]

We are moving over to composer-by-default indeed, we’ve made the recommendation since it was first introduced back in Mautic 4 I think it was, because things like the marketplace rely on Composer.

Going forward we’ll most likely be removing the zip install option in the future (no sooner than Mautic 8, I shouldn’t think), but we need to have a lot of improvements to our docs and our troubleshooting resources, not to mention helping people to transition from zip to composer. The work we’re doing on the Docker build might well make this much easier for folks if they prefer a containerised installation but our docs just need a lot more love and attention for installing/updating, I think, to make that process much smoother for people.

We do have docs on switching to composer, but it’s by no means high quality or easy to follow for a less technical user. You’d want to replace the 5 here with 7: mautic/recommended-project:^5 for example.

[stefan-franz]

OK - i think it makes sense, to work only on the composer based installation. All other is wasting time.