The official K2 has been updated. Are there any plans to add anything new here?

[eugenkyiv]

Hello developers. I hope you are safe. I noticed that the official developer of the K2 component has started updating his component. He regularly improves or adds new features to the component. He was asked if he already plans to update it to Joomla 5, and he replied that he still does not plan to. I do not know why he does not want to update. After all, almost all new sites have been using the latest Joomla core for a long time. But it still persists. I have a question for you: Do you have any plans to update your fork in the future? Do you plan to add the updates that are in the latest official version of K2? Thank you

[mgscreativa]

Same question...

[eworkers]

Hello,

First, thank you for checking in — we appreciate your patience. We’re barely catching our breath after the war. Communications within our team were disrupted, and our members were scattered between Gaza and Lebanon. We lost a dear teammate and many family members; we’re still grieving and doing our best to support the survivors and rebuild. That has understandably slowed our work and left us playing a difficult game of catch‑up for the last two years.

That said, on the technical side: we do plan to continue this line of work and have a concrete roadmap. We are preparing a complete, maintained fork of K2 called Quantent. Quantent started as a custom solution for an enterprise client who was stuck on K2 with a very large content footprint; we reworked and modernized the codebase to handle that scale. Our goals for Quantent are:

• Full, ongoing maintenance — we will keep the project actively maintained.
• Compatibility with modern Joomla — Quantent is already compatible with Joomla 6 and we are committed to supporting Joomla 7 as it becomes relevant.
• Improved architecture and new features — we will remove legacy code and features that no longer make sense, add practical enhancements, and make the codebase easier to extend and secure.
• Third‑party friendly — it will be straightforward for existing K2 add‑ons and third‑party developers to extend or adapt their integrations to work with Quantent.

We know migration is a major barrier, so we’re building a migration tool that automates the transfer from K2 to Quantent. Right now some migration steps require manual intervention; our tool aims to fully automate the process so site owners can move safely and reliably without heavy manual work.

Timing: we expect to publish Quantent and the migration tooling within about 1–2 months from today.

If you or any developers here are interested in early access, testing, or collaborating on adapter guides for popular K2 extensions, please let us know — we’d welcome the help and the feedback.

Thanks again for your message and for your understanding during this difficult period.

[shoulders]

@eworkers Thanks for the update, but one major question, is Quantent going to be free?

[eworkers]

yes, 100% free

[shoulders]

Thank you 😀

[eugenkyiv]

Hello. I am sincerely glad to hear that everything is fine with you! And I am glad to hear that the project will be developed further. But I have a question and a request. Could you update K2 to Joomla 6 so that we can test it on it (also test its compatibility with third-party components) I use the acymailing integration component, and I critically need to maintain its compatibility

[shoulders]

@eugenkyiv

It will be compatible

Compatibility with modern Joomla — Quantent is already compatible with Joomla 6 and we are committed to supporting Joomla 7 as it becomes relevant.

you need to wait a little while 😄

Timing: we expect to publish Quantent and the migration tooling within about 1–2 months from today.

or

If you or any developers here are interested in early access, testing, or collaborating on adapter guides for popular K2 extensions, please let us know — we’d welcome the help and the feedback.

[cmirnow]

Hello. I am sincerely glad to hear that everything is fine with you! And I am glad to hear that the project will be developed further. But I have a question and a request. Could you update K2 to Joomla 6 so that we can test it on it (also test its compatibility with third-party components) I use the acymailing integration component, and I critically need to maintain its compatibility

I am joining this question and request.
Is the K2ForJ4 fork able to work on Joomla 6?
Does it even make sense to test the component and its plugins on J6?
Is it possible to adapt it to the current version of Joomla 6?

Separately:
@eworkers, I sincerely hope that you and your loved ones manage to stay safe in this horrific catastrophe.

[krmrtrzv]

@eworkers,thank you for getting back, much appreciated, and my condolences for all the souls you lost in that devastating disaster! I hope you find the strength to rebuild!
It is a great news that you are planning to reincarnate the dead K2! All this time I was wondering what to do with my sites based on K2.
I am looking forward and willing to test the new component and the migration tool and to be of any help that is in my scope.

One request/suggestion: big part of the power of K2 was that it integrated in one editor all the media one would include in a piece of content: not only main content but also images, galleries, video/audio, tags, attachments, etc.. I mean the integration of Simple Image Gallery Pro and Allvideos were, at least for me always the standard package to install. Now that JW abandoned all their Joomla projects (AllVideos still work but god knows if it will in J!6), I miss not only K2 but SIG Pro too (I mean a full graphic interface of a gallery with captions integrated in the editor). I managed to update it to work with Joomla 4/5 (yes, its proprietary but abandoned, right, so I can fix it for my own sites) by removing the old code and replacing it with the J4 calls, but it is not a roadmap, just a temporary clumsy fix with lost of deprecated code.
Do you consider it makes sense to build a replacement for Sig Pro, so the full power of the CCK will be restored in max?

[cmirnow]

Is the K2ForJ4 fork able to work on Joomla 6?

Or, perhaps, we should stop hoping that Fotis will continue developing K2, now for Joomla 6? As, if I'm not mistaken, he once promised this, but broke it, just like his other promises?
In this case, users of the K2 component should only rely on Quantent, since there's no point in further preserving the component's database structure in hopes that the original extension's developer will return to development.@eworkers
, please tell me, will there be an option to upgrade from K2ForJ4 to Quantent? Thank you in advance for your answer - this is important.

[shoulders]

please tell me, will there be an option to upgrade from K2ForJ4 to Quantent? Thank you in advance for your answer - this is important.

There will be because currently K2ForJ4 has the same database structure as K2 and this was point when developing K2ForJ4.