# Issue with logging in to mautic 6.0 after upgrade from 5.2.5 **URL:** \ **Category:** Mautic 6 Install/Upgrade Support\ **Created:** [May 1, 2025, 12:06pm UTC](https://forum.mautic.org/t/issue-with-logging-in-to-mautic-6-0-after-upgrade-from-5-2-5/35610 "2025-05-01T12:06:25Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\ **Post date:** [May 1, 2025, 1:03pm UTC](https://forum.mautic.org/t/issue-with-logging-in-to-mautic-6-0-after-upgrade-from-5-2-5/35610/3 "2025-05-01T13:03:06Z")
I searched the GitHub PRs for UUID using [this query](https://github.com/mautic/mautic/pulls?q=is%3Apr+UUID+is%3Amerged+sort%3Aupdated-desc) to find when it was introduced: > > > | Q | A > | --------------------------------โ€ฆ------ | --- > | Bug fix? (use the a.b branch) | ๐Ÿ”ด > | New feature/enhancement? (use the a.x branch) | ๐ŸŸข > | Deprecations? | ๐ŸŸข > | BC breaks? (use the c.x branch) | ๐Ÿ”ด > | Automated tests included? | ๐Ÿ”ด > | Related user documentation PR URL | mautic/user-documentation#... > | Related developer documentation PR URL | mautic/developer-documentation-new#... > | Issue(s) addressed | Fixes #... > > > > \## Description > UUID implementation. This is necessary for global identification of entities for the campaign library: > > https://github.com/mautic/mautic/pull/14504 > > The UUID will be used to decide whether an entity should be updated or inserted during the import of entities. > > > > > > > > \--- > \### ๐Ÿ“‹ Steps to test this PR: > 1. Run \`bin/console doctrine:migrations:migrate\` to apply the migration. > 2. You should see in the changed entities/tables like reports, pages, emails and so on that there is new UUID column in the table with filled in hash. There was also a PR to fix some issues: > > > Cf 583: Copy Roles via RC/GT. > > > > | Q | โ€ฆA > | -------------------------------------- | --- > | Bug fix? (use the a.b branch) | โŒ > | New feature/enhancement? (use the a.x branch) | โœ”๏ธ > | Deprecations? | โŒ > | BC breaks? (use the c.x branch) | โŒ > | Automated tests included? | โŒ > | Related user documentation PR URL | mautic/user-documentation#... > | Related developer documentation PR URL | mautic/developer-documentation-new#... > | Issue(s) addressed | Fixes #... > > > > \## Description > > UUID implementation. This is necessary for global identification of entities for the campaign library: > > https://github.com/mautic/mautic/pull/14504 > > The UUID will be used to decide whether an entity should be updated or inserted during the import of entities. > > > > > > > \--- > \### ๐Ÿ“‹ Steps to test this PR: > > > 1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs \[here\](https://contribute.mautic.org/contributing-to-mautic/tester)) > 2. Run bin/console doctrine:migrations:migrate to apply the migration. > 3. You should see in the changed entities/tables in role and permission and so on that there is new UUID column in the table with filled in hash. Both were merged in 6.0.0. In the first PR I found the migration: `app/migrations/Version20210211081531.php` Then there are two migrations in the second one: `app/migrations/Version20210818090322.php` `app/migrations/Version20210819201726.php` If youโ€™ve done an upgrade and the migrations were processed, it should have migrated your database and completed the necessary changes. I alos [searched the issue queue for UUID](https://github.com/mautic/mautic/issues?q=is%3Aissue%20%20UUID%20) and found this issue: [Missing `uuid` field in Lead entity after updating to 6.0.0-rc ยท Issue #14760 ยท mautic/mautic ยท GitHub](https://github.com/mautic/mautic/issues/14760) which was fixed with the later PR: > > > | Q | A > | --------------------------------โ€ฆ------ | --- > | Bug fix? (use the a.b branch) | ๐ŸŸข > | New feature/enhancement? (use the a.x branch) | ๐Ÿ”ด > | Deprecations? | ๐Ÿ”ด > | BC breaks? (use the c.x branch) | ๐Ÿ”ด > | Automated tests included? | ๐ŸŸข > | Related user documentation PR URL | > | Related developer documentation PR URL | > | Issue(s) addressed | > > > > \## Description > > This PR adds permission checks during contact and company imports. > > > > > > > \--- > \### ๐Ÿ“‹ Steps to test this PR: > > 1. Create a role that does not have permissions for editing contacts but has permissions to create contacts. > 2. Login as a user that has the above role assigned to them. > 3. Create a new contact import that contains rows for both inserts and updates. > 4. Wait till the import is \`imported\`. > 5. Any CSV rows containing updates should be ignored. > 6. There should be error messages like \`User '\' has insufficient permissions\` for all the rows containing updates. > 7. Validate that permissions are checked against a user who \*\*last updated a given import\*\*. > 8. Validate the above steps for company imports at \`/s/companies/import/new\`. The company import follows the same \`Contact Permissions\`. There are no separate \`Company Permissions\`. Also released with 6.0.0. --- _[View the full topic](https://forum.mautic.org/t/issue-with-logging-in-to-mautic-6-0-after-upgrade-from-5-2-5/35610)._