SuiteCRM 7.15 ESR Released

Dear SuiteCRM Community,

We’re excited to announce that SuiteCRM 7.15 has officially landed!

As an Extended Support Release (ESR), this version is built for long-term stability. By extending the life of the 7.x series for at least another two years, SuiteCRM 7.15 provides a dependable foundation and gives you ample time to plan your future roadmap.

What’s new in 7.15?

  • :e_mail: Better Control: Refined email import handling.
  • :spiral_calendar: Seamless Sync: Improved calendar integration.
  • :high_voltage: Modern Foundation: Full support for PHP 8.4.
  • :hammer_and_wrench: And Much More: Improved API security and a revamped text editor.

You can read the full details and download SuiteCRM 7.15 below👇

A huge Thank You to every contributor who submitted code, reported bugs, or shared feedback. You are what makes SuiteCRM stronger with every release! :folded_hands:

3 Likes

New trending GIF tagged whoa awesome whoa awesome… | Trending Gifs


:page_with_curl:Documentation Updates:

New or updated guides are available for:


Error: It does not support .jpg and .jpeg logos.

admin → System Settings → Select Logo

 The file format of the image must be JPEG or PNG. Upload a new file with the file extension .jpg or .png.

Hi,

First of all, thank you to everyone who worked on this new version :left_facing_fist:t2: . It’s great, and the features you delivered are very useful.

That said, I have an observation: in the roadmap for version 7.15, it was mentioned that the Reports module would be worked on. However, I don’t see that reflected in this release. Normally, the release notes include a section listing the bugs and the PRs that address them (which is very useful), but that section is not present in these release notes.

Could you please confirm whether there were no Reports module changes included in 7.15, or if the information simply wasn’t documented in the release notes?

Hi @hipolito,

Thanks for your question and for the kind words about the new features!

To clarify, you won’t see a specific list of bugs addressed in this release as v7.15.0 was focused on new features. However, as with every release, you can view the full technical breakdown of all commits via the GitHub comparison here.

Regarding the Roadmap: I believe you are referring to the planned “Reports Rendering and Performance improvements.” Work on this is still ongoing. Since it wasn’t fully completed to our standards, we opted to hold it back from this specific release to ensure stability, but we intend to release it as soon as it’s ready.

In the meantime, is there something specific you were hoping to see in the Reports module? We would love to hear your thoughts!

If we get features from KReports in SuiteCRM Reports module, it would be great.

  1. KReports for SuiteCRM

PHP

Thank you very much for sharing the GitHub comparison; it’s really helpful to quickly understand what has been integrated into the new version.

I’ve been working as a SuiteCRM developer for a while now, both on v7 and now on v8, and I genuinely like the platform. However, the module that gives me the most trouble is Reports, mainly because I keep running into issues quite often. While reviewing the GitHub repositories for both v7 and v8, I noticed that many of these report-related topics are already logged and still open (as you mentioned, they’re planned for later). For the ones I didn’t see reported, I’ve already added them there.

And yes, regarding the item “Reports rendering and performance improvements”: I initially assumed it referred to work focused on fixing the existing open Reports bugs. I now understand this will likely be addressed in future releases. With that, my question is resolved—thank you very much.

Taking the opportunity (I know this is not directly related to the thread), I have two additional questions:

  1. Is there a plan to migrate to the new frontend the legacy (Detail/Edit) views of the core modules that haven’t been migrated yet? For example: Meetings, Quotes, Invoices, Documents, Notes, etc. I understand it’s a large effort due to the amount of customizations those views usually have, but I’d like to know if there is any plan or roadmap for this.

  2. With the new features in the latest releases, I feel developers have more flexibility to customize views, but there is still a major limitation when something very specific is needed (for example, an experience similar to Quotes/Invoices to add line items inline, like a “function field”). In those cases, what I usually end up doing is switching the view back to legacy to make it possible. However, I’d personally like to keep the SuiteCRM 8 view because the user experience is much better. I feel this is currently one of the biggest limitations for developers on v8. I understand it’s not about replicating the v7 approach, but it would be great to have a supported way to inject a custom Angular component at the field level in these views for advanced customization scenarios.

2 posts were split to a new topic: 7.15 ESR - problem with invoice numbers