1. 17 Nov, 2017 1 commit
  2. 29 Oct, 2017 1 commit
  3. 17 Mar, 2016 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. 13 Dec, 2012 1 commit
  9. 11 Dec, 2012 1 commit
  10. 20 Sep, 2012 1 commit
  11. 14 Apr, 2012 1 commit
  12. 17 Mar, 2012 1 commit
  13. 12 Jan, 2012 1 commit
  14. 30 Sep, 2011 1 commit
  15. 02 Mar, 2011 1 commit
  16. 27 Feb, 2011 1 commit
  17. 08 Mar, 2010 1 commit
    • chealer's avatar
      accesslib: add check_authenticity() for CSRF protection · 55241a7f
      chealer authored
      some accesslib deployment
      ticketlib: Mark ticketlib[1] as deprecated again
      ticketlib: Store tickets in session instead of database
      [FIX] ticketlib: granting a ticket destroys previous one
      [FIX] HTML special chars escaping
      55241a7f
  18. 11 Feb, 2010 2 commits
  19. 09 Feb, 2010 1 commit
  20. 10 Dec, 2009 1 commit
  21. 10 Jul, 2009 1 commit
  22. 27 May, 2009 1 commit
  23. 04 Jul, 2008 1 commit
  24. 25 Jun, 2008 1 commit
    • nyloth's avatar
      [NEW] Dynamic Contents: many enhancements · b552ee16
      nyloth authored
      	* Now fully support the 'Label' - introduced in DB by nkoth - of a bloc (in listing table and when using the smarty function),
      
      	* Use smarty pagination and self_query + find.tpl. This also make this feature AJAX-ready (for column sorting, pagination, find and actions),
      
      	* Change smarty 'rcontent' function to allow no params (neither 'id' nor 'label') that will return a random content not related to a specific bloc,
      
      	* New smarty compiler 'assign_content' that simplifies the use of dynamic contents in templates (for exemple, {assign_content label='my_label' var='test'} will put the data of the dynamic content in the $test variable, available in the smarty template. This is easier than using smarty capture and is useful to display the dynamic content only if the value match some conditions),
      
      	* Use one query instead of two in TikiLib::get_actual_content(),
      
      	* Change dcslib::list_content() to get all data from one query, in order to be able to easily sort on every fields,
      
      	* Change dcslib::get_random_content() to allow no params, which means random with no specific contentId,
      
      	* Display the current value of a dynamic content in the list of content blocs,
      
      	* Remove the 'last versions' column which takes place and is not really useful,
      
      	* To gain more place, move the 'Description' above the Label (in the Label column) as it is more and more done for table listings in tiki,
      
      	* Move the cross icon ('Delete' action) to display it as the last action (as nearly everywhere in tiki)
      b552ee16
  25. 30 Mar, 2008 1 commit
  26. 24 Mar, 2008 1 commit
  27. 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
  28. 23 Jul, 2007 1 commit
  29. 16 Jul, 2007 1 commit
  30. 06 Mar, 2007 1 commit
  31. 12 Feb, 2007 1 commit
  32. 04 Feb, 2007 1 commit
    • mose's avatar
      [MOD] timezones: rollback of last commit about timezones. Idea is good but... · 42ae55ff
      mose authored
      [MOD] timezones: rollback of last commit about timezones. Idea is good but spreading timestamp manipulation makes erratic border effects and makes impossible to display timezone properly with date functions. Please hold commits for some hours, calendar rolledback code will be committed back, as well as some other parts, as there were some nice fixes anyway
      42ae55ff
  33. 03 Feb, 2007 1 commit
    • nyloth's avatar
      [MOD] dates and timezones : Modify every call to php native date / timezone... · fc42b45c
      nyloth authored
      [MOD] dates and timezones : Modify every call to php native date / timezone functions in order to use GMT timezone instead of the server timezone.
      
      Timestamps stored in the database should be stored in GMT timezone, because changing the server (or just its timezone settings) should never have an impact on tikiwiki. This is why every date(), strftime() and mktime() calls are replaced by gmdate(), gmstrftime() and gmmktime(). Those functions will use GMT timestamps and not a timestamp that depends on the server TZ environment variable.
      
      !! Note that everything has not been fully tested yet and that this update lacks of an upgrade path for existing calendars and timezones stored in database with a server timezone.
      fc42b45c
  34. 19 Sep, 2006 1 commit
  35. 18 May, 2005 1 commit
  36. 05 Jan, 2005 1 commit
  37. 01 Jan, 2005 1 commit
  38. 08 Sep, 2004 1 commit
  39. 31 Mar, 2004 1 commit