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.

I will release the module very soon.

Demo:

https://turkish.erenyumak.com/modules/xcreate/item.php?id=2

Another great contribution from you! You're on a roll!

I can't wait to test it!

Viva XOOPS!

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.

Demo: https://turkish.erenyumak.com/modules/publisher/item.php?itemid=25

Download: https://erenyumak.com/xoops-temalari/31-xoops-custom-field-module-xoops-ilave-alan-modulu.html CustomFields is a powerful extension module developed for XOOPS CMS that allows you to dynamically add custom fields to any module.
Without writing any code, you can easily define custom fields from the admin panel and enrich your existing modules.
FEATURES
14 Different Field Types:
✓ Text (single line)
✓ Textarea (multi-line)
✓ Rich Text Editor (HTML)
✓ Number
✓ Email
✓ URL (Link)
✓ Phone
✓ Date
✓ Date-Time
✓ Checkbox
✓ Dropdown List
✓ Radio Buttons
✓ Multiple Select
✓ Image Upload
✓ File Upload
Admin Features:
✓ Easy management via admin panel
✓ Sorting (drag & drop or by weight)
✓ Required/optional field selection
✓ Field descriptions
✓ Default values
✓ Active/inactive status
Display:
✓ Smarty template support
✓ Flexible display options
✓ Customizable with CSS
✓ Automatic form integration
Easy Integration:
✓ Ready-to-use integration for the Publisher module
✓ Simple API for other modules
✓ Minimal code changes
✓ Unaffected by module updates
USAGE EXAMPLES
EXAMPLE 1: Build a Real Estate Website Using the Publisher Module
Scenario:
You want to display detailed information in your real estate listings.
Added Fields:
• Price (number) – Listing price
• M² (number) – Square meters
• Number of Rooms (dropdown) – 1+1, 2+1, 3+1...
• Floor (number) – Floor number
• Occupancy Permit (checkbox) – Available or not
• Mortgage Eligible (checkbox) – Can a loan be used?
• Map Location (URL) – Google Maps link
• Floor Plan (image) – Plan image
Title: Apartment for Sale in Central Location
Price: 2,500,000 TL
Area: 120 m²
Rooms: 3+1
Floor: 5
Occupancy Permit: Yes
Mortgage Eligible: Yes
[View Map Location]
[Floor Plan Displayed
With the CustomFields module, you can customize your XOOPS site without limits. Add the fields you need in minutes — without writing any code — and tailor your site exactly to your requirements.
Fast • Flexible • Secure • Customizable
© 2025 XOOPS CustomFields Module
Developer: Eren Yumak – eren@aymak.net

That looks very cool!!!

I can't wait to test it!

Bravo!

With this smart add-on, you can display the contents of the Publisher module anywhere you want in your theme, independently of the Publisher module's blocks.

Example:


custom category="5" = category selection
order="rating": Sorting type
template="publisher_custom": Template to be used
limit="5": Number of articles to display
status="2": News with an active status.

You can find many more example codes and all parameters in the README_EN.md file.

Example usage in theme.tpl

XOOPS Publisher Custom Plugin is a powerful and flexible Smarty plugin developed for the XOOPS CMS Publisher module. With this plugin, you can display your Publisher module content anywhere in your theme files, in any format you desire.

DEMO:
https://turkish.erenyumak.com/

DOWNLOAD:
http://erenyumak.com/uploads/shared/Publisher-Smart.zip

All detailed explanations are available in the README_EN.md file.

Examples

Thank you for letting us know.
Please follow up on GitHub: https://github.com/XOOPS/XoopsCore25/issues/1588

Hello,
good job!

I always use an old version of Xoops (2.0.16...) on my site aquaportail.com but sometimes, I use the most recent versions of Xoops to hack "my" code for a better compatibilty with recent versions of PHP.

There's a real problem with PHP 8.4 in kernel/common.php with implications in kernel/functions.php. Fonctions to open, read, etc., a session are not compatible with 8.4 for session_set_save_handler with xoops_gethandler. "$sess_handler = xoops_gethandler('session');
session_set_save_handler..."

Just my two pences...

Jef

I just submitted a solution which hopefully will self-correct the issue:

https://github.com/XOOPS/XoopsCore25/pull/1578

Please check it out and let me know if it works.

Actually, instead of specifying the domain like this:


you can use:


And to give you more background, the old, incorrect setting only worked because browsers used to have very relaxed security rules for cookies, which they have since tightened significantly.

Old Behavior (Pre-XOOPS 2.5.11 & Older Browsers)
In the past, when a cookie was set, browsers defaulted to a SameSite=None policy. This meant a cookie could be sent even if its domain (myhoster.com) didn't match the website's domain (mywebsite.com). The browser saw it as a "third-party" cookie but allowed it to work for logins. This was a fragile setup that relied on insecure defaults.

New Behavior (XOOPS 2.5.11+ & Modern Browsers)
To prevent security vulnerabilities like Cross-Site Request Forgery (CSRF), all major browsers (Chrome, Firefox, Edge) now default to SameSite=Lax for cookies.
• SameSite=Lax means the browser will only send a cookie if the domain in the cookie matches the domain of the website you are currently visiting.
• When your user on mywebsite.com tried to log in, XOOPS told the browser to set a cookie for "myhoster.com".
• On the next page load, the browser looked at the cookie for myhoster.com and said, "Nope, you're not on "myhoster.com", you're on mywebsite.com. I'm not sending this cookie."

So again, if you have set the XOOPS_COOKIE_DOMAIN to something that is not your domain, just replace it your domain name, or simply with: