thanks!
Hello all. I messed up my upgrade from 2.3.8 to the current version: I neglected to export my entries before attempting the upgrade. Of course the upgrade got borked and now I am left with just a list of URLs. Is there any easier way to import them into a fresh install without entering one by one?
Hi, for the 2.4.0 release the release doc says “Don't forget to run the command php bin/console --env=prod wallabag:generate-hashed-urls after upgrading to 2.4.0.”. Can we launch this command several times or can this do any harm? (context: a yunohost package for which the upgrade script can be called several times)
Yes it doesn’t matter. But wait for 2.4.1 which optimize the way we retrieve url for which we have to generate hashes
Thanks j0k3r
When is 2.4.1 expected to land?
1 reply
Works perfectly well, update ran like a charm. No issues found so far.
Thank you!
At this point I'm contemplating just restoring my db files from backup and trying the upgrade again. This is for the dockerized version using mariadb.
@wjksiazek: don't know if it can inspire you but here are mine https://box.kdecherf.com/s/sMGfMH8cXwX6Fn4
Hey @niessen, it depends on what you try to achieve. Sharing the same client id/secret between several devices may be easier to setup but in case of leak/hack you will need to reconfigure all of them at once
Hey, 2.4.0 run pretty well on my shared hoster, but upgrade to 2.4.1 won't work.
web46819@ernie:/wb.mdomann.tk$ /opt/plesk/php/7.4/bin/php bin/console cache:clear --env=prod
In ParameterBag.php line 102:
You have requested a non-existent parameter "server_name".
same config that worked in 2.4.0
@micha hey, you need to add a new parameter in your parameter.yml, please see the example and the doc
Thanks, now it works.
Glad to hear that it fixes your issue :)
From here.
is there any way to avoid having to "compile" to install wallabag? I'm using a low end server (128mb ram), and when it tries to create the database scheme in postgresql, kernel kills it (I guess due to low resources: ram not enough). I know 128mb is like nothing at all, but I've managed to install freshrss and shaarli on it, currently running both with no problem, so I'd like to know if there is some sort of workaround for it? Thanks either way
@maguilara: my wallabag setup here consumes ~ 100 MB without any activity according to docker stats. Knowing that wallabag may requires a lot more ram when fetching some pages and you already host other tools on the server, I would recommend more ram unfortunately
@soberrhino: did you run
bin/console cache:clear --env=prod after editing the smtp configuration?
Hi, after updating my version from 2.3.7 to 2.4.1 i got a " Undefined table: 7 ERROR: relation "wallabag_internal_setting" does not exist" even after the db:migrate; could you please help me?
I succeed to fix the migrate, removing a back constraint then restarting the migration process.
