Unable to get the content of shaarli posts

[AmauryCarrade]

When I try to import a link from a Shaarli post, Wallabag answers “nope, [unable to retrieve full-text content]”.

The import does not work will all Shaarli links.

[tcitworld]

Indeed, but this may be because of the fact Shaarli pages aren't w3c compliant.

Moreover, since shaarli pages aren't on a single domain, it's no use creating specific rules for it. You better may consider proposing a PR for shaarli, if sebsauvages wakes himself. ;)

[AmauryCarrade]

Yes, you're right. It's still a bug anyway.

You make exceptions in the code for such websites, so...

13 avril 2014 18:49 "tcitworld" notifications@github.com a écrit:

Indeed, but this may be because of the fact Shaarli pages aren't w3c compliant.

—Reply to this email directly or view it on GitHub.

[tcitworld]

I've edited my comment above. You're a bit right, I want to see what the others think.

[AmauryCarrade]

We can detect Shaarli (there is some specific codes, like :

<link type="text/css" rel="stylesheet" href="inc/shaarli.css?version=<str>" />

).

Send a PR to Shaarli is a good idea; However, the dissemination of such a PR may take a long time (not counting the very long period of acceptance of that said PR).

[tcitworld]

There shouldn't be a specific rule for shaarli. However, we may be able to modify/extend the parser class to get around the bugs shaarli produces.

[nicosomb]

I close this issue. We can't add specific rules for problems like that.