- Apr 09, 2012
-
-
Anika Henke authored
Instead of three stylesheets for 'all', 'screen' and 'print' modes, they are all loaded into a single stylesheet by wrapping all screen styles in a "@media screen {}" and all print styles in a "@media print {}". The 'all' mode is not wrapped in anything. Potential issues with existing CSS: If any of your screen or print CSS files already contain any "@media" syntax, the CSS will probably break. In that case please add any CSS with "@media" in it to the 'all' mode instead! Also, the 'rtl' mode is hereby deprecated. Please just prefix any RTL styles within your normal CSS files with "[dir=rtl]". This also fixes that RTL styles cannot be added for 'all' or 'print' modes.
-
- Mar 22, 2012
-
-
Dominik Eckelmann authored
-
- Mar 21, 2012
-
-
Dominik Eckelmann authored
-
- Feb 07, 2012
-
-
Andreas Gohr authored
This removes the cachekey parameter again and instead follows @michitux's suggestion to trigger an event for the cache usage
-
- Feb 05, 2012
-
-
Dominik Eckelmann authored
-
- Feb 01, 2012
-
-
Andreas Gohr authored
-
Andreas Gohr authored
-
- Jan 24, 2012
-
-
Dominik Eckelmann authored
-
- Jan 18, 2012
-
-
Andreas Gohr authored
-
- Jan 08, 2012
-
-
Dominik Eckelmann authored
-
Dominik Eckelmann authored
-
Dominik Eckelmann authored
-
- Dec 22, 2011
-
-
Dominik Eckelmann authored
-
- Dec 10, 2011
-
-
Tim Roes authored
The score was randomly transfered as string or as integer. This way it will always be transfered as an integer.
-
- Dec 04, 2011
-
-
Anika Henke authored
-
dploeger authored
-
- Dec 01, 2011
-
-
Tim Roes authored
The score was randomly transfered as string or as integer. This way it will always be transfered as an integer.
-
- Nov 29, 2011
-
-
Tim Roes authored
Added the new error codes and categories: --- 212 Not allowed to delete media == 230 Media edit error --- 231 Filename not given --- 232 File is still referenced --- 233 Could not delete file
-
Tim Roes authored
Since there are currently a lot of error coded returning 1, that mean completly different thing, i guess it would be very nice to change this. A client should not be forced to parse the error message, the error code should be enough to explain the error. This change suggests some error codes, that have a hierarchical structure. In the following list the categories begin with = and the error codes actually used with -. = 100 Page errors == 110 Page access errors --- 111 User is not allowed to read the requested page --- 112 User is not allowed to edit the page == 120 Page existance errors --- 121 The requested page does not exist == 130 Page edit errors --- 131 Empty page id --- 132 Empty page content --- 133 Page is locked --- 134 Positive wordblock check = 200 Media errors == 210 Media access errors --- 211 User is not allowed to read media --- 215 User is not allowed to list media == 220 Media existance errors --- 221 The requested media does not exist = 300 Search errors == 310 Argument errors --- 311 The provided value is not a valid timestamp == 320 Search result errors --- 321 No chances in specified timeframe
-
- Nov 28, 2011
-
-
Dominik Eckelmann authored
-
Andreas Gohr authored
For some reason trailing/leading underscores were allowed when uploading files. But the rest of the code (eg. listing or downloading files) never supported this. This patch removes this special case for uploading files to streamline ID cleaning of pages and media files.
-
- Nov 26, 2011
-
-
Tim Roes authored
Without creating an IXR_Base64 object, the file will be encoded as base64, but send as string. The client XML-RPC parser cannot detect that it is meant to be a base64 encoded file.
-
- Oct 30, 2011
-
-
Adrian Lang authored
-
- Oct 27, 2011
-
-
schplurtz le déboulonné authored
-
- Oct 15, 2011
-
-
Christopher Smith authored
-
Andreas Gohr authored
The login wasn't able to modify the session as it was already closed earlier. This patch also executes the correct event when logins via XMLRPC are done.
-
Michael Hamann authored
If the user is already logged in, a 403 is sent instead now.
-
Michael Hamann authored
This is far from perfect but should solve most issues in the recommended configuration where only authorized users have access. Sending proper status codes should be implemented when the API implementation refactoring is done.
-
Anika Henke authored
-
- Sep 13, 2011
-
-
Adrian Lang authored
-
- Sep 06, 2011
-
-
Kate Arzamastseva authored
-
- Sep 04, 2011
-
-
Adrian Lang authored
This reverts commit ba6c070e. This reverts commit 92351008.
-
Adrian Lang authored
-
- Sep 02, 2011
-
-
Kate Arzamastseva authored
-
- Aug 24, 2011
-
-
Kate Arzamastseva authored
-
- Aug 20, 2011
-
-
Kate Arzamastseva authored
-
- Aug 19, 2011
-
-
Kate Arzamastseva authored
-
Andreas Gohr authored
-
- Aug 18, 2011
-
-
Andreas Gohr authored
jquerized
-
Andreas Gohr authored
-