History: Profiles Todos

Regressions

• Site search: can't put text in it? Only affects thenews.css try again after trim update
• $profilerequest: was working in blog but no longer Blog uses that and it works in trunk 2009-02-04 It was probably a problem caused by the plugin editor

Fun stuff

Bugs

• params for modules not working for Bug_Tracker
• The plugin editor, when used on YAML, messes up the YAML formatting by deleting some line breaks I turned off the plugin editor on this site
• File Gallery inclusion is not working workaround: All dependencies must be regrouped

Todo

Technical

• To be able to remove modules (ex.: remove login)
  • Otherwise, login module should be removed from bare-bones install, in favor of site header login box
  • Perhaps bare-bones install should be a profile which is added via SVN and bundled in install? (because Internet connection is needed to use other profiles)
  • Having bare-bones as a profile would facilitate removing a module, or updating parameters on a module.
• When installing a profile, there is a huge list. There is a text box to filter by category, but it would be a lot easier if it was a drop-down menu.
• 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
  • Articles handler so we can add default content (later because it's not trivial)
  • RSS handler so we can pre-package TikiWikis with RSS feeds to various sites
  • Forums handler so we can avoid this extra step (later because it's not trivial)
• 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) Now possible to replace or append to wiki pages
• 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

• Migrate / update all relevant profile related content on doc:profiles dev:profile manager tw:TikiProfilesDev
• Work on Profile_Ideas

Nice to have

• In installer, when no Internet connection, tell people they could have profiles if they were connected
• Order in profiles page: "filter" should be below "list"
• 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 This was done, worked and is now broken, so now in bugs instead of wishlist
  • 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, so we already know what has been loaded.
• Report/diff on my configuration vs a certain profile (only for preferences)
  • This could help with Troubleshooting because people could report what they have changed compared to the standard bare-bones install.
• something on this site that verifies whether a profile works or not?
  • Like a batch test all profiles?
    • Do-able but not a priority
• 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
• 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
• Something to help editors detect if there is a problem with the current YAML syntax, ex.: syntax highlighter. Do browser-based YAML editors exist?
• Maybe a profile creator with a bunch of little predefined actions. Like Automator do in Mac OS X. All done without the knowledge of the YAML syntax or even PHP.
• Submit button to send new profiles to the community.

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)
  • Looks like line breaks are back in branches/3.0
• Is there way to "uninstall profile"? I only see "Forget Past Installation" but this doesn't uninstall (for me anyway — Gary).
  • No there is not, but you could create a profile which turns off all the features :-) (ML)
• Should we use plugin aliases to make nicer/cleaner YAML blocks?
  • LP says not yet, because it wouldn't work