Avis de Utilisateur ou utilisatrice 18161541 de Firefox
Noté 5 sur 5
par Utilisateur ou utilisatrice 18161541 de Firefox, il y a 2 ans35 notes
- Noté 5 sur 5par Utilisateur ou utilisatrice 15304775 de Firefox, il y a 5 mois
- Noté 5 sur 5par Orich, il y a 7 moisBeen great so far. There is an error I'm getting for one site though. I see I new version is being worked on, so I can hardly complain. Thanks so much!
TypeError: can't access property "textContent", lCat.querySelector(...) is nullRéponse du développeur
mis en ligne : il y a 6 moisThis is a known issue with that particular website, which I have a fix pending for. In the meantime, the workaround is to simply log out of that website before downloading the story, as this issue affects only logged-in users. - Noté 5 sur 5par Utilisateur ou utilisatrice 18842787 de Firefox, il y a un an
- Noté 2 sur 5par lwtgoIdens, il y a 2 ans
- Noté 5 sur 5par Stacey2148, il y a 2 ans
- Noté 5 sur 5par Utilisateur ou utilisatrice 13385738 de Firefox, il y a 2 ans
- Noté 5 sur 5par Utilisateur ou utilisatrice 18387325 de Firefox, il y a 2 ans
- Noté 2 sur 5par Utilisateur ou utilisatrice 16383947 de Firefox, il y a 2 ansI tried to download something, everything went fine until it stuck on saving file for 6 minutes until it decided to time out and yes I sent a message to the support, nobody answered
Réponse du développeur
mis en ligne : il y a 2 ansPlease contact me via www.ficlab.com/contact for assistance. I answer every single support request received via that form, usually the same day.
If you did not receive a reply to your original message, then this most likely means there was a typo in the email address you provided, and my reply to you bounced as a result - this is the most common reason for my being unable to contact a user.
Regarding your specific problem - that is the result of a bug in Firefox that occasionally causes problems with the download API. Fully restarting your browser (or rebooting your computer) will resolve it. - Noté 5 sur 5par Utilisateur ou utilisatrice 18288255 de Firefox, il y a 2 ans
- Noté 5 sur 5par Laiz325, il y a 2 ans
- Noté 5 sur 5par club fans de la abuela, il y a 2 ans
- Noté 5 sur 5par thekev69, il y a 2 ans
- Noté 4 sur 5par Tin, il y a 2 ans
- Noté 4 sur 5par Bhargav Ram, il y a 2 ansi just found out that the latest update removed Wattpad as one of the sites where download is not possible from now on. Will in the future is there any chance for FicLab to get it back in the future versions?
Réponse du développeur
mis en ligne : il y a 2 ansSupport for Wattpad was removed in v1.0.102 while I work through some legal headaches.
At this point, I'm unsure whether support for it will return in the future. That will depend on whether I can negotiate a solution with Wattpad that resolves their concern; the call is ultimately theirs to make. - Noté 4 sur 5par Erica, il y a 3 ans
- Noté 3 sur 5par Mich, il y a 3 ans
- Noté 5 sur 5par 嘎嘎嘎嘎, il y a 3 ans
- Noté 4 sur 5par Utilisateur ou utilisatrice 13454845 de Firefox, il y a 3 ansThis has really helped me out since I could no longer download stories from one of my favorite sites with the other program I used.
I will admit there are a few more features I would like to see added. Such as a wider selection of fonts to be able to choose, to be able to choose to display the stories as a full width page instead of the more centered look it has now and the ability to change the line spacing. As it is now it can be a little hard to read. Even being able to change it to 1.15 or 1.5 would be a big improvement.
I also used to use a program with a nice feature that broke the story up into chapters and created a folder to hold the story. It started with an index and each chapter was it's own smaller file. It was a bit easier on the cpu and browser.
Edit- I just discovered that this extension seems to have trouble downloading large stories. I went to download one with over 2 million words and the 1st time there was an error. The second time it crashed Firefox.Réponse du développeur
mis en ligne : il y a 3 ansThanks - those are some good suggestions :-).
Regarding the 2m word story - it should be able to cope with that, and on testing can usually manage things longer than that. Could you please contact me via https://www.ficlab.com/contact and provide the story URL, so that I can investigate further. - Noté 5 sur 5par Antag, il y a 4 ansIt's been truly fantastic, but with today's (Oct 2, 2022) update, it now returns the following error: 'Render (docx): Remote render failed: Websocket communication error'. It says it for each download option, and clearing my cookies/cache didn't fix the issue. Any guidance would be appreciated. (EDIT Oct 3: It's no longer an issue! Updating rating for 4 -> 5 stars)
Réponse du développeur
mis en ligne : il y a 4 ansSome formats (docx, mobi, azw3 & pdf) are rendered remotely. The error you saw was due to some server downtime on that day - FicLab was complaining about being unable to contact the rendering server.
I normally post on Twitter (@ficlabapp) in advance of any planned downtime that may affect FicLab users. - Noté 5 sur 5par moonpoolart, il y a 4 ans
- Noté 5 sur 5par lilce1992, il y a 4 ans
- Noté 5 sur 5par Utilisateur ou utilisatrice 17283937 de Firefox, il y a 4 ans