wallabag: v1.9.1: JSON export returns empty file

Issue details

Wallabag v1.9.1 ; JSON export returns empty file. I have ~900 entries with pictures stored.

Environment

  • wallabag version Wallabag v1.9.1
  • wallabag installed Via composer create-project
  • Last wallabag version that did not exhibit the issue (if applicable): no
  • php version: 5.6.17
  • OS: debian 8.0 armhf
  • type of hosting: dedicated
  • storage system MySQL

Steps to reproduce/test case

config -> export json -> empty file

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 25 (9 by maintainers)

Most upvoted comments

Here is my alternative migration script: https://github.com/benediktg/wallabag-migration

Migration script from @benediktg worked a treat, thanks! Using wallabag API instead of SQL import/export makes you benefit from wallabag v2 features (reading time among others) and you have no encoding problems…

Version 1.9.2 is out. Please give it a try.

@benediktg : You’re right. One reason (the one I encountered) for this 0-byte-file was a JSON_ERROR_UTF8 error. It may have several other reason I did not experienced.

I already did so. There only three sql to migrate from 1.9.1 to 2.0