1379 Results for the search: ""
Comments 116
Great job @predrag_vukovic @kaviyaa @escopecz - looking forward to seeing the UX work progress in the next sprint!
Great job @predrag_vukovic @kaviyaa @escopecz - looking forward to seeing the UX work progress in the next sprint!
.
.
@ravi_2002 you seem to have disregarded the template which must be used for all feature requests. I have proposed an amendment which restores the template, please fill out the missing parts. Thanks!
@ravi_2002 you seem to have disregarded the template which must be used for all feature requests. I have proposed an amendment which restores the template, please fill out the missing parts. Thanks!
OK thanks - I'll see if we can find a developer to work with you on this!
OK thanks - I'll see if we can find a developer to work with you on this!
Well, I am programming PHP but I have absolutely no experience with Symphony and the Mautic infrastructure. At the moment I can assist and I think the mapping of the existing country and Region definitions with the new standard will be the most involving part of the project. I think I can contribute with this part if you have somebody else who can give me assistance with the coding.
Well, I am programming PHP but I have absolutely no experience with Symphony and the Mautic infrastructure. At the moment I can assist and I think the mapping of the existing country and Region definitions with the new standard will be the most involving part of the project. I think I can contribute with this part if you have somebody else who can give me assistance with the coding.
Begini cara pengajuan Restrukturisasi di spinjam shopee, langkah pertama yang harus kamu lakukan menghubungi pihak shopee Via Chat (082164514143) jelaskan bahwa kamu ingin melakukan restrukturisasi, ikuti proses verifikasi yang di instruksi customer service dan juga siapkan data diri seperti KTP.
Begini cara pengajuan Restrukturisasi di spinjam shopee, langkah pertama yang harus kamu lakukan menghubungi pihak shopee Via Chat (082164514143) jelaskan bahwa kamu ingin melakukan restrukturisasi, ikuti proses verifikasi yang di instruksi customer service dan juga siapkan data diri seperti KTP.
Great initiative and a well-organized kickoff meeting. I really like the focus on clearly explaining what Mautic is and who it’s for, especially with a mobile-first and persona-driven approach. Using WordPress for faster collaboration is a smart decision, and the shared wireframes look like a solid starting point.
I’m personally interested in practical, user-focused web tools that simplify complex functionality—similar to TI-84 Calculator Online (https://ti84calculatoronline.org/
) which makes advanced calculations easily accessible via the web. Looking forward to the next steps and sharing feedback on the wireframes.
Great initiative and a well-organized kickoff meeting. I really like the focus on clearly explaining what Mautic is and who it’s for, especially with a mobile-first and persona-driven approach. Using WordPress for faster collaboration is a smart decision, and the shared wireframes look like a solid starting point.
I’m personally interested in practical, user-focused web tools that simplify complex functionality—similar to TI-84 Calculator Online (https://ti84calculatoronline.org/
) which makes advanced calculations easily accessible via the web. Looking forward to the next steps and sharing feedback on the wireframes.
@mneumann are you able to make the PR for this feature? It was discussed today in the release planning meeting and we'd like to stage it for the 8.0 alpha.
@mneumann are you able to make the PR for this feature? It was discussed today in the release planning meeting and we'd like to stage it for the 8.0 alpha.
Questions from the release planning call:
This sounds great, but what would the benefit be over and above doing a campaign where things like waiting for a user to click a link are already built in, and the campaign library makes it much smoother to implement?
Also, relying on the click in the email could yield false-positives - what's the suggestion for working around this?
Questions from the release planning call:
This sounds great, but what would the benefit be over and above doing a campaign where things like waiting for a user to click a link are already built in, and the campaign library makes it much smoother to implement?
Also, relying on the click in the email could yield false-positives - what's the suggestion for working around this?
This project is now completed and shipped in Mautic 7! Thanks to everyone for their great work and collaboration on this project!
This project is now completed and shipped in Mautic 7! Thanks to everyone for their great work and collaboration on this project!
Hi folks, we've written up a full project spec here: https://docs.google.com/document/d/16v21gcRm_9rvkfPtsXsMeyXxObCa4TqWA5928hYoRVw/edit?usp=sharing - the next step is to find funding for the project. I am currently working on this with a view that we'd get this into Mautic 8 or a minor release of 8.
Hi folks, we've written up a full project spec here: https://docs.google.com/document/d/16v21gcRm_9rvkfPtsXsMeyXxObCa4TqWA5928hYoRVw/edit?usp=sharing - the next step is to find funding for the project. I am currently working on this with a view that we'd get this into Mautic 8 or a minor release of 8.
hmm... I was specifically asking about the POSTGRESQL version to test it so long, as I did not believe the general forum would've answered that, but will ask now in the general forum
hmm... I was specifically asking about the POSTGRESQL version to test it so long, as I did not believe the general forum would've answered that, but will ask now in the general forum
Beside the strongly worded notes to developers we can probably add extra plugin scan for raw/hand-writen MySQL specific queries. Simlply trigger warning during plugin installation. This scan check don't have to be perfect. It just have to remind user that there may be compatibility issue and may need developer assistance.
Beside the strongly worded notes to developers we can probably add extra plugin scan for raw/hand-writen MySQL specific queries. Simlply trigger warning during plugin installation. This scan check don't have to be perfect. It just have to remind user that there may be compatibility issue and may need developer assistance.
OK so it sounds like this _could_ go into a minor release, with strongly worded notes to developers in the Release Candidate stage of the release, and the release notes, about the need to validate any database-related queries.
OK so it sounds like this _could_ go into a minor release, with strongly worded notes to developers in the Release Candidate stage of the release, and the release notes, about the need to validate any database-related queries.
Please ask these questions at https://forum.mautic.org rather than here, @hvisage , this is for discussing the proposal at hand rather than general questions about Mautic. Thanks!
Please ask these questions at https://forum.mautic.org rather than here, @hvisage , this is for discussing the proposal at hand rather than general questions about Mautic. Thanks!
You can find the expected release dates here: http://mautic.org/releases but the basics are:
7.0 expected Jan 26 (had to bump it back a month due to newly released Symfony 7.4 changes breaking our existing Release Candidate release)
7.1 expected Q1 2026, projected Release Candidate on 22/02/2026 and General Availability on 29/03/2026
These are the expected dates for releases, sometimes things don't go to plan and we end up bumping a release, so hold them a little lightly!
You can find the expected release dates here: http://mautic.org/releases but the basics are:
7.1 expected Q1 2026, projected Release Candidate on 22/02/2026 and General Availability on 29/03/2026
These are the expected dates for releases, sometimes things don't go to plan and we end up bumping a release, so hold them a little lightly!
There may be very limited impact on 3rd-party plugins with:
1. Raw/hand-written MySQL-specific queries that use functions we didn't polyfill yet.
2. Direct use of MySQL-only commands (e.g. Leuchtfeuer Housekeeping plugin - OPTIMIZE table needs a one-line VACUUM/ANALYZE equivalent).
3. Loose boolean <-> integer comparisons that are not yet covered by the extra operators we created.
Additionally PostgreSQL enforces the SQL standard (ONLY_FULL_GROUP_BY).
I already added an automatic fix in ReportBuilder that detects missing non-aggregated columns and adds them to the GROUP BY clause.
There may be very limited impact on 3rd-party plugins with:
1. Raw/hand-written MySQL-specific queries that use functions we didn't polyfill yet.
2. Direct use of MySQL-only commands (e.g. Leuchtfeuer Housekeeping plugin - OPTIMIZE table needs a one-line VACUUM/ANALYZE equivalent).
3. Loose boolean <-> integer comparisons that are not yet covered by the extra operators we created.
Additionally PostgreSQL enforces the SQL standard (ONLY_FULL_GROUP_BY).
I already added an automatic fix in ReportBuilder that detects missing non-aggregated columns and adds them to the GROUP BY clause.
What installation method should I use?
Also, what extra packages/etc. do I need to install for Debian?
What installation method should I use?
Also, what extra packages/etc. do I need to install for Debian?
Seeing as a new user I'm looking for PostgreSQL support (given I'm a PostgreSQL only shop at present) when would an official 7.1 be released?
🤔
Seeing as a new user I'm looking for PostgreSQL support (given I'm a PostgreSQL only shop at present) when would an official 7.1 be released?
🤔
@escopecz would this be something we could consider for the 7.1 release? I think we're now too late to get it into 7.0 but given it's a feature it'd need to be in a minor release. From the sounds of it we don't have any BC changes being introduced?
@escopecz would this be something we could consider for the 7.1 release? I think we're now too late to get it into 7.0 but given it's a feature it'd need to be in a minor release. From the sounds of it we don't have any BC changes being introduced?
I like it. Smart solution to go with the polyfill functions. Here is the commit link for lazy people like myself:
https://github.com/wieslawgolec/mautic/commit/924eb50c14e0ea0d657819d45e7e56aa5118430b
I like it. Smart solution to go with the polyfill functions. Here is the commit link for lazy people like myself:
https://github.com/wieslawgolec/mautic/commit/924eb50c14e0ea0d657819d45e7e56aa5118430b
A genius solution for marketers. Can't wait to see in core.
A genius solution for marketers. Can't wait to see in core.
@mzagmajster I've bumped this forward to 8.0 further to our conversations in London but if it's not going to be a BC break once all the coding is done, we can consider it for a minor in the 7.x series.
@mzagmajster I've bumped this forward to 8.0 further to our conversations in London but if it's not going to be a BC break once all the coding is done, we can consider it for a minor in the 7.x series.
Outstanding features which we could consider for future releases:
Field Group Bundle - had a small amount of work left to be done, wouldn't make 7 but might be eligible for a minor release if not 8.0: https://community.mautic.org/processes/roadmap/f/43/results/12
Campaign Library/Theme library / Plugin Marketplace - pitching for Mautic 8.0 but some work might be merged sooner depending on when it's ready and what is B/C breaking.
Specify different email transports for use in different settings - highly requested feature, we recently merged a PR to implement the ability to specify multiple DSNs. Might need to consider the implications (e.g. spammers) https://forum.mautic.org/t/ability-to-specify-different-email-gateways-to-use-for-different-purposes/10620/12.
Part two - exporting tags, now that we can import we should also enable exporting: https://forum.mautic.org/t/include-contact-stage-and-tags-in-imports-and-exports/10262/19
AI initiative - what, when, by whom
Discussion on implementing email expiration date: https://www.zerocarbon.email/ (see also https://badsender.notion.site/Feature-Request-Manage-Email-Expiration-Dates-in-OpenSource-Email-Clients-139dd12c64084147bf21c105fa7af9b7?pvs=4) on Slack, seems a lot of interest, thread here: https://mautic.slack.com/archives/C02GEN0SQ/p1760024624457189. We would need to be clear on the wording for this to avoid confusing with our active/inactive terminology etc but I think it would be a fairly small lift and a useful thing to consider implementing.
Outstanding features which we could consider for future releases:
Field Group Bundle - had a small amount of work left to be done, wouldn't make 7 but might be eligible for a minor release if not 8.0: https://community.mautic.org/processes/roadmap/f/43/results/12
Campaign Library/Theme library / Plugin Marketplace - pitching for Mautic 8.0 but some work might be merged sooner depending on when it's ready and what is B/C breaking.
Specify different email transports for use in different settings - highly requested feature, we recently merged a PR to implement the ability to specify multiple DSNs. Might need to consider the implications (e.g. spammers) https://forum.mautic.org/t/ability-to-specify-different-email-gateways-to-use-for-different-purposes/10620/12.
Part two - exporting tags, now that we can import we should also enable exporting: https://forum.mautic.org/t/include-contact-stage-and-tags-in-imports-and-exports/10262/19
AI initiative - what, when, by whom
Discussion on implementing email expiration date: https://www.zerocarbon.email/ (see also https://badsender.notion.site/Feature-Request-Manage-Email-Expiration-Dates-in-OpenSource-Email-Clients-139dd12c64084147bf21c105fa7af9b7?pvs=4) on Slack, seems a lot of interest, thread here: https://mautic.slack.com/archives/C02GEN0SQ/p1760024624457189. We would need to be clear on the wording for this to avoid confusing with our active/inactive terminology etc but I think it would be a fairly small lift and a useful thing to consider implementing.
Hi @mzagmajster I wondered if there was any progress on this project, it seems we've missed the boat for the 7.0 release so I wondered if this is still on the cards, and if so, whether we should push it forward to 8.0 as I think it's going to be a breaking change, no?
Hi @mzagmajster I wondered if there was any progress on this project, it seems we've missed the boat for the 7.0 release so I wondered if this is still on the cards, and if so, whether we should push it forward to 8.0 as I think it's going to be a breaking change, no?
Results per page:
Share