Needs the comment.php from spiders cloud, for a feed of comments off the system, like backend.php and sitemap.php feeds.. This is to bring it inline with wordpress' RSS Comment feed.

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.

Log in via social networks is a must.

After looking at rm commons it kind of hit me that we should look at possibly adding support for plugins in 2.6. The intention is to eventually work away from having ANYTHING built into the core. Things like the image manager, PM, Profile, comments, rankings, etc... Perhaps even things like authentication, and some other things.. Things that are light enough they don't need to be full modules. Thinks we have preloads for now plus others.. This would allow easy replacement of base stuff without having to rewrite core. Make the core lighter can't be a bad thing.

Rodney

Fields that are defined with INITVAR() need to have database functions specifiable.. For higher functions of mySQL and other databases..

ie:



As well as there needs to be a strapping for modules like onInstall, onUpdate and onUninstall for preference changes in system called onPreferences for when particular details like salts and other information are changed.

This is so if you are using crypt functions for example and a database and someone changes the salt in the preferences then you can patch the values in the database, the need to be passed the new preferences values with the old preference values as well so there would be a pre function as well as a post function for this the pre is passed the new values and the post is pasted the old values.

Quote:

This would be done with profile module.. I might make the changes at some point to do this.

Thanks

Simon

Please do... It's very nasty logging on traditional way. Idea is to make a user, but autification with captcha and fb, twitter etc.

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.

blocks show with expiry date...show on certain days etc

just like what trabis did with mytabs module..

My wish list:

1) A great news module like V1.44, with a view counter..
2) Clean - SEO urls all over xoops, also in news items.. (drupal style)
3) A greater and newer comment system, with example captcha option for non-members to post a comment. (WP style)
4) Auto. Mobile website viewer for iphone, tablets and other mobile devices.
5) Integration of editors: jQuery
6) Supporting multiple database drivers
7) Supporting multiple authentication drivers, including native xoopsDB, LDAP, OpenID, etc.
8) Supporting multi-site feature
9) Supporting multiple template engines thus customized template engine (great to make different mini sites, in your site)
10) Embedded security protection against XSS and sql injection to free module developers from security concerns