Please add site https://ruvers.ru; https://fanficus.com

[DEATHAN-SAA]

Hello.
I'm sorry to bother you, but I don't know how to bypass websites with protection. So that it doesn't give errors like this:

Не найден элемент с содержимым на странице https://ruvers.ru/ya-nepravilno-vospital-zlodeya-kak-mne-eto-ispravit/8'. fetchWebPageContent/<@moz-extension://946d8a44-ae5f-4c23-a08f-2648cd8b7149/js/Parser.js:519:23

Provide URL for web page that contains Table of Contents (list of chapters) of a typical story on the site

https://ruvers.ru/ya-nepravilno-vospital-zlodeya-kak-mne-eto-ispravit

Did you try using the Default Parser for the site? If not, why not?

Instructions for using the default parser can be found at https://github.com/dteviot/WebToEpub/wiki/FAQ#how-to-convert-a-new-site-using-the-default-parser

What settings did you use? What didn't work?

• URL of first chapter
  * https://ruvers.ru/ya-nepravilno-vospital-zlodeya-kak-mne-eto-ispravit/5
• CSS selector for element holding content to put into EPUB
  * .inner_text > div:nth-child(1)
• CSS selector for element holding Title of Chapter
• html body.custom_scroll main#app.fade_effect div.block_inner div.chapter_inner div.chapter_text div div.inner_text.not-copy div div

Unfortunately, I don't understand how to create a parser on my own while bypassing the error.

[dteviot]

@DEATHAN-SAA

Please create separate issues for each web site.
(e.g. Remove https://fanficus.com from this issue and create a new issue for https://fanficus.com)
It makes tracking progress much easier for us.
I'd do it myself, but then you'd lose feedback.

[DEATHAN-SAA]

P.S. Sorry for not editing for so long. I did as you said - I removed the information about the second site and made a new Issue for it.