What was the last working SVN update that worked with 2.4.5? i.e., the pre 2.5.x. Thanks!

I agree that the Article module is the most feature rich module when compared to the news module, and it does news, blogs, pages, etc. However, it is not bug-free nor complete. The News module works OOB.

Also, I've found that most clients don't need the functionality of the Article module. Most just need/want a simple news module with solid, simple functionality. The News module does just that and does it well.

As to templates and layout, I've found that I always have to play with templates to make them work well for any website. No one is ever happy with the default layout of any module, it seems.

As to the Article module, I have a bug-free version I'd be willing to share in the SVN, and will work with the team to get it up. There is still some missing functionality, but not that I've needed to put into use yet.

Und ich spreche nicht gut Deutsch.

It would help if you gave the version of XOOPS, the module you had problems with, what you did to "cause" the problem, more description about the problem and exactly what has changed, and what you have tried to solve it.

I would recommend the news module for news. It works well. The article module by phppp showed promise, but the one linked to is an RC with some bugs and incomplete functionality. I have fixed the bugs that I've found.

My notes on these two modules: News | Article

Also, my notes on various news, blogs, and similar modules.

Also, don't confuse Article with Articles, which is a simple news module based on an earlier version of news module.

I'm pretty sure that I've posted all this info here on X.o somewhere....

Others: Article 2.00 RC Test Request | Article 2.00 RC

Good luck!

There is an OpenID hack floating around here that is on my list of things to try. I'm a huge fan of OpenID. That would be an excellent addition.

I also find interesting Drupal's approach where (if given permission from each end) you can login to any site based on your login at another site.

That said, I prefer the OpenID type of integration over this type, but both have the circle-of-trust concept at work.

Perhaps not, however if you were to talk about your needs, hi-level functional requirements, and workflow issues, perhaps we can suggest some things for you to use.

I'm basing this off 1.63 as I've not put 1.67 into use yet. However:

archive.php line 114:


remove the expired stuff from the where clause so that it looks like:


You will also have to change the article page to allow expired articles to be viewed:

article.php lines 144-158:


You can likely just comment all that code out and it should work.

YMMV.

Things XOOPS needs:

SEO URLs - ability to add keywords to every page; it's arguable whether or not these actually help as much as links to the page, but everyone asks for it.

xoRewriteModule - include this in the core along with a method to change the directory name through modules manage that reroutes to it (requires mod_rewrite, of course). Requires some changes to a few core files along with search page and more. Make search page run off a template.

Image Thumbnailing - a method that will auto-generate thumbnail images and call them from within content, especially the WYSIWYG editors (such as FCKeditor, my fave).

Workflow - The ability for users to have/need approvers for content. So a user's posts in any module either requires approval and/or generates notification for/to approvers. So many folks ask for this. We usually just kludge it somehow or go without and trust more.

Event History/Audit Log - for administration, able to turn on and off, archive, log-rotate, etc.

Comments notifications - all and/or by module and/or by module categories (or similar segmentation).

Blocks Anywhere - merge both (from trabis and Catzwolf) and make it more easily available for use.

XOOPSforms - modified to use templates (and specify custom templates) and specify better CSS ids and to thus allow better layout on sites on the user side (most all web folks I've done sites for don't like the generic forms appearance).

Use Templates for Everything - there are still some pages that have not been smarty'd. This includes XOOPS forms among others. We should take the HTML out of every page on the user side and use templates.

Additional smarty variables for use in templates: xoops_modid, xoops_modname, xoops_modsearch, xoops_name, among others.

XHTML 1.0 Strict CSS, although HTML 5 is coming.

Some additional site/user/module tokens for use in mailer templates.

PM allowed via settings to send via email instead of solely PM on the site, allowing admins to select one (or more) and to default to one (or more) and to allow one (or more).

I'm glad to see a focus on getting a regularized interface for administration of modules. That's what tends to confuse users who aren't techies. It will help new adopters, too.

I'm also willing to work on these and other parts as desired. Some of them I've already done for installations I use. And documentation remains a key thing that XOOPS doesn't do as well as other CMSes. But I don't find another better, realistically.

Try the Subscriptions Module. I've used it successfully.

I was looking for this today. It was released by Red Mexico, seemingly a member of the defunct XOOPS Mexico site.

I managed to find a link to RM-Soft Library 2.0 (according to the xoops_version and language files).

I'm looking for a copy of the latest RM-Soft Library module (dirname rmlib). Version 2.0.1 is the last reference I found.

There is also announced a Hack for NetPBM/ImageMagick, but those links are dead now.

I'm also looking for the English Translation (with Russian) referenced in this review request.

Note: this requires the RMSoft Common Utilities, too. I found version 2.0.1 (interestingly the only location I found it at was on a forked XOOPS site).

A community project I'm working on is the focus of the request.

There are some other RM-Soft modules that I don't think are available on the community site that might be worth archiving as well.

I'll at least upload both of these modules to the SVN.