Another option, depending on your audience, is to use the new HTML5 input types. If you only need time you could use the "type=time". If you're looking for users to to enter a starting time/date and ending time/date then type="datetime-local" might be a good solution.

Michael,

You can also look at the changes I made in my fork (from your GitHub repository). It's pretty extensive so you might have to merge them 'over time'. This change is already there but there's pretty significant changes elsewhere. I haven't had time to test most of it out yet so "caveat emptor"

No problem. Glad that "did the trick".

Janice,

You should have replaced:


with:


So now if you just delete:


the error should go away.

supergran,

Replace this line in ./include/config.php:



with:



This should fix the error you're seeing.

Yeah.. Not sure it's lack of interest as much as it is a lack of time. I have the same problem testing the modules I'm working on - even I don't have time to test them properly so I haven't released them yet...

This module is very old and has not been updated in quite some time. It would need to be updated before it can be used in any "modern" installation.

I looked over the code and it took about 30 seconds for me to recognize that I would not recommend installing this on a production site (or even a test site connected to the internet). There are some security concerns that must be addressed before this module is used.

There is a XOOPS core system block which will allow users to select one of the available themes. Maybe this is sufficient for what you need?

You're not being stupid...

XOOPS search does not use templates. You will find most of the html generation (for the form) is created in ./include/searchform.php. There's very little styling done there since it uses XoopsForm - so to make changes to the CSS you'll either have to modify the searchform.php file directly or modify the theme or base (xoops.css) files to get what you want.

The html generated as the result of a search is primarily done through ./search.php directly. Again, styling is done "inline" with the code so you'll have to modify the php file.

I know this is one of the things that's been talked about "fixing" in the past but doubt any changes will be made to this code before XOOPS 2.6

By the way - the version of XOOPS Tag module that Mamba posted above no longer requires the Cumulus module. This version of XOOPS Tag includes a cloud (cumulus) block.

To find any errors that might lead us to the problem type a term in the search block and click the Search button. At the bottom of the page click on the "Error(s)" link and then let us know what is displayed. The output you showed us above is the SQL query that was made on your homepage instead of any error(s).

Since I can't remember if 2.0.16 administration panel displayed the system information the easiest way to find the PHP version is to do the following:
Create a file on your system with a text editor. You can call it anything but for simplicity just call it phpinfo.php with the following contents:



Upload this to the root folder (directory) on your web server using either an ftp client or your web server control panel (cpanel, etc). Go to your website and then type:



A report of your PHP configuration will be displayed. The PHP version is displayed near the beginning. It might be useful for you to print this out in case you need it later.

Important: DELETE the phpinfo.php file from your webserver. This file can give a potential hacker useful information if you leave it for anyone to find.

You can find the version of the module (mastop-publish) by looking at the Admin panel > Module page. Please report the PHP and module versions back here so we can see if there's either a known problem or help you "dive in" to find the problem. I looked at the current version of mastop-publish and does support search.