Which modules to prioritize for updates?

Trying to get a feel for which modules to focus on updating to work better with ImpressCMS 2.0 and up. Which ones are you using? Which ones are holding you back from upgrading to 2.0?

I'm looking into the content module at the moment. I've already updated iforum to work with ImpressCMS 2.0 RC2 as well as news and sprockets.

I'm having trouble with imblogging : I can't get the blog overview page to work. The rest is humming along nicely but I get a white page after a long while when I go to the start page. Probably a timeout somewhere.

Thanks, David!

I'm having pretty good luck with imBlogging - it's a module I've used considerably. And, with the changes I've been talking about in the icms_ipf_Metagan post, it's still working well. Basically, I'm using what's in the master branch on github, plus some changes I've shared in the metagen post.

For your blank page - could it be a permissions or cache issue?

What would be a good place to track which modules have been tested and work on 2.0, and which ones we'd like tested?

I installed it on a PHP 7.4 running ImpressCMS 2.0 RC2 with mariaDB10, the database might also be a factor. I'll verify today (it's past midnight, woo-hoo )

I was thinking of perhaps extending the downloads module we now use on icms.org with tagging support (imtagging or sprockets) and using a label to indicate compatibility.

mariaDB isn't something I work with, so let me know!

I would like a Downloads module - trying to migrate to Downloads (QM-B's module) isn't working fully. I've found some things related to how the db schema is handled by IPF and how the latest MySQL won't allow default values for text, blob, or json fields.

well, MariaDB should, in theory, be compatible with MySQL, but there will of course always be subtle differences in how they work. But it's becoming a popular alternative to Oracle's MySQL so it would be logical to verify the compatibility.

I was first thinking of patching up the downloads module, to have a more or less quick fix. But given the number of issues you encountered already, perhaps it will be faster to re-start from scratch then. I've been analysing some parts for several months now, I'll see how it goes.

When it comes to modules that would be nice to get to work on 2.0 : imbuilding could definitely use an update, both in its working (I never got it to work in its latest version) and in the code it generates.

What's the latest version of the profile module? I had version 1.3 present and not installed on the SimplyWiki site and when I upgraded it to ICMS 2.0, the module admin page was broken - lots of old class and object references. Once I removed the folder, everything was fine.

BTW - www.simplywiki.org is now running on ImpressCMS 2.0!

Profile needs lots of fundamental security  fixes, and there is at this moment nobody maintaining it. More details on H1.

Re: Profile - thanks.

Re: ICMS 2.0 - I'm noticing a debug message occasionally about being unable to write session data at the close of a session. It doesn't seem to hinder anything and is not constant. May be related to your blank page after some time has elapsed?