Yes, it's fixed. Thanks

@robi Yes Robi, they use real device.

@girish Thank's Girish... I think this is a big limitation of Wallabag: cannot export highlights to other platforms

Then we can rule this out and it is better reported upstream. Maybe you can create an issue at https://github.com/wallabag/wallabag/issues and if so, please link it here then for context.

@nebulon Not that I could tell, other than there were no error messages in the logs when I tried importing via the app. I could see it was an image problem because of the cli progress.
Oh, and I had o boost both my Wallabag app AND its Redis to 5 or 6GB of ram each to manage 1200 articles. Anything less than 5GB didn't seem to work. Afterwards I've lowered both to under 1GB and it's all good.

@nebulon How do I get this update to be visible? My current version is 2.4.1, but the app store lists that version is 2.5.2, but that doesn't show up when I press Check for Updates.

NM. I found the notice from A YEAR AGO! https://forum.cloudron.io/post/23720

@ctrl Oh.. that wallabag you are using is very old, like 3 years ago and it's also the abandoned package. See https://forum.cloudron.io/topic/1691/wallabag-is-back

If you go to Services -> redis -> restart the redis there. Then try to update the app to atleast package 1.5.0 and let us know how that goes.

So I guess we just wait for a wallabag release then. Generally allowing things to be modified in vendor/ folders is not ideal, as mostly those contain code.

@hillside502 😅 thanks, corrected!

@jk Thanks for the write up! Indeed, the migration is a bit rough because Wallabag had made a 2.3.8 release back in May 2019. Then a 2.4 release came up after 1.5 years but this wasn't "upgrading" cleanly and had many migration issues. In fact, there are still migration issues pending upstream like 5197, 4820, 4979, 4821. We thus decided it's best to start "afresh" because it doesn't seem like the migration issues will be fixed any time soon.

@nebulon FWIW I was able to spin up an instance of the new version and migrate everything over without hiccup today. Fingers crossed that we won't need such a migration for future updates...

I've made another attempt to publish the new version with a fixed start script. Lets see if this mitigates the migration issue.

So we have to wait for the next patch release to fix a few regressions it seems: https://github.com/wallabag/wallabag/milestone/65