On Wed, Sep 30, 2009 at 4:50 PM, Markus <[email protected]> wrote: > >> Ok, great. I am glad you are sticking with us awhile longer! I was >> afraid we might have lost you to concrete5. :) > > No way. Read the features page of BoltWire and you know why. ;)
Sigh of relief... :) > It's hard to find functionality in concrete5 that is not easily put > together in BoltWire. But of course, some users don't want to put > anything together and don't want to read about concepts – incompatible > attitudes for using BoltWire, much more compatible with concrete5. Agreed. I didn't spend too much time there, because I sensed the same kind of underlying limitations that made me leave drupal and moodle. But it is true, BoltWire is not for everyone. Adding more plugins, and conceivably more features in the core might make it more accessible to others, however, so your point is well taken. > Let's go through some random features I stumbled upon: > > 1) Lock the site for maintenance > What would I do in BoltWire? Set site.auth.view to admins only and > create an appropriate action.block. Yes we could have an action that renamed site.auth.view to site.auth.view.backup and then named site.auth.view.block to site.auth.view--with settings like you suggest. On my site, I've just modified index.php, or perhaps you could modify the skin. You just need ftp access to undo it. On the other hand, you could probably develop a plugin that simply said: echo "Site Under Construction..."; die(); That would do it. But again, how do you turn it off... I'm open to suggestions... > 2) Member management > Does BoltWire need on-site member management? Like displaying a list > of all members with their groups, last login date? Maybe some > functionality to rename or delete users etc. It would be nice to have some people develop a few plugins like this. Need someone to hammer out a set of tools a person could simply install and run with. I would really like to see more users create plugins systems (not code, but actions pages, headers, footers, etc) and maintain them. I'm stretched way too thin to maintain most of our existing 150+ plugins. > 2.1) Activate registered accounts > Some sites need to verify newly registered accounts before allowing > them to access the site. concrete5 has such an option. > I assume in BoltWire you just create a group, say "new_users" and > assign newly registered accounts to it. Then move them to your members > group when they are OK. Actually, you can have the registration page create a page like temp.login.caveman. Then in the header/footer of temp.login, markup that allows you to display their information as you wish, and then click a button to rename as login.caveman. That way they have no privileges until approved. A search function in temp.login, or some site page to list recent pages. Perhaps a button to delete pages you don't want to approve whatever. > 2.2) Email activation > Many sites require users to provide an email address. Usually you have > to open an activation link in an email and then your account is > activated. This is such a common thing it might be a good idea if > BoltWire supported it with a plugin. There is the plugin below, but it needs to be completely rewritten using core functionality. Same idea. Create a temp page, but with a random key. The email message they are sent contains a link to a confirmation page with that key as a $_GET variable. When the page is called with the right key, it gets resaved as a regular login page and they are automatically logged in. I do it all the time on my site. But I keep my site up. Not the plugin... :) http://www.boltwire.com/index.php?p=solutions.email.verify > Here the list ends... Not much I can think of that BoltWire misses. > Unbelievable if one considers the difference in size and (confusing) > complexity to other CMS's. Yes, I'll be honest in that I never cease to be surprized by the power of actions, which allow you to move most of the engine right into the site itself, rather than humongous core code. The advances in flexibility becomes exponential with every new lego you throw in, giving virtually limitless permutations of possibilities. I really see BoltWire is almost a new generation of web engines. If the first generation was software that allowed you to create by hand html websites, the second generation had to be wiki's which allowed you to customize content from within the site. The third generation allows you to create the engine itself in the site. It's that radical a step. > The opposite list, what other CMS's should learn from BoltWire, would > be much easier to compile I assume. > > Still, I wouldn't give grandma a BoltWire site. :) It's always a tight balance between bloat and ease of use. I'd like to see in the future large plugins. For example a full-blown cms system with advanced registration, user/group management tools, email verification, profile features and the like all built in to some site, and installed with one click. Similar major plugins for advanced forums and blogs. Or whatever. But that will take developers willing to plant a stake and invest in some corner of the BoltWire development universe. So far we haven't had too many takers on that. Someone to stick up for the grandma's. Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
