| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Fix #4137
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Updating twig/twig (v2.12.0 => v2.12.1)
- Updating symfony/mime (v4.3.4 => v4.3.5)
- Updating friendsofsymfony/rest-bundle (2.5.0 => 2.6.0)
- Updating j0k3r/graby-site-config (1.0.91 => 1.0.93)
- Updating monolog/monolog (1.24.0 => 1.25.1)
- Updating simplepie/simplepie (1.5.2 => 1.5.3)
- Updating symfony/http-client-contracts (v1.1.6 => v1.1.7)
- Updating symfony/http-client (v4.3.4 => v4.3.5)
- Updating nette/utils (v3.0.1 => v3.0.2)
- Updating phpstan/phpstan (0.11.17 => 0.11.18)
- Updating zendframework/zend-code (3.3.2 => 3.4.0)
- Updating php-amqplib/php-amqplib (v2.10.0 => v2.10.1)
- Updating beberlei/assert (v3.2.3 => v3.2.6)
- Updating zendframework/zend-diactoros (2.1.3 => 2.1.5)
- Updating sentry/sentry (2.2.1 => 2.2.2)
|
| |
|
| |
|
| |
|
|\
| |
| | |
Add ability to manually define the reading speed
|
| |
| |
| |
| | |
Instead of using a select, let the user decide its own speed.
|
|/
|
|
|
|
|
|
|
| |
- Add missing translations
- Add some tests
- Add `/api/taggingrule/export` API endpoint
- Add baggy theme
- Add error message when importing tagging rules failed
- Also fix all translations (I think we are good now)
|
|\
| |
| | |
Fix migration with prefix table name
|
| |
| |
| |
| |
| | |
The previous URL started to report title as `snippet intertitre` instead of the previous title which contains Google.
It looks like a bug on the website side. Instead of updating the test to match that new title, I prefer to use a more recent url instead.
|
|/
|
|
| |
`mnapoli/piwik-twig-extension` locked Twig to the 1.10 version. The new version is compatible with Twig 2.0
|
|\
| |
| | |
mysql: change collation of tag label
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
utf8mb4_unicode_ci considers that 'caché' is equal to 'cache' which
can lead to attaching incorrect tags to entries. This issue is due to
some unicode normalization done by MySQL.
utf8mb4_bin makes no unicode normalization, letting wallabag to consider
'cache' and 'caché' as two different tags.
We change the collation of the whole table as Doctrine does not support
setting a collation on a column for a specific platform (it tries to
apply utf8mb4_bin even for pgsql and sqlite).
Fixes #3302
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| | |
|
| |
| |
| |
| |
| | |
When using `OR` in a where clause, a composite index can't be used. We should use a `UNION` to take advantages of it.
Instead, create 2 indexes on each hashed urls and make 2 queries to find an url. It'll be faster than the previous solution.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Added index on entry table for given_url field
- Fix tests:
The previous `bit.ly` url redirected to doc.wallabag but that url doesn't exist in the fixtures.
I used our own internal "redirector" to create a redirect to an url which exist in the fixtures.
Also, updating current migration to use the new `WallabagMigration`.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
api/entries: add parameter detail to exclude or include content in response
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
detail=metadata will nullify the content field of entries in order to
make smaller responses.
detail=full keeps the former behavior, it sends the content of entries.
It's the default, for backward compatibility.
Fixes #2817
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| | | |
|
|\ \ \
| |/ /
|/| /
| |/ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Instead of fetching one domain, we use the same method as in site config (to retrieve the matching file) and handle api.example.org, example.org, .org (yes the last one isn’t useful).
If one of these match, we got it and use it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Also, do not run the hashed_url migration into a Doctrine migration
|
| |
| |
| |
| |
| |
| | |
It'll most often be used in addition to the `user_id`.
Also, automatically generate the hash when saving the url.
Switch from `md5` to `sha1`.
|
| |
| |
| |
| |
| |
| | |
- Add migration
- Use md5 instead of sha512 (we don't need security here, just a hash)
- Update tests
|
| |
| |
| |
| | |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|\| |
|
| |
| |
| |
| | |
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The expect parameter enables an application to request the whole entry
or only the id when requesting its deletion.
`expects` defaults to `entry` to prevent any API breakage.
Fixes #3711
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When using the entity manager to retrieve an already stored entry, the
id disapears from $entry after the first delete call. This leads to
testing a nonexistent endpoint (api/entries/.json) during the second
delete call.
This change now creates an entry specifically for the test.
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|