1. 17 Mar, 2016 1 commit
  2. 10 Apr, 2015 1 commit
  3. 09 Apr, 2015 1 commit
  4. 06 Feb, 2015 1 commit
  5. 29 Sep, 2014 1 commit
  6. 12 Apr, 2014 1 commit
  7. 05 Jan, 2013 1 commit
  8. 11 Dec, 2012 1 commit
  9. 12 Jan, 2012 1 commit
  10. 10 May, 2011 1 commit
  11. 02 Mar, 2011 1 commit
  12. 16 Mar, 2010 1 commit
  13. 11 Feb, 2010 1 commit
  14. 12 Jan, 2010 1 commit
  15. 02 Dec, 2009 1 commit
  16. 18 Nov, 2009 3 commits
  17. 17 Nov, 2009 1 commit
  18. 07 Jul, 2009 1 commit
  19. 22 Apr, 2009 1 commit
  20. 30 Mar, 2008 1 commit
  21. 24 Mar, 2008 1 commit
  22. 12 Oct, 2007 1 commit
    • nyloth's avatar
      [MOD] prefs and user prefs: $prefs array deployement in php + some small fixes · 86185302
      nyloth authored
      (Preliminary note : This is a deep modification in tikiwiki's prefs code. Please test first and send feedback if you can)
      
       * Now use the $prefs array everywhere (in php files also) instead of global vars. This will :
      
      	- allow to use prefs the same way in smarty and php ($prefs array),
      
      	- simplify all code parts that modifiy a preference, because when a pref is modified in php's $prefs array, it is also up-to-date in smarty $prefs array (everything is passed by reference now). So, no more need to reassign values in smarty each time,
      
      	- avoid duplication of values in memory,
      
      	- reduce risks of errors (e.g. collision in variables names, forget to add one of the "global $prefname", ...)
      
      
       * All user prefs are now retrieved in one query at tiki-setup stage (as site prefs) and also in session vars (when sessions are used). This will :
      
      	- reduce overhead and database queries after the first page
      
      
       * User prefs are now overriding $prefs. This will :
      
      	- simplify the whole usage of $prefs, because only one array is used (no more need, in general, to use tikilib's functions to get user prefs),
      
      	- set some $prefs['site_*'] (listed in the $user_overrider_prefs array of lib/setup/user_prefs.php) for some specific site prefs that needs to be accessed in php (for example when sending mails) and that could have been overrided with the corresponding user pref
      86185302
  23. 07 Oct, 2007 1 commit
    • nyloth's avatar
      [MOD] prefs : some cleaning / factorizing · 9e8d826e
      nyloth authored
        - set the $prefs array in order to use it in php files
        - move tiki-setup_base.php's session code in order to execute it as soon as possible and benefit from prefs already in session vars,
        - remove some useless smarty assignations and calls to tikilib's get_preference() method,
        - group some preferences queries,
        - rewrite tikilib's get_preferences() method to also handle "exact names" (not filters), in order to ask for more than one pref in one query (same as the get_user_preferences() method),
        - new tikilib method _get_values() on which is based get_preferences() and get_user_preferences(). It is used to get values from db, global vars, or defaults depending on where it finds the first value,
        - remove an debug call to print_r related to contributors
      9e8d826e
  24. 31 May, 2007 1 commit
    • nyloth's avatar
      [MOD] absolute URI / login : Determine http and https URLs automatically and... · 3405f3aa
      nyloth authored
      [MOD] absolute URI / login : Determine http and https URLs automatically and remove configuration need for tiki domain and https mode.
      
      This commit affects the way HTTPS and absolute URI are handled in Tiki.
      
      = Not changed =
        * https_mode (boolean, true if we are currently using HTTPS)
        * http_port (configurable in admin panels)
        * https_port (configurable in admin panels)
        * login_url (used in code, but not configurable, as previously)
        * https_login (configurable in admin panels, determine if we should allow HTTPS for login step)
        * https_login_required (same as above, but force an HTTPS login)
      
      Note that 'http_port' and 'https_port' are empty when used if they have the default values (respectively 80 and 443).
      
      = New global and smarty vars to be used everywhere for absolute URLs =
        * base_url (auto-detected in tiki-setup.php, using current protocol and including the directory  path, not configurable)
        * base_url_http (same as base_url but forced to 'http://')
        * base_url_https (same as base_url but forced to 'https://')
      
        ...and to be less used (base_url is built on them):
        * url_scheme ('http' or 'https', depending on which is currently used)
        * url_host (current host)
        * url_port (current port)
        * url_path (current directory path that both begins and ends with a '/')
      
      = Not used anymore =
        * url_prefix
        * http_svrname
        * https_prefix
        * https_domain
        * feature_server_name
        * https
      
      = Obsoleted (Not used in the main code, but keeped to be compatible with other styles templates) =
        * http_login_url (same as login_url)
        * https_login_url (same as login_url)
        * http_prefix (same as url_path)
        * http_domain (same as url_host)
        * tiki_path (same as url_path)
      
      They are now only used in templates/styles/... (Those used in lib/pdflib/pdflib.php are not the  same).
      
      Tikilib::httpScheme() and Tikilib::httpPrefix(), used many times too, have been ugraded to directly use the new global vars, to avoid duplicated code and overhead. They now handle the port used.
      3405f3aa
  25. 03 Apr, 2007 1 commit
  26. 06 Mar, 2007 1 commit
  27. 22 Jan, 2007 1 commit
  28. 22 Dec, 2006 1 commit
  29. 17 Dec, 2006 1 commit
  30. 29 Aug, 2006 1 commit
  31. 18 May, 2005 1 commit
  32. 01 Jan, 2005 1 commit
  33. 15 Oct, 2004 1 commit
  34. 26 Aug, 2004 1 commit
  35. 27 Jun, 2004 1 commit
  36. 09 Jun, 2004 2 commits
  37. 31 Mar, 2004 1 commit