As of February 3, 2025, ISPConfig 3.3 has not yet been released. The latest official update from the ISPConfig team, published four weeks ago, indicated that version 3.3 was scheduled for release at the end of January 2025. This update also mentioned the introduction of a new WordPress Manager extension, with a beta version expected in the following days. ispconfig.org Given that these releases are overdue, it's possible that the ISPConfig team has encountered unforeseen delays. As of now, there have been no official announcements regarding a revised release date or the cause of the delay. For the most current information, I recommend regularly checking the official ISPConfig blog at https://www.ispconfig.org/blog/ or reaching out directly to the ISPConfig support channels.
Ok, that's one way to try and trigger a reaction from ISPC team It will be ready when it's ready. As with everything in life. Better a good working product than a bugged product and waiting on patches. If the team has new information to share they'll surely share it in the proper channels.
ISPConfig 3.3 will be released when its development is finished. There have been some delays in the development, so it will likely take 1-2 more weeks to finish it. The WordPress Manager requires ISPConfig 3.3, so it makes no sense to release it before ISPConfig 3.3. As you referred to the blog post, I've changed the release date to February now.
Thanks for the update—I really appreciate your prompt response. We're all keen to hear the latest, especially as I’ve been asking about the WordPress module for three years now! It has to be one of the most requested features from customers, so it's great to see it finally coming to life. Anyway, thanks for all your hard work—I’m looking forward to test-driving it!
A realy big part of ISPC's code is community driven. All volunteers who like contributing to the project and taking ISPC to a higher level. Most have normal fullltime jobs so time is always an issue. Release dates, if any, in projects like this are never fixed and can change because of all kinds of reasons. Your post seemed to ask about a new release date without actually asking it (saying the release date was missed) and didn't add anything of value. Anyone who's interested in the project already knows where to find the proper channels for news, updates etc.
software hardly ever gets released on time, and if they do, it's usually because features announced as being in that version got postponed to a later version so that they can get what is working out on that date, which can be even worse, having to go through a (sometimes painful) upgrade only to realise that the feature/bugfix you were eagerly waiting on is not in the new release. Or they just release a very buggy version on time, hoping most people won't need to use the buggy bits so they can (hopefully) fix it quickly with patches before there's too many complaints. much better to treat announced release dates as a guideline and expect it to actually arrive 2-4 weeks later depending on complexity. i'd rather have it a bit late and working properly, or have some features delayed, than have buggy software rushed out to meet an artificial deadline.
Any further updates? I've tried to follow progress via Git, but my account hasn't been approved (also after repeated emails) Yes, I know it's free software and the release will be ready when it's ready and all that... Still, if you make an announcement you'll create expectations, so of course people will ask for a status update. Especially if you set a deadline, miss that deadline, say there's a 1-2 week delay and miss that too by more than a month, without any communication. Don't get me wrong, I appreciate the effort that the developers are putting in and I know that it's mostly community driven (ie. people are volunteering their time). All I'm saying is, if you make public announcements then you create expectations. Either keep people updated or delay your announcements until the release is ready. Just my two cents
Thank you for your comment. We are making good progress, and I will announce it when it is finished and released. If you are eager to get the new functions, run ispconfig_update.sh and choose the development branch, and then you get them. If you send me a PM with your git username, I can check why it got rejected.
ISPConfig 3.3 beta 1 has been released for testing. https://www.ispconfig.org/blog/ispconfig-3-3-beta-1-released/
I don't think that we have any breaking changes in API. When it comes to PostgreSQL support, there was already a parameter for the database type, which was always 'mysql', and it now also supports 'postgresql' in that field. Besides that, the extension installer has no API yet, but it has a commandline option, the command is 'ispc extension'. And if there have been any new 'fields' in the UI, these are available in $params array of the matching API call automatically.
I just want to say many thanks to ISPConfig team for the 3.3 new release! I specially like the SSLCert auto cleanup & the PHP version of SSH users aligned with the website version. Those features will save my time. Now, I’m waiting for the 3.4 release for next great features ;-) Long life to ISPConfig!
Many thanks to Till and the team behind ISPConfig! I am very happy with the new version as it generated a lot of expectation. Installing new extensions with just one click is amazing. Just a quick question: I can't find the new announced WordPress Manager extension, I imagine it will be added to https://repo.ispconfig.com/, is it still under development or am I looking wrong?
Yes, it will be added there. The extension is already complete, but I still need to finish the actual installer. I hope I can publish it there in a few days.
Again expectation are set high, due to various announcements. This time for the long awaited WordPress Manager extension. Blog post January 6, 2025: "ISPConfig WordPress Manager...This will be released in March 2025" Blog post March 31, 2025: "More extensions like the ISPConfig WordPress Manager will be available in the next few days." Blog post April 25, 2025: "More extensions, such as the ISPConfig WordPress Manager and ISPConfig Billing Module will be available in the next few days." And finally the previous forum post in this thread, Apr 28, 2025: "I hope I can publish it there in a few days." I would really urge you to reconsider how / when you announce releases. As i mentioned in my previous post: "If you make public announcements then you create expectations. Either keep people updated or delay your announcements until the release is ready." All the best with finalizing the new extensions though.
The team is not trying to mislead anyone. These annoucements get shared to keep the community in the loop and show what is coming up in the project. But like many free and open soruce projects, the team doesn't have fixed timelines. Things get delayed due to real-world limitations like technical hurdles, shifting in priorties (like fixing bugs after the 3.3 release) and just not enough time in the day. If you’d like to see the project move forward faster, consider contributing. Whether financially, by helping other users or by contributing code and documentation. Every bit of support makes a difference in reaching the project goals faster.
