| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
|
|
|
| |
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In fact it's not _just_ a rename.
We are now able to use our own entity with the CraueConfigBundle which allow us to enforce a custom length on string field and avoid error with utf8mb4 on MySQL.
To fix that issue before we were in need to fork CraueConfigBundle to hard apply these length changes.
The recent 2.3.0 release fix that issue. That's why we are in need to rename the table (getting rid of the bundle name from it)
Also updating deps:
- Updating symfony/polyfill-mbstring (v1.11.0 => v1.12.0)
- Updating symfony/polyfill-ctype (v1.11.0 => v1.12.0)
- Updating symfony/polyfill-php70 (v1.11.0 => v1.12.0)
- Updating symfony/polyfill-util (v1.11.0 => v1.12.0)
- Updating symfony/polyfill-php56 (v1.11.0 => v1.12.0)
- Updating symfony/polyfill-intl-icu (v1.11.0 => v1.12.0)
- Updating symfony/polyfill-apcu (v1.11.0 => v1.12.0)
- Updating j0k3r/graby-site-config (1.0.88 => 1.0.89)
- Updating php-http/message (1.7.2 => 1.8.0)
- Updating symfony/polyfill-php73 (v1.11.0 => v1.12.0)
- Updating symfony/http-client (v4.3.2 => v4.3.3)
- Updating symfony/polyfill-php72 (v1.11.0 => v1.12.0)
- Updating symfony/polyfill-intl-idn (v1.11.0 => v1.12.0)
- Updating symfony/mime (v4.3.2 => v4.3.3)
- Updating craue/config-bundle (dev-utf8mb4 46cfd37 => 2.3.0)
- Updating masterminds/html5 (2.6.0 => 2.7.0)
- Updating nette/di (v3.0.0 => v3.0.1)
- Updating symfony/polyfill-iconv (v1.11.0 => v1.12.0)
- Updating wallabag/php-mobi (1.0.1 => 1.1.0)
|
|
|
|
| |
Instead of using a select, let the user decide its own speed.
|
|\ |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
|
|
|
|
|
|
|
|
|
| |
First, the setParameter() were done on the same parameter which in fact
just duplicated the condition in the SQL query (like `where t.label =
'test' and t.label = 'test'`.
Changed the parameter doesn't help because the query was then wrong.
Changing the way to match associated tags for an entry and it worked.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I've added a toggle feature (in internal settings) so that user api creation can be disabled while form registration still can be enabled.
Also, the /api/user endpoint shouldn't require authentication. Even if we check the authentication when sending a GET request, to retrieve current user information.
I've moved all the internal settings definition to config to avoid duplicated place to define them.
I don't know why we didn't did that earlier.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fix #496
|
|
|
|
| |
Fix #668
|
| |
|
|
|
|
|
| |
This will speed up the test suite because it won’t download everything when we add new entry…
Add a custom test with downloading image enabled
|
|
|
|
| |
Because we need wallabag_url to be defined when we’ll insert entries
|
| |
|
|
|
|
|
| |
Tags & Annotations weren’t really well exported.
This is now fixed (+ tests)
|
| |
|
|
|
|
|
|
|
|
| |
- using javibravo/simpleue
- internal config value are now `import_with_redis` & `import_with_rabbit` which are more clear
- if both option are enable rabbit will be choosen
- services imports related to async are now splitted into 2 files: `redis.yml` & `rabbit.yml`
-
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following https://gist.github.com/Ocramius/3121916
Be sure to remove the related entity when removing an entity.
Let say you have Entry -> EntryTag -> Tag.
If you remove the entry:
- before that commit, the EntryTag will stay (at least using SQLite).
- with that commit, the related entity is removed
|
| |
|
|
|
|
| |
Thanks for https://github.com/thomasbachem/php-short-array-syntax-converter
|
|
|
|
| |
Fix #1867: remove download_picture setting and manage show_printlink in material theme
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
v2 – Remove user reference in tag
|
| |
| |
| |
| | |
Fix #1543
|
|/
|
|
| |
Related #1490
|
| |
|
|
|
|
|
|
|
| |
When a new tag is created but not yet persisted, it can be duplicated.
It could happen when multiple rules match the content and at least 2 of them should attach same new tag.
Fix #1528
|