XOOPS doesn't use the "includeq" anymore, but the standard "include"
You can fix it manually by removing the "q", but what you should do is to run the "Upgrade", by copying the /upgrade folder from the XOOPS distribution to your website, and then run it from there:
I added the xsitemap 1.56 module to a Xoops 2.5.11 site. From the user's perspective, the sitemap displays perfectly. However, there is a serious problem in the administration panel :
Erreur: SmartyCompilerException: Syntax error in template "db:db:xsitemapadminindex.tpl" on line 2 "<{includeq file='db:xsitemap_admin_header.tpl' }>" unknown tag 'includeq' dans le fichier /class/libraries/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatecompilerbase.php ligne 2
I’m sharing this message a bit in advance, as I will be away, but I wanted to sincerely thank you all before I go. Thank you to everyone who contributes to the Xoops project in any way: developers, translators, testers, module creators, community members, and dedicated users. Your time, ideas, and passion are what make this CMS truly special.
Xoops continues to exist, grow, and improve because of you. I encourage you to keep using it, sharing it, and helping it evolve, with the same energy and collaborative spirit.
I wish you all wonderful end-of-year holidays filled with rest, peace, and meaningful moments, and already wish you a great year 2026 ahead—full of new projects, innovation, and shared successes.
Thank you for your commitment, and long live Xoops!
You can think of the xcreate module as an empty module. After installing this module, it can be transformed entirely into a module that fits your needs. While creating a category, you can create two tpl files: one representing the short.tpl section and the other representing the full.tpl section. Let’s explain this with an example.
Suppose you need a game download module.
Category name: Game
Let’s say the custom fields we need are as follows:
For the game download link: use “Field Type = URL”. Let’s enable the dynamic duplication feature because a game may have multiple download links.
For the system requirements field: let’s use an HTML editor. No need for dynamic duplication.
For the supported systems field: it should be a Multiple Selection field.
For the game images field: use an Image Gallery.
You can create as many fields as you want for this game category, and you can enable or disable the dynamic duplication feature for each single or multiple-use field.
All Available Custom Field Types:
Text (Single Line) Multiline Text HTML Editor Image Upload Image Gallery (Multiple) File Upload Dropdown List Multiple Selection Single Selection Date Picker Date-Time Picker Number Email URL Color Picker
With this logic, you can create as many categories as you wish—such as a music download category, movie download category, real estate category, etc.—and meet your needs through custom categories and custom fields. Since the short.tpl and full.tpl sections are independent from each other, you can design completely category-specific layouts.
The Xoops Custom Field Module that I have been working on for a long time is now ready to be tested. The module can be used with all Xoops modules, but you need to implement the integration for the module you want to use it with. I have completed the integration for the Publisher module, so you can test it with Publisher. I will prepare a tutorial when I have time.
