History: Profiles Todos

• «
• »

            {maketoc}

Also see ((Admin)) for housekeeping aspects of this site. 

!!Super duper important things
*--A Wiki plugin so can call profiles from anywhere--. Ex.: in the admin doc, click ((Debug_Mode_Enabled|here to go in debug mode)), click ((Debug_Mode_Disabled|here to leave))
**Ex.: ~np~ {profile install=blog} ~/np~
***Should add the name of the profile you are just about to install
***Since profile plugin, like all risky plugins, needs to be validated, the message should be better (it's normal on clean install or upgrade)
***If not possible, move last module to bottom left, and maybe just for admins
*Add staging & approval here (Pascal)
*Swap all uses of images in profiles to use images in the app (Pascal)

!!Regressions
* --$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
--[tiki-admin.php?page=plugins&plugin=profile|configure profile plugin alias] with no plugin edit UI--  [http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=rev&revision=17702|done?]

!!Bugs
*tiki-lastchanges.php doesn't show things done by profiles
*--((Test_All_Features)) -> on Test_All_Modules, all modules require validation even if there are not risky-- seems ok now
* --Articles Publish Date & Expiration Date are set to "now" on creation.-- Still need to push to 1 year, instead of 1 month
*--params for modules not working for ((Bug_Tracker))--
*The plugin editor, when used on YAML, [tiki-pagehistory.php?page=Small_Business_Web_Presence&diff_style=sidediff&compare=Compare&newver=0&oldver=10|messes up the YAML formatting by deleting some line breaks]  __I turned off the plugin editor on this site, need to test again with next svn up__
**[http://profiles.tikiwiki.org/tiki-pagehistory.php?page=Powered_by&diff_style=sidediff&compare=Compare&newver=0&oldver=10&tra_lang=ar|this change] caused that this mini-profile was breaking Company_Intranet "An error occured during the profile validation. This profile cannot be installed. Message: Unknown objects are referenced: profiles.tikiwiki.org/Powered_by#Powered_by"
*[http://profiles.tikiwiki.org/Company_Intranet#Adding_a_file_gallery|File Gallery inclusion is not working]  workaround: All dependencies must be regrouped

!!Todo

!!!Dogfood
((Doc:Dogfood)) ((Data Channels)) for a real World example

!!!Technical
*Need wiki-parsed and title for ((module handler)), to be used in ((RSS_Examples)), ((IRC_Chat)) and the menus
*{QUOTE(replyto=Sylvie)}Is there a way to use local profiles, profiles that I write on my local ( I can not have httprequest working on my local since my last system upgrade - it is why I am looking for alternative solution {QUOTE}
*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 a ((Barebones_Profiles)) 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.-- Done see: ((Instructions))
**--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--
** --RSS handler so we can pre-package TikiWikis with RSS feeds to various sites--
** --Forums handler so we can avoid this extra step--
** Poll handler
** FreeTag handler
** Create Calendar
* --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--
**Reinstall is possible in one step (good), but it doesn't provide the profile validation, so it the re-installed profile is broken, we get blank page instead of helpful error message.

 
!!!Non technical
*((Profiles_in_30_installer)) <- ~~#FF0000:urgent~~
*Migrate / update all relevant profile related content on doc:((doc:profiles)) dev:((dev:profile manager)) tw:((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 ((dev: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?
***Would be nice to run at save page time on profiles.tikiwiki.org
***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__
*{TAG(tag=>strike)}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{TAG}
*Something to help editors detect if there is a problem with the current YAML syntax, ex.: [http://dev.tikiwiki.org/wish2325|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 instructions/motivators to share new profiles with 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? ([http://profiles.tikiwiki.org/tiki-pagehistory.php?page=Contact_us&compare=1&oldver=5&newver=8&diff_style=sidediff|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)
**And now, when you forget, it's to re-install.
*Should we use plugin aliases to make nicer/cleaner YAML blocks?
**LP says not yet, because it wouldn't work