History: Profiles Todos
Source of version: 106
Copy to clipboard
{maketoc}
Also see ((Admin)) for housekeeping aspects of this site.
!! Super duper important things
* Add staging & approval here (Pascal, Nelson & Marc)
** Currently in testing here
*** --Staging kicks in even on objects not in "Features Profiles"--
**** 6.2 will be just nice for S & A!
**** staging pages like *Personal_Blog_and_Profile_6x should not be in [profiles|profiles list].
*** --Staging copy shouldn't ask for language pick-- fixed
* Swap all uses of images in profiles to use images in the app (Pascal)
** There are plenty of nice images in famfamfam
!!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?]
*get http://profiles.tiki.org/tiki-mindmap.php?page=Feed_aggregator to work
!!Bugs
* --((site_width_3x)) not possible to include wikicontent as a preference (fixed in 3.1?)--
*tiki-lastchanges.php doesn't show things done by profiles
*At ((Personal_Blog_and_Profile|#Modules)), nonums: y is converted to nonums=1 commit done, need to merge to trunk
* --Articles Publish Date & Expiration Date are set to "now" on creation.-- Still need to push to 1 year, instead of 1 month
*[http://profiles.tiki.org/Company_Intranet#Adding_a_file_gallery|File Gallery inclusion is not working] workaround: All dependencies must be regrouped
**Even this seems to be unreliable (or we don't know how to do properly). We'll stop using in Featured profiles.
!!Todo
!!!Technical
*--Add "Only one item per user or IP" (oneUserItem) to ((Tracker Handler)) so ((User_Trackers)) can work. -- done in 5.1
*Profile plugin
**Should add the name of the profile you are just about to install
**Should show offer user input
*Add missing ((handlers)) as we need them in an attempt to support all of Tiki's data types.
** Spreadsheet
** Create Calendar
** FreeTag handler
** Poll handler
*Need wiki-parsed and title for ((module handler)), to be used in ((RSS_Examples)), ((IRC_Chat)) and the menus
*--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.--
* --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 occurred 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 if the re-installed profile is broken, we get blank page instead of helpful error message.
**{QUOTE(replyto="Geoff")}But I decided to re-run the profile, and second time around it did correctly flag that the profile had already been applied BUT when I used the "Forget and Re-apply" it did not ask me to fill in any custom fields and simply applied the defaults - overwriting my previous customisation. I can imagine a new user wanting to re-run because first time round they didn't really understand what the custom fields did - and re-running the whole thing would offer an easy way to get it right second time round.{QUOTE}{QUOTE(replyto="luci")}I think this is fixed in trunk (at least it works for me there) but not in 5.x{QUOTE}
!!!Non technical
* Except for Featured Profiles, remove all profiles that are for 4.x and 5.x so we can focus our energies on 6.x and 7.x
*Improve ((Profiles_in_installer))
*Migrate / update all relevant profile related content on doc:((doc:profiles)) dev:((dev:profile manager)) tw:((tw:TikiProfilesDev))
*Work on ((Profile_Ideas))
*Change all remaining references in the code and documentation. A profile is ''applied'', instead of ''installed''. Install implies that additional code needs to be downloaded.
** well, "installed" can also imply just downloading new information and set that information in place (that information can be PHP code, or "Tiki code", i.e., tiki(wiki) syntax - yaml, etc - to do things on your Tiki installation). So for me (thinking in terms of an end-user), no problems with "installed", but it's ok also if it wants to be changed for "applied" (subtle difference). My 2 cents. (Xavi)
*Profile plugin:: Start using Ex.: in the admin doc, click ((Debug_Mode_Enabled|here to go in debug mode)), click ((Debug_Mode_Disabled|here to leave))
!!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.tiki.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.tiki.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.
!!Needs thinking about for a good solution
*Profile plugin
***Since profile plugin, like all risky plugins, needs to be validated, the message should be better (it's normal on clean install or upgrade)
***How to have safe, pre-signed plugins?
*Files
**To get images via profiles
!!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.tiki.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.
*Perhaps bundled profiles should no longer be in installer.
**They were there because old profiles were on install only
**Would simplify code of installer
**We now have better UI (needs to be even better still) to showcase "featured profiles"
**It forces people to make a choice which they may not be ready to do.
!!Unsolveable or long term
!!!Limitation of system log
*((Profile Rollback))
!!!Limitation of wiki parser
*The plugin editor, when used on YAML, messes up the YAML formatting [tiki-pagehistory.php?page=Small_Business_Web_Presence&diff_style=sidediff&compare=Compare&newver=0&oldver=10|by deleting some line breaks] or by [tiki-pagehistory.php?page=Debug_Mode_Enabled&diff_style=sidediff&compare=Compare&newver=27&oldver=26&tra_lang=ar|changing the parameters] __I turned off the plugin editor on this site__
*Should we use plugin aliases to make nicer/cleaner YAML blocks?
**LP says not yet, because it wouldn't work
!!!Long term
((Doc:Dogfood)) ((Data Channels)) for a real World example
!!!!Profiles offline
**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.
*** Jonny added one in Tiki5
*{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)