I host quite a few sites over a couple of servers, but most of the XOOPS sites I host are my own, which are now down to 3. People go more for Wordpress or Joomla these days.

I would be offering specialist support as the main draw, with things like the auto-install being an extra feature. I think I'll have to do some more research to see if there's enough demand for it.

Hi all,

I've been hosting web sites for around 14 years now, and have been hosting my own XOOPS sites getting on for 10 years, as well as having written modules in the past.

I have been considering offering a XOOPS web hosting package, with support for those who need it as I know my way around XOOPS reasonably well (even though I've had a break from CMS stuff for a while). I am thinking of this for two reasons - one, obviously (and to be honest and up front) to help bring business to my web hosting service, and also to help support XOOPS and its users.

So, while I know XOOPS works on my servers without issue that I have found so far (apart from some older modules not liking newer versions of PHP), I was wondering if there was any "must have" features or options you've run into.

My basic (generic) package would support a small XOOPS site, but would people buy a specialist package tailored to XOOPS, that also included a certain amount of support for if/when you had problems?

An example would be: If you choose a XOOPS based package, the latest version would be installed automatically when you ordered, so you can then go straight in and start building the site without having to install it yourself.

I get the same problems as chefry with Xortify, same version and also XOOPS 2.5.1. Sadly it seems unusable for me at the moment.

Ah, thanks, that pointed me in the right direction.

For future reference for other people, the class name has to be:



Where <Modulename> is the name of the module (automatically filled if not specified, and <Filename> is the name specified.

I've tried using the xoops_getmodulehandler() function for the first time, but have had little success.

As I understand it, you use the name of the class file in the module's class directory (without the .php extension). With the module's name (directory name) as an option.

I can duplicate a file and give it different names, but it might only work if I use "menu" for example, if it's called something else, it fails.

I'm not sure if I'm missing something here or not?

For example:



I've not done much coding over the last couple of years, so I'm rusty and looking at the function itself is not revealing anything to me.

Quote:

Thanks :)

Following up a recent thread, I am starting work on a new version of my module, AM Events. This is will be coded from scratch.

It's normally easier to plan ahead for features than to add them retroactively, so I would appreciate it if you have any ideas or feature requests to add them here:

http://code.google.com/p/amevents/issues/list

Thanks for the replies and support!

I've set up a project page for it - I would appreciate it if anyone has any feature requests to add them to the tracker.

Thanks for the replies!

To answer some stuff, and give a little background or info on modules (some were started over 5 years ago, and things have changed since then):

Articles
My first module - I don't think SmartSection existed back then, and there was only the very basic (and IMHO terrible) "Sections" module. I forget what else there may have been at the time.

This module is dead in the water now anyway, and I had planned a "version 2", but all my notes and the initial module was lost in a HD crash.

AM Contact
This came about because there was no module with a decent Captcha solution. Liaise was also overkill for what I wanted.

I think I will just "polish" it off at some point and make it a full release.

AM mini gallery
Came about as I needed a simple way of adding/embedding a small gallery into an article. But at the time there was no way to do this without editing a main XOOPS file, which a lot of people either could not do, or were not willing. Of course, it's apparently easy to extend the text sanitiser class now (although I have no idea how this is done yet).

I think I will continue with this module.

AM Events
I no longer need this module myself, but I did at the time. This version is dead in the water as inexperience meant I made a basic mistake and it is essentially a security risk.

I will need to start from scratch with this module. A "version 2" was planned.

AM Reviews
I got very close to a release version of this, but it was lost in the HD crash mentioned above. I did manage to retrieve an older version from CVS, but all my notes, code sample and hours of work was lost - along with my will to continue with it.

I may restart this module.

AM Directory
A directory module I wrote specifically for one web site at [url]http://www.dogs-welcome.co.uk/modules/amdirectory/[/url] - work on the site has also stopped, but you canb view it by logging in as guest (both user and pass).

Let me know what you think of it. I may try and finish it and release it.

AM HTError
Was an attempt to make an easy way to display and log 404 pages, and stuff, integrating it into XOOPS. I think it's useful

I think I will carry on with this module.

I think that's mostly it. Apologies if I've bored anyone.

A few years ago I wrote some modules for XOOPS, which include Articles (please do not confuse with the similar named module called Article), AM Events and a couple of others that I started but never got to a proper release stage. My modules home is athttp://support.sirium.net

Due to health and other personal reasons, I had to stop developing them and they have (IMO) fallen behind and are somewhat "stale", even though they still work with the latest releases of XOOPS (I believe).

However, now I think I have time to work on them again - the problem is I don't use XOOPS as much these days and tend to either use Wordpress or Joomla (spit), mainly because I simply can't sell XOOPS as it *still* does not have a built in SEO URL solution.

And Joomla and Wordpress usually has all the modules/plugins you could need, so there's little need to write my own for them.

So now that I do not have the need for myself any more, it makes me ask the question - do you still want me to develop my modules? Is there any demand for them?

I'm also interested to know if people would be willing to make donations as an incentive? BTW I have had a donation thing on the side of the web site for years, but have never received one single donation. Not sure if I would if it was more obvious. Please bear in mind that the modules would remain free, unlike many Joomla plugins.