Quote:

People that want to complain typically want to be anonymous.

People that love something don't normally post.

Would it be possible to make the frameworks into a "module"?

I know, it's fundamentally different from what a module really is. But if it could be treated like one by users it would really help simplify things again for the average XOOPS user. Install it like a module. Check versions like a module. Upgrade it like a module. Make changes to it like a module.

It would be a module that other modules use.

And then do the same thing for the editors?

Your forum avatar is soooooo appropriate considering your goal!

I'm looking forward to logging into the XOOPS site for a lunchtime theme fix over the next month!

Interesting line of thought here. Waaaay over my head but it looks promising.

Thanks for exploring this and looking for a way to pass on to the rest of us. By you doing it, the devs can focus on the next update and learn from your experimentation. Much appreciated!

Very nice. I'd be one happy camper if this script was Xoopsified. I'm glad people are looking into it!

Regarding email name for login purposes:

1) Many sites use email address for login.
2) Many users are members of many sites and may need to use different logins on each site due to their preferred one being taken already.
3) Email address are unique.
4) You are much more likely to remember your email address than a username if you have several.

What I'm asking is for the login process to be changed to check username and/or email address and match either of them against the password for the account? If the name entered is in the username table and the password matches, grant access. If the email address and the password for that user with that email address match, grant access.

It wouldn't be too difficult to hack in I would imagine. But it would be a really nice core feature. It gives people an option and more it is progressive.

Is it a security risk? I'm not familiar with the core coding so maybe this isn't a simple change?

Implemented or not, I'd like to encourage discussion and try to get more people to talk about possible features or changes. If no one knows what people want, they won't ever be implemented....

Quote:
I know. That's what my example there clearly says.

What I was getting at was creating one place to make cosmetic changes. Right now to customize the text on a site, you need to go into module admin, then block admin, various general settings for other names, edit a php file and adjust language files if needed. There are a lot of places to rename things.

You and I know where to make those adjustments without thinking twice. New users on the other hand have a bewildering array of options -- some of which are very non-intuitive -- that are spread out all over.

I don't know the best approach, but I am more than willing to give some suggestions. I'm hoping that people smarter than me can then refine and implement them if they make sense. I don't completely agree with ozp11's statements or reasons for wanting change, but they are a good starting point for a discussion.

That all said, what would work better than the existing format and the suggestions posted here? Let's brainstorm.

Your suggestions are good but not totally applicable to all the sites that can be created with Xoops.

I'd like to see more options added to help customize the appearance of sites. Instead of having to edit a file to change the names, it would be super duper nice to be able to edit them from within Xoops. Maybe something along the lines of this:



I'd like email address to be added as an OPTION to login so users can use their username -OR- email. This allows backwards compatibility as well as a lot less typing for those that are stuck with 20+ character email addresses. It's a whole lot easier for me to type Speed than it is xxxxxx.xxxxx@xxxxx.xxxxxxx.xxx.... Making XOOPS recognize both as valid would be ideal and it could be set as either/or/both in the admin section.

As far as Drupal (Mambo, whatever) popularity rising while XOOPS is falling or remaining constant, it's all about buzz and the latest new toy. Most people try the latest CMS that is being talked about and don't shop around to see whether another one would better fit their needs. I'm sure once the next major release of XOOPS hits the net, there will be a spike in XOOPS installs again. I'm not really interested in popularity contests. I want a solid, secure CMS with a strong dev team and good support. I've found it.

Quote:

Not sure the best way to do this for you. I'd probably do a standard html page and wrap it into Xoops.

Quote:

Not sure. I moved to CBB years ago.

Quote:

Importing users is a matter of copying the data into new tables. That's how I switched from phpbb to NewBB (which is now CBB). It's tedious but definitely doable.

If I recall, my only problem here was that I had messages that were getting truncated due to length. And the BB codes didn't match up correctly at that time. This was a while back though so your mileage may vary.

Quote:

Several calendar modules exit and I think at least one does scheduling. I don't use one so I'm not sure what would suit you best or if any would suit your particular needs.

Quote:

I don't need this so I haven't paid close attention to it (and will be politely corrected if wrong), but this is one of the things I've seen many ask for but XOOPS doesn't do well. There IS a newsletter functionality in Xoops. I think it had a limit on the number of people it could send to reliably. Do some forum searches on this feature.

Quote:

Available in SmartSection (I think they call it SEO) and I know that short urls have been implemented in a variety of fashions for XOOPS over time. Forum search!

Quote:

phppp is doing a great job of integrating user blogging into Xoops. Do a search on recent module releases (within the last few weeks for the latest update).

Quote:

Sort of. This was added to XOOPS 2.2x. I'd recommend sticking with 2.0.15 since it is the most current code (despite it's numbering). 2.2x works well for many. I ran it for quite a while. But not all modules will work with it. Since you have a wide list of needs, it's safest to stick with the best supported version of Xoops.

Quote:

And in that case, XOOPS should be a joy to work with. I couldn't code my way out of a Hello World contest, but I feel semi-comfortable hacking XOOPS and modifying templates or themes.

Good luck! Hope to see you around again soon.

See the following thread for the solution.

https://xoops.org/modules/newbb/viewtopic.php?topic_id=54266&forum=28&post_id=240418#forumpost240418