1071 Results for the search: ""

Mautic still haven't healed from the last renaming. Segments used to be called Lists, contacts used to be called leads. So it's very confusing in the code where some code is using the old terms and the new code is using the new terms. The biggest problem is on the database level as changing names of tables and columns is very time consuming and such migration would be done when Mautic is offline as the tables will be locked for hours or days.

Another issue is with APIs and webhooks. If there are services connected to Mautic via APIs or webhooks and we change one keyword to another then all those services must be changed to use the new keyword. So every renaming is very costly and will cause confusing many years in the future, perhaps during the whole lifetime of the project.

The plugins in the Plugins page are installed plugins. Most of them are core plugins. The product team is trying to remove the core plugins from the core as the usage is minimal and the maintenance cost for the core team is high. We've tried that for Mautic 4 but it was reverted as we wanted to firstly prepare the easy way to install plugins. That's where the marketplace came to be. It's still very immature as no company hosting Mautic really wants it. They install plugins differently and some do not support plugins at all. All companies also see it as a security risk to let users install 3rd party plugins. I want to say that the development of the marketplace is slow but there is some new movement with the GSoC students.

About the naming, the marketplace started to use Composer which is the standard tool to install dependencies in the PHP world. It has open repository of packages. So now we have the packages keyword in the marketplace. A package can be either plugin or a theme.

Then there are special kind of plugins called integrations. Those extend special integration interface that enables plugins to easily implement authentication to another system and even custom field mapping configuration. Perhaps that's what you call External Services? Can we call it integrations? But those are still plugins. In other words, integrations are subset of plugins. Plugins and themes are subset of packages.

Well, it's certainly useful!

It would be awesome if we could use some of the information retrieval features to make other actions related to cron jobs visible for users.
Having the backend ready, we can work to bring related UI improvements

Looking forward to joining in-person!

My suggestion: Beyond Expectations, Beyond Limits.
Apple Style 😂

I am in favor and support the new interface uplift or design. I could help if one of those framework like Bootstrap, Zurb Foundation, or Tailwind CSS (Just started learning this one) is used for redesign / facelift.

We have multiple clients (especially when talking to the actual users/marketers) asking for this feature during presales.

I missed this 😩 I will be present for the next meeting

I wholeheartedly support the proposal for a new and improved Mautic interface. This initiative carries immense potential for the platform's growth and success.

Investing in a new Mautic interface is not just about aesthetics; it's about enhancing user satisfaction, community involvement, accessibility, competitiveness, and long-term sustainability. It's a step towards a brighter and more prosperous future for Mautic and its community.

Within the changes I'm proposing and the path to achieve them, there won't be a need for full-time efforts to make it happen. It's possible to achieve significant and amazing results within the existing framework.

I've taken the lead on the project to drive this change, requiring minimal developer attention, so we can make the new interface a short-term reality.

Love it! I'd suggest to add the bounty amount into a comment so multiple people could add bounties to the same issue. But this is already way better than nothing!

Firstly, a huge thanks to everyone who has put a lot of effort into this proposal already, it's clearly been well researched and has been thought through from a lot of angles. Huge kudos to you all for taking this deep dive and identifying where Mautic needs to improve!

I think this would make a really great Community Initiative, especially seeing as you have already got several people who want to work on it and a clear scope as to what needs to be achieved.

Something to bear in mind is that not everybody is privacy-minded, so while I absolutely agree it would be awesome for Mautic to be the gold standard in that regard, there are a lot of folks who do want / need to collect some information that folks in Europe may not. So we should be mindful of that as we move forward with this, to not 'throw the baby out with the bathwater' and communicate clearly the impact of changes being made.

Mautic still needs to remain functional for the marketer, at the end of the day!

Firstly, a huge thanks to everyone who has put a lot of effort into this proposal already, it's clearly been well researched and has been thought through from a lot of angles. Huge kudos to you all for taking this deep dive and identifying where Mautic needs to improve!

I think this would make a really great Community Initiative, especially seeing as you have already got several people who want to work on it and a clear scope as to what needs to be achieved.

Something to bear in mind is that not everybody is privacy-minded, so while I absolutely agree it would be awesome for Mautic to be the gold standard in that regard, there are a lot of folks who do want / need to collect some information that folks in Europe may not. So we should be mindful of that as we move forward with this, to not 'throw the baby out with the bathwater' and communicate clearly the impact of changes being made.

Mautic still needs to remain functional for the marketer, at the end of the day!

What does it mean to endorse?

Solo falta 1 día para poder conocernos cara a cara. No te lo pierdas

Totally get your viewpoint here, but to be clear this is not something we'd be making from scratch - it's already been created by a business because they needed greater oversight of their cron jobs and where they were failing, and they wanted to contribute it to Mautic. So it's not taking any time that would be otherwise directed elsewhere, other than for the code review and testing.

From my perspective, if cron jobs are setup correctly the first place, no application user should be interested or bothered by this anymore. We created a little "cron boost plugin", which allowed to trigger cron jobs from the backend, which is handy when working on campaigns and testing them.

But watching cron jobs run via the UI?

There are other shortcomings that have real impact at the acceptance of Mautic in organizations: data privacy features (currently Mautic can't yet be used in full compliance with the law without hacks) and also multilingual support (emails are well supported, while e.g. forms are not) is not finished yet.

Sorry.

I wanted to use the feature to offer money for boring work last week. I would not have done it knowing the fifth goes to someone else.

We did talk about that in the call with the Product Team but I think it was felt that it would be a little complex for the first phase of the project - we did suggest that displaying the correct paths to the cron jobs would be really helpful as well, so that people could go there to copy the correct commands etc.

This is a good initiative.
I'd like to ask if there will be the possibility of creating cron from the dashboard also.

Something to also consider, although it's a large project, is something we've been talking about: decoupling the user interface from the application all together (eg having it in React or Angular or some such).

I don't think we're really in a position to do this fully at this time, but I just wanted to flag we'd been talking about it for some time as part of the next generation discussions, and it could be a long term goal that was worked towards. It has a bunch of hefty dependencies - like beefing up our API so we have full coverage, etc. - so it's not for the faint hearted! But just wanted to ensure folks were aware that this was something on the long-term radar.