Import fails with white screen

[funkenstrahlen]

I installed a fresh wallabag 1.9.1. I then uploaded my Pocket export with about 800 entries by using the import functionality.

At first it looked fine. It started to import the links and refreshed the progress itself. Then suddenly the page went white and nothing happend any more. Reloading the page required me to login again.

There were a lot of links shown with "Click to continue import". Each time I click on any of them the page gets white again and I have to relad + relogin. The import does not work any more.

Any help? How can I debug?

[jessaimaya]

Exactly the same here.

[bertbalcaen]

Same thing for me. Was importing from Instapaper. Culprit for me was a Facebook entry. It just deleted it from the db, so no further details on the root cause. The rest of my 700+ entries imported did import without issues.

Fixed it with some caveman debugging: added a var_dump($entries) in the retrieveUnfetchedEntries() function inc/poche/Database.class.php, around line 307. The first element in the array should be the one causing trouble.

[gdm85]

@tcitworld yes, sorry that issue is unrelated. I am also experiencing many "Click to continue import" saved URLs (actually more than half of the ~600 I imported from pinboard with a Netscape export).

However, the main issue I have is that I cannot really help troubleshooting as I couldn't individuate where logs are saved (if any).

1. does wallabag have a log file? I was expecting to find some output in php5-fpm.log but nothing is going there, even when toggling catch workers output in www.conf
2. is it possible to enable some debug output since there are still some bugs around?

I do not think these "?import" URLs are well-formed, as they do not contain any ID referencing the resource saved in Wallabag, hence the white page; so there are basically two bugs:

• in case of a malformed URL with "?import", it's returning a white page and HTTP status code 200 (which means all good)
• the generated URLs are not well-formed

I haven't yet looked at the 2.0 version, if you think it's better to work on that one instead - please say so

[j0k3r]

@gdm85 It's better to look at the v2 since I don't know if it'll have an other v1.9.x version. Also, import isn't yet ready on v2 (see #1493).

[nicosomb]

This issue affects wallabag v1. This version won't move anymore.