Quote:

I did not realize it's so flexible! Will try it ASAP, thanks!!

A great feature/module option for everyone, would be the ability to prevent anonymous users from seeing attachemtns & images in the forums and modules (smilies, attached files, attached images, etc), while still being able to read the text in those pages/modules.

It would help promote membership to the sites that use it, and would help organic SEO growth by allowing the robots etc to see everything 'text' in the module. Right now, if anonymous users are denied access to the information, so is the robot, etc.

Thanks!

Quote:

HOOORA!

Could someone turn this

http://www.phpmycomic.net/

into a XOOPS mudule?

Quote:

Very interesting, so this is basically a database specific to comic books, artists, issues, etc... ??

We would simply need to break down the features and also the specific data fields associated with each data type.

Quote:

Its probabl;y the best thing I have found for free that keeps track of ones comics. Converting it to a XOOPS module would be much appriciated!

Last year I would have said that a good business directory would be the most desirable module. Now, however, with mxDirectory and efqDirectory coming along nicely, that hole is hopefully filled.

A good classified ads module would be my next choice. There used to be much demand for this, but people have, I think, pretty much given up on it. This is, in my opinion, a module that every site could use. Worldwide Classifieds 4.0 is a nice script, is inexpensive, and they will integrate it into Xoops, but it is not a module. Class ads would be my first request.

My second request would be a really simple module, and also widely applicable--a birthday/anniversary module to spotlight users' birthdays and anniversaries in a nice way.

Thanks for asking.

Jere

I have been working with Drupal as well as XOOPS as I think it's a good idea to notice what other CMSs are doing. One of the most important developments with Drupal is the Taxonomy system (categories and classifications) without going into long descriptions (and it is complex) the main point is that XOOPS needs to be able to classify content in a different way.

1- With XOOPS modules the issue is that most of our categorisation is linear, that is we only have one parent as a category and subgroups or categories as children of that parent. phppp has begun to break away from this concept with the content module, but I feel this needs expanding into a more taxonomous categorisation, where content can be placed in more than one category allowing for cross reference.

2- Another issue- Currently we are too ridgid in the concept that one type of content (ie photos) can only be used within a certain module and other content cannot be easily added. Sure we can hack a module and add stuff, but again the classification of content is still linear.

Proposal: A module that allows a real taxonomy rather than linear classification of content, also facility to add different content medium.

With this concept XOOPS would become open to a whole new area of website structure, appealing to many more users. In addition we would begin to appeal to professional business market who require a more flexible and comprehensive form of data display and retrieval.

I gues one of the challenges is the way core data is stored and organised and this is where Drupal's 'node system' scores. Maybe XOOPS data storage does not lend itself to this kind of organisation. I am not a software developer, but seeing you ask the question about new modules, here at least is a concept to work with

Quote:

This is a very good point and it is something I've been thinking about lately. One idea is to have a feature called XoopsBots, which would provide a module wide hook (setup in xoops_version.php like a search hook it for example) that would enable content from one module to be displayed anywhere. In the example of the gallery module, specific pictures could be shown anywhere in a XOOPS site by a simple markup (TAG.GALLERY[PictureID] for example). Another Markup up would be {TAG.ALBUMS[AlbumID]} to display an album for instance...

This markup would be intercepted by the Text Sanitiser, passed to the relevant module and rendered. Almost like smarty tags but for modules.

I might do a such a hack to the core and present it to the core team if there is enough demand for such a feature.

Cheers.

Thanks McNaz for taking this up; you wait till tzvook sees this... he'll be banging your door down! I know there are others who are very keen on the idea. My guess is this concept will be very popular, when users descover how it can improve the flexibility of their websites.