| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
If the database isn't found when checking for the connection it means, we can connect to the server.
The InstallCommand will create the database later.
Also, when checking for the SQLite connection, Doctrine creates the file (so the database). That's why the test is skipped for SQLite.
|
|
|
|
|
|
| |
Checking for the driver isn't enough.
We are now checking if we can etablish a connection to the database before trying to do anything.
By displaying the error from the Exception (in case of error) we hope to reduce issues overload about people getting error with the database
|
| |
|
|
|
|
| |
If user doesn't want to create a new admin (even if it's recommended) the internal config weren't created resulting in error when using the interface.
|
|
|
|
|
| |
When installing a new project with MySQL, if the database doesn't exist before installation will fail because DBAL will try to get the server version by querying it.
And since this query is done using the default database connexion and since the database doesn't exist, DBAL can't connect to the server.
|
|
|
|
| |
Fix #1867: remove download_picture setting and manage show_printlink in material theme
|
|
|
|
| |
Instead of checking that one of the DB driver is installed we retrieve the selected driver (in parameters) and see if the extension exists.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We already faced this problem but we are facing it again.
https://github.com/wallabag/wallabag/commit/d502762598db68ec822078642df8f6a8214202f7
It seems we can drop a database properly using wallabag:install.
The server log keep saying:
ERROR: source database "template1" is being accessed by other users
DETAIL: There is 1 other session using the database.
STATEMENT: CREATE DATABASE "wallabag_test"
Which means, it can't remove the database wallabag_test because one other person is using it.
|
|
|
|
| |
> The variable $requirement does not exist.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Settings page
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
These default configuration value shouldn't be in parameters.yml.
|
|/ |
|
| |
|
|
|
|
| |
symfony-upgrade-fixer fix src/Wallabag/
|
|
|
|
| |
And some little mistakes
|
|
|
|
|
|
| |
For a not-clear reason, I can't properly drop the current database. Even if Doctrine made a special case for that (https://github.com/doctrine/dbal/pull/849).
So instead of trying crazy things to achieve the test, better way is to skip test (too much wasted days ..)
|
|
|
|
|
|
| |
It will slow down the whole test suite (because it'll use doctrine command).
Remove unecessary `KernelTestCase`.
Also rename `AbstractControllerTest` to `WallabagApiTestCase` for consistency.
|
|
|
|
| |
This is not the same message exception from MySQL & SQLite with Postgres.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Ensure that created use during install command will always be unique.
We assume that the install command must be run to initialize a wallabag instance. NEVER to add more user.
Also, use a better way to retrieve the real name of the database and not the one defined in parameters.yml (which isn't the same for test envi because the dbname isn't defined in parameters.yml but directly in config_test.yml)
|
| |
|
| |
|
|
|
|
| |
Will fix #799
|
|
|
|
| |
will fix #1000
|
| |
|
|
|
|
|
|
| |
Also add fixtures for Config
InstallCommand now check if database, schema are here and ask the user what to do (keep or trash & re-create)
|
| |
|
| |
|
| |
|
| |
|
|
Instead of the legacy bin/install here is a symfony command that can initialize wallabag.
There are still work to do on the requirements part (to be sure that wallabag can run like a charm).
I've also added (but commented) the fixtures load part (which will need an extra doctrine package). We'll see that point later.
|