i got a onyx boox note pro and it runs android, so i just use the android app
there's only one last thing on the radar
i see Kdecherf already did a lot to push this last thing in PR #4026. is there anything i can do to support?
I am having "server 500" errors in my android app. I figured I would upgrade to the latest code from git before I came here and asked for help. I have done the install, but I am getting this error: "Column not found: 1054 Unknown column 'w0_.starred_at" I looked in the code, and I found the file app/DoctrineMigrations/Version20170824113337.php . While doing the "make install", I answered "no" to both of the questions in "Step 2 of 4". Those questions were as follows: It appears that your database already exists. Would you like to reset it? (yes/no) [no]: and Seems like your database contains schema. Do you want to reset it? (yes/no) [no]: It seems like there was a database migration step that I didn't perform. Is that correct?
Looking at the GNUmakefile, maybe I should have done "make update" instead of "make install" ?
php bin/console doctrine:migrations:migrate --no-interaction --env=$ENV <<< I see that in ./scripts/update.sh . Is "make update" safe to run on my version from head?
and now the android app works.
If you enabled 2FA via email, try to enable the app method
Don’t terminate the procedure
I think that all will be disabled
Now I started the process of enabling 2FA via TOTP but interrupted it, and now I have disabled 2FA authentication. I tried the same thing yesterday, but in the interface, after the same actions, it showed that I turned on TOTP. Perhaps the problem was because after changing the type of 2FA type from TOTP to email, I needed to log out and log in to my account. Anyway, thanks for the help, @nicosomb!
I'd like to know if fronten-wise there's a lot of change for the upcoming wallabag 2.4.0?
There has been a bit of drama on issue #3118 and I figured most of the work would be on the UI. Adding a bulk-oriented equivalent to the following API shouldn't require too much work https://app.wallabag.it/api/doc#patch--api-entries-{entry}.{_format}
There has been a bit of drama on issue #3118 and I figured most of the work would be on the UI. Adding a bulk-oriented equivalent to the following API shouldn't require too much work https://app.wallabag.it/api/doc#patch--api-entries-{entry}.{_format}
(my point is I don't want to work on wallabag 2.3.x UI if 2.4.0 is going to have major changes)
nicofrand Devs & others ofc
lpn You little shit
The best way to address is it to generate a QR Code per API Client, which would contain
- The server URL
- The client_id
- The client_secret
- The username of the user who generated the API client
This QR code should then be scanned and be readable by the client app (both Android and iOS).
Should I open an issue on the wallabag server repo and on each "official" client app repo? Are there things I should know before opening those tickets?
Thanks for this great application
I use wallabag since severals years with docker
I make a mistake in removing my old wallabag docker image (i thinks it's a 1. version)
I have the wallabag.sqlite file
I have installed the new version of wallabag from dokerhub but i can't access my old stored articles
Are there some tools to migrate the old wallabag.sqlite to new format?
thank's in advance
Thierry
I don't know a tool to export article from the database of the v1 directly
@di72nn as of now, wallabag is still no compatible with PHP 7.4, at least, tests are red: https://travis-ci.org/wallabag/wallabag/jobs/642791099
there is no plan to fix them as of now but we'll have to look into them asap because 7.4 has been released since few weeks now
but fixes will only be applied to the upcoming 2.4.0
(I even think that we must fix them before releasing 2.4.0)
thank's for your advices