| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
UT: fix formatting issue when the current day has a single digit
|
| |/ |
|
| |\
| |
| | |
API postLink: change relative path to absolute path
|
| | | |
|
| |\ \
| | |
| | | |
Remove unnecessary escape of referer
|
| | | |
| | |
| | |
| | | |
Fixes #1611
|
| |\ \ \
| |/ /
|/| | |
Fix compatiliby issue on login with PHP 7.1
|
| | | |
| | |
| | |
| | | |
session_set_cookie_params does not return any value in PHP 7.1
|
| |\| |
| | |
| | | |
Raise 404 error instead of 500 if permalink access is denied
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Include php-simplexml in Docker image
|
| |/ / /
| | |
| | |
| | | |
Composer 2.0 is now blocking everything if requirements are not met
|
| |\| | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Reduced additional processing time per links from ~40ms to ~5ms
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This changes creates a new form in addlink page allowing to create
multiple bookmarks at once more easily. It focuses on re-using as much
existing code and template component as possible.
These changes includes:
- a new form in addlink (hidden behind a button by default),
containing a text area for URL, and tags/private status to apply to
created links
- this form displays a new template called editlink.batch, itself
including editlink template multiple times
- User interation in this new templates are handle by a new JS script
(shaare-batch.js) making AJAX requests, and therefore does not need page
reloading
- ManageShaareController has been split into 3 distinct controllers:
+ ShaareAdd: displays addlink template
+ ShaareManage: various operation applied on existing shaares
(change visibility, pin, deletion, etc.)
+ ShaarePublish: handles creation/edit forms and saving Shaare's
form
- Updated translations
Fixes #137
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Heavy refactoring of DailyController
- Add a banner like in tag cloud to display monthly and weekly links
- Translations: t() now supports variables with optional first letter
uppercase
Fixes #160
|
| |/ / |
|
| |\ \
| | |
| | | |
Feature: Share private bookmarks using a URL containing a private key
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Add a share link next to « Permalink » in linklist (using share icon
from fork awesome)
- This link generates a private key associated to the bookmark
- Accessing the bookmark while logged out with the proper key will
display it
Fixes #475
|
| |\ \
| | |
| | | |
Feature: add a Server administration page
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It contains mostly read only information about the current Shaarli instance,
PHP version, extensions, file and folder permissions, etc.
Also action buttons to clear the cache or sync thumbnails.
Part of the content of this page is also displayed on the install page,
to check server requirement before installing Shaarli config file.
Fixes #40
Fixes #185
|
| |\ \ \ |
|
| | | | |
| | | |
| | | | |
just replace "*/ ?>" and "<?php /*" with '' and "Trim" output whatever is EOF will trimmed out.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
i was getting error
```
An error occurred while parsing JSON configuration 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.
```
after debug i found
```php
$data = str_replace(self::getPhpHeaders(), '', $data);
$data = str_replace(self::getPhpSuffix(), '', $data);
```
doesn't removing php header and php suffix
cause of this issue was PHP_EOL represents the endline character for the current system. if my ```config.json.php``` was encoded with unix ( LF ) and php running on windows windows encoding ( CR LF ) is not same as unix encoding ( LF ) so ```str_replace``` doesn't replace strin then it causes issue.
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | | |
Fixes #1122
|
| | |/ /
| | |
| | |
| | | |
netscape-bookmark-parser)
|
| |\ \ \
| | | |
| | | | |
Fix: nginx - add rule to disable url-rewriting for the docs
|
| | |/ /
| | |
| | |
| | | |
Related to #1603
|
| |\ \ \
| |/ /
|/| | |
Dislay an error if an exception occurs in the error handler
|
| |/ /
| |
| |
| | |
Related to #1598
|
| |\ \
| | |
| | | |
Asynchronous retrieval of bookmark's thumbnails
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
This feature is based general.enable_async_metadata setting and works with existing metadata.js file.
The script is compatible with any template:
- the thumbnail div bloc must have attribute
- the bookmark bloc must have attribute with the bookmark ID as value
Fixes #1564
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
- Use dedicated function to download headers to avoid apply multiple regexps on headers
- Also try to extract title from meta tags
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- There is a new standalone script (metadata.js) which requests
a new controller to get bookmark metadata and fill the form async
- This feature is enabled with the new setting: general.enable_async_metadata
(enabled by default)
- general.retrieve_description is now enabled by default
- A small rotating loader animation has a been added to bookmark inputs
when metadata is being retrieved (default template)
- Custom JS htmlentities has been removed and mathiasbynens/he
library is used instead
Fixes #1563
|
| |\ \ \ |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \ |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
How it works:
1. when a fulltext search is made, Shaarli looks for the first
occurence position of every term matching the search. No change here,
but we store these positions in an array, in Bookmark's additionalContent.
2. when formatting bookmarks (through BookmarkFormatter
implementation):
1. first we insert specific tokens at every search result positions
2. we format the content (escape HTML, apply markdown, etc.)
3. as a last step, we replace our token with displayable span
elements
Cons: this tightens coupling between search filters and formatters
Pros: it was absolutely necessary not to perform the
search twice. this solution has close to no impact on performances.
Fixes #205
|
| |\ \ \
| | | |
| | | | |
Improve Manage tags page
|
| |/ / /
| | |
| | |
| | | |
Fixes #1125
|
| |\ \ \ |
|
