@alain01: I merged the latest core changes into my fork and I am looking at the updates to xSwatch4.

Since my version of xSwatch5 is based on the most recent version of Bootstrap/Bootswatch, and there are features there I need, I plan to continue my implementation there. I don't want to step on any toes here, so would it be OK if I looked at how you are using the core changes and see about incorporating the way you implemented a few things?

I will share my private repo once I get the next pass complete.

You will need to invite individual users by their GitHub user ID to your private repository.

See more info here, specifically the 2020 Update screenshot

Hi,
Nice news !
you can show your own repository first. (Github URl).

I have my own repository but I need to continue my efforts.
We've just merged some new features in the core here.

Maybe Mamba could propose another solution, let's see what he says!

I have a preliminary port of the xSwatch4 theme to xSwatch5 for Xoops 2.5.11, based on Bootstrap/Bootswatch 5.1.1. It also adds a second menu option for a responsive, offcanvas sidebar menu in addition to the original navbar menu.

This is currently a private project on GitHub, and still needs some additional tweaks for items removed in Bootstrap 5.1.1.

Is there some place you would like me to put this so that it is visible within the Xoops community?

I don't have the release date for XOOPS 2.5.11 (that's up to the Core Team), but the current code on GitHub is very stable, and as a matter of fact, we're using it here on xoops.org

Regarding updating your personal modules, you can take a look at the XOOPS Module Framework (XMF) and at the XOOPS Modules Cookbook tutorials. The last one is still work in progress...

Of course, the Module Builder can help with creating the basic module structure that is using XMF and namespaces.

You might also consider making your modules Open Source and upload them to GitHub, so if somebody has similar needs that your modules address, they could contribute to your modules.

Anyway, we're here to help, so if you need anything, just ask....

Thanks,
I will take another look at xmnews (and perhaps xmcontent) and see how easy it is to shut everything down so we end up with only basic templated pages that can be displayed with the MyMenus module.

Other than the basic text content, my modules are specifically tied to the various tables in our database which hold the information we want to display. I am afraid there is nothing generic in them that would be worth sharing. However, I will eventually have a few bug fixes to share once I finish with the upgrade project.

ok,
Glad you're using and developing your own modules.

For the submitted content, the group management allows you to easily adapt the module to your needs.
You just have to let only the webmaster group manage the edition / modification / deletion of the content.
And in the general preferences of the module, if it is well done, you can deactivate comments and votes for the whole module.
The xmnews module manages it perfectly, for example.

Concerning your own modules, do you propose them to share ?

@alain01: Thank you very much for the information, especially about monxoops.fr using Xoops 2.5.11 Beta 2.

I appreciate your comments about using existing modules, and agree that for many websites that is the correct choice. I initially started our website with a version of TinyD, but we are not a portal, do not support submitted articles or comments/ratings/etc and it is currently not open to new users. The webmaster is the only content creator, so about 75% of the functionality of the impressive and well constructed public modules really just gets in my way. I found Xoops when I was looking for a way to organize and maintain the website for our small non-profit organization. Every time I upgrade to a new version of Xoops I review the public offerings, but the needs of our organization are not met by these modules at this time.

I want to thank everyone at Xoops for the time you put into the product. Over the years it has simplified my task as webmaster. And since I needed to develop my own specific functionality to maintain and display the data in our database, being able to easily create my own modules has been a significant benefit. I have enjoyed seeing the code base continue to improve in features, structure and OOP constructs. I look forward to the upcoming releases, will use the latest ModuleBuilder with Xoops 2.5.11 to refresh my modules, and see if my testing gives me enough confidence to upgrade the website to 2.5.11.

Hi,
for a basic webmaster,
the answser is always the same :
The stable version is the 2.5.10 version.

But for advanced webmaster, sure,
xoops 2.5.11 comes with lot of improvement.

For modules, could list your modules ?
I think the best choice is to choose maintained modules,
I mean, with full fonctionalities on XOOPS 2.5.11.

There are several modules like that, for exemple, the xmodules.
So may be it's better for the future that your check your modules and watch ig you keep them or update to new modules...

For xoops, Know that monxoops.fr use a 2.5.11 beta 2 version.

@Mamba: Thanks. I can take a look at porting the Docker version to Xoops 2.5.11. The PHPUnit tests also look interesting, although at this point porting them does not seem to make sense.

It would be nice to understand what release strategy to expect for this version in relation to Xoops 2.6.0. Both appear to be in active development, but there does not seem to be a current Roadmap for Xoops in general. Do you plan to release Xoops 2.5.11 in the relatively near future?

I ended up here because, for a variety of reasons, I need to upgrade my website to Bootstrap 5.1.1, and in that process I also need to upgrade my collection of modules that run my website. A few of these were developed in Xoops 2.3/2.4 and they are in need of refreshing on the admin side. I would rather not have to do this work multiple times and it seems like Xoops 2.5.11 might have some admin improvements over 2.5.10. Would appreciate some advice/guidance for what to use as my code base.

Thanks for your help.