XOOPS 2.30 kick-off and task distribution

From XOOPS Web Application System

Back to Wishlist for XOOPS 2.30

From XOOPS Sourceforge Forum

XOOPS 2.30 kick-off and task distribution (New) By: D.J. (phpppProject AdminAccepting Donations) - 2008-01-09 09:07

Hi developers, we are now back on 2.30 branch, let's write down the part you are or will be working on so that we won't conflict with each other.

As far as I know, from people's emails or chats with me, some of the tasks have been taken:

• mboyden - profile module
• phelim - pm module
• dugris - admin area
• nekro - banner functionality refactor
• ppcm - user management crossing modules, persistance objects

If I made mistake, please correct me. I would suggest to create a branch instead of submitting commits to TRUNK directly IN CASE you have very big changes in code.

Meanwhile we have other developers on other branch, like julio_nc and me will take care of 2.0.18.1; I will watch 2.30 adding some minor fixes and continue my coding on 3.0

By: DuGris (dugris) - 2008-01-09 09:33 I worked on the installer (120976-install) for xoops france

• Request login and password administrator, if this is not the first installation
• Adding XOOPS_TRUST_PATH for GIJOE's modules (Especially for Protector)
• Adding Password strength meter for Administrator Account
• Adding Password generator for Administrator Account
• Adding "Site configuration" : Site name, Site name, Allow new user registration, Meta keywords, Meta description, Meta author and Meta Copywrit, by default, but other elements may be added in a configuration file
• Adding the installation of modules
• Adding Choice of the theme by default

By: Mark Boyden (mboyden) - 2008-01-09 09:40 Where will we present, manage, and get feedback for the functional requirements and enhancement requests for these tasks? These forums and the SF bug/enhancement tracker really are pretty poor frameworks for this. Will we do it on the wiki? I'd just like to see one, simple place to capture it all. I'll do a quick write-up on the Profiles module to present wherever this is, and then will solicit feedback from the community for it.

Also other things discussed have been:

• Updated Blocks Engine
• Updated Forms Engine
• Updated Editor Framework

as well as easier module cloning and SEO streamlining, among others.

However, I know this was generally a merge, so probably only the Editor aspect needs to be updated along with things like the admin area and such (includes blocks, templates, and other functions from the Mexico team, along with GIJoe's contributions via AltSys, right?)

I just think we need to make sure we capture stuff well and then move XOOPS forward well.

By: Xoops_Gold (xoops_goldAccepting Donations) - 2008-01-09 10:00

I have made many changes in the profile and system modules and works like a charm. This is for an association who required an extended profiles management.

Here are some enhancements:

• XoopsMailer gets an extra Command passed on from anywhere and that may change something within the function.
• Find Users is completely overhauled.
• A system of generating dropdowns by simply give field values somewhere.
• Possibility of making display modus for find users.
• Masks of find users looks very different than default, more functions and features.
• Results from find users enhanced.
• Extended statistics of groups and an overview of groups management with user-stats.
• Resetting passwords at the level of Xoops mailer where it is generated, inserted and send without display.
• Unsubscribe key management.
• Possibility of making ALL CHANGES viewable by the admin by inserting those changes in the profiles in the respective profile medium-text fields.
• Construction a Protocoll of all that happens in the account changes and saving it, including of logging, IP, etc.
• Possibility of using pre-configured templating system and applying those templates to selected user profiles from find-users of through email to groups functions.

Uh, I do not even remember all those features that I have developed, which works extremely well. All I know that those scripts do not look like in the distribution.

Well, if one wants, may rework on my codes and send for consideration to be included in the distribution. Then I will have to clean the code quite a bit.

What I also plan to do is also make it Ajax sensitive integrating it with Xajax, like I said earlier...

What interesting would be also to plug the email-templating system with an existing module like Articles, etc. and have the admin work on those templates of that module. Then the system will find out which template needs to be attached while relay of the massmail.

More will follow ...