Hello,
I’m eagerly awaiting the alpha release of Mautic 7 and I was wondering when its likely to be made public so I can begin testing it on our web platform ?
I know its difficult to give an accurate timescale as its still being developed but I would appreciate an estimate i.e. one month, three months, six months etc… so I can plan ahead.
How can I get involved in the alpha testing phase ?
Thanks.
Hey @andrew_c3 great to hear you’re keen to test!
At the Community Sprint in Prague last week, we merged the last PRs that were needed to bring Symfony 7 and PHP 8.4 support
Mautic: Open Source Marketing Automation Software.
We recommend using DDEV to test locally:
https://mau.tc/tester
We are aiming to make the release for the alpha once we have this PR merged which must go out in the alpha, you can help with that by testing/reviewing it:
Campaign import/export:
7.x ← levente999:campaign-library-CL-34
opened 12:21PM - 27 Jan 25 UTC
| 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? | 🔴
| User documentation | https://github.com/mautic/user-documentation/pull/361
| Developer documentation | https://github.com/mautic/developer-documentation-new/pull/242
## Description
This proof of concept (PoC) implements the Campaign Library feature, focusing on the export and import of a single campaign entity without involving the UI. The goal is to demonstrate the core functionality of exporting and importing campaign data in a streamlined manner.
---
### 📋 Steps to test this PR:
#### 1. **Exporting Campaigns**
Use the following commands to export campaigns:
- Export campaign data in JSON format only:
```bash
ddev exec bin/console mautic:entity:export --entity=campaign --id=1,2,3 --json-only
```
- Export campaign data as a ZIP file:
```bash
ddev exec bin/console mautic:entity:export --entity=campaign --id=1,2,3 --zip-file
```
The output files will be stored in the Docker container's temporary directory (`/tmp`). To access these files on your system, use the following commands to copy them to a local directory:
```bash
docker cp ddev-mautic-web:/tmp/campaign_data.zip ../mautic/campaign_data.zip
```
#### 2. **Importing Campaigns**
To import the exported campaign data, use the following command:
```bash
ddev exec bin/console mautic:entity:import --entity=campaign --file=campaign_data.zip --user=1
```
**Note:** Before running the import command, the required files must be copied to the Docker container's temporary directory. Use the following commands to copy the files into the container:
```bash
docker cp ./campaign_data.zip ddev-mautic-web:/tmp/campaign_data.zip
```
#### 3. **Verification**
- Verify that the campaign data is correctly exported by inspecting the ZIP files in the system directory.
- Ensure that the imported campaign data is successfully reflected in Mautic.
### 🚀 Expected Results:
- Export commands generate the appropriate files in the Docker container's temporary directory.
- Import commands successfully import the exported campaign data into the system.
- No errors are encountered during the export or import process.
### 🚀 Jira Ticket:
https://mautic.atlassian.net/browse/CL-34
Also this one is a breaking change:
7.x ← remove-track_by_tracking_url
opened 08:49PM - 04 May 25 UTC
Remove Identify visitor by tracking url configuration settings usage
| 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
---
### 📋 Steps to test this PR:
Seems like we do not need this option in configuration. From some refactoring, contacts are identified by CT parameter by default with the line: https://github.com/mautic/mautic/pull/14974/files#diff-ff1cf0e25a20c2ebe5f252374318df2cb7aa36bb6c880db1a693f3e2e2e4ec8cL122
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. Just check if tracking works like before
The full milestone is here with other PRs we’d like to get merged. Quite a lot only need one more test.
Once we release the alpha we’ll then have a beta and Release Candidate, the goal is to release General Availability by the end of the quarter.
. You can pull the 7.x branch and test there: