Regressions
$profilerequest: was working in blog but no longer
Bugs
Todo
Technical
- Part of the profile should be a post-installation message, which could be in some cases a link.
- For example, a wiki page (which I presumably just created), with the next steps to follow. This will help when handlers are not yet created.
- Add missing handlers as we need them in an attempt to support all of TikiWiki's data types.
-
Add Blog handler
- RSS handler so we can pre-package TikiWikis with RSS feeds to various sites
-
Profile list has no pagination so it only shows first 25 results
- If a wiki page exists, profile should provide a meaningful error message (instead of Handler failure: Tiki_Profile_InstallHandler_WikiPage) or just replace it (keeping version history of course)
- perhaps this is the same thing as above, but when loading a profile on their site the user just clicks on a broken profile and won't get any clues about what is or isn't happening (being nothing) and why.
- After a "forget past installation" or "An error occured during the profile validation. This profile cannot be installed.", there should be a button right there to attempt an installation
- Set up InterTiki on this site
Non technical
Nice to have
- Use TRIM to deploy profile demo sites
- "Save current configuration as a profile" (not sure if cost/benefit is there)
- The possibility to ask for data which is to be used as variables in the profile (Something interactive)
- Ex.: ask the person for a username and the wizard-like thingy uses this information to put them in the Admins group.
- The Wizard asks the name of the blog
- The Wizard asks if you want A or B. This would permit simple variants to a profile without forking it.
- A list/log of loaded profiles locally in the Profiles Admin page.
- something on this site that verifies whether a profile works or not?
Once you have installed a profile you can't install again (even if profile has improved and you may have deleted the stuff created by the profile). Maybe an override option would be good. Done
Multiple YAML sections per page, to facilitate readability Done
- To be able to remove modules (ex.: remove login)
Additional settings for groups, like
- Group Homepage
- Users Information Tracker (should be variables of newly created groups, needed for User_Trackers)
- Users Information Tracker Fields (should be variables of newly created groups)
- User can assign to the group himself
Questions
- In tiki-admin.php?page=profiles, should the profile field be a drop-down?
- I don't think so. It's a search field for filter the list. The drop down would contain too many items to be usable after a short period of time.
- Should the plugins support line breaks to increase readability? (example)