| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
API: add DELETE endpoint
|
| |
| |
| |
| |
| |
| | |
Based on #840
See http://shaarli.github.io/api-documentation/\#links-link-delete
|
|\|
| |
| | |
REST API: implement PUT method
|
| |
| |
| |
| |
| | |
* Related to #609
* Documentation: http://shaarli.github.io/api-documentation/#links-link-put
|
|\ \
| | |
| | | |
History mechanism
|
| | |
| | |
| | |
| | | |
Only read it when it's necessary
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use case: rest API service
* saved by default in data/history
* same format as datastore.php
* traced events:
* save/edit/delete link
* change settings or plugins settings
* rename tag
|
| | | |
|
|\ \ \
| | | |
| | | | |
Change timezone data structure send to the templates
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The goal of this is to be able to adapt the timezone form
in template without hacking the HTML already rendered.
* there are two arrays available:
* `continents` which contains only a list of available continents
* `cities` which contains a list of available timezone cities, associated with their continent
Note: there are two distinct array because RainTPL doesn't support nested loop very well.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It was multiplying a string containing a letter.
Moved function to Utils.php and display a human readable limit size
|
| |_|/
|/| |
| | |
| | | |
Fixes #818
|
|\ \ \
| | | |
| | | | |
REST API: implement POST link service
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | | |
Fix version check branch for UT
|
| | | |
|
|\| |
| |/
|/| |
Use 'dev' version on the master branch
|
| | |
|
| |
| |
| |
| | |
Allowed check branches are now `latest` and `stable`.
|
|\ \
| | |
| | | |
Fixes #304: use atom feed as default
|
| | |
| | |
| | |
| | | |
RSS feed is still available with the setting set to false
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
Error:
An error occurred while parsing configuration JSON file (data/config.json.php): error code #4
➜ Syntax error
Please check your JSON syntax (without PHP comment tags) using a JSON lint tool such as jsonlint.com.
|
|\ \
| |/
|/| |
Link imports are now logged in `data/` folder, and can be debug using…
|
| | |
|
| |
| |
| |
| |
| |
| | |
`dev.debug=true` setting
related to #741 and #681
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Use php-intl extension to display datetimes a bit more nicely, depending on the locale.
What changes:
* the day is no longer displayed
* day number and month are ordered according to the locale
* the timezone is more readable (UTC+1 instead of CET)
|
|
|
|
|
|
| |
- Creates arrays_combination function to cover all cases
- add the underscore separator in the regex
- add `utf8` encoding in addition to `UTF-8`
|
|
|
|
|
|
|
|
|
|
|
| |
Namespaces have been introduced with the REST API, and should be generalized
to the whole codebase to manage object scope and benefit from autoloading.
See:
- https://secure.php.net/manual/en/language.namespaces.php
- http://www.php-fig.org/psr/psr-4/
Signed-off-by: VirtualTam <virtualtam@flibidi.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This setting allows to escape HTML in markdown rendering or not.
The goal behind it is to avoid XSS issue in shared instances.
More info:
* the setting is set to true by default
* it is set to false for anyone who already have the plugin enabled
(avoid breaking existing entries)
* improve the HTML sanitization when the setting is set to false - but don't consider it XSS proof
* mention the setting in the plugin README
|
| |
|
|
|
|
| |
See http://shaarli.github.io/api-documentation/#links-link-get
|
| |
|
|
|
|
|
|
| |
No update regarding the UI or the API for now
Fixes #758
|
|
|
|
| |
Fixes #724
|
|\
| |
| | |
REST API: implement getLinks service
|
| |
| |
| |
| | |
See http://shaarli.github.io/api-documentation/#links-links-collection-get
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Relates to https://github.com/shaarli/Shaarli/pull/731
Added:
- require the presence of the 'Authorization' header
Changed:
- use the HTTP Bearer Token authorization schema
See:
- https://jwt.io/introduction/#how-do-json-web-tokens-work-
- https://tools.ietf.org/html/rfc6750
- http://security.stackexchange.com/q/108662
Signed-off-by: VirtualTam <virtualtam@flibidi.net>
|
|\ \
| | |
| | | |
Theme manager: improvements
|
| | | |
|
| | | |
|
| |/ |
|
| |
| |
| |
| | |
Signed-off-by: VirtualTam <virtualtam@flibidi.net>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/shaarli/Shaarli/issues/737
Added:
- Base64Url utilities
Fixed:
- use URL-safe Base64 encoding/decoding functions
- use byte representations for HMAC digests
- all JWT parts are Base64Url-encoded
See:
- https://en.wikipedia.org/wiki/JSON_Web_Token
- https://tools.ietf.org/html/rfc7519
- https://scotch.io/tutorials/the-anatomy-of-a-json-web-token
- https://jwt.io/introduction/
- https://en.wikipedia.org/wiki/Base64#URL_applications
- https://secure.php.net/manual/en/function.base64-encode.php#103849
Signed-off-by: VirtualTam <virtualtam@flibidi.net>
|