[Device Plugin] Kobo Touch Extended Driver

[NiLuJe]

@JSWolf: Some of @davidfor's betas *may* have been using a higher version number than the latest release. Install it manually to clear things up.

[jhowell]

It is not a problem with calibre. The Index of calibre Plugins is not showing the latest versions for those. Perhaps the daemon that periodically checks for new plugins in down.

[ownedbycats]

Originally Posted by jhowell

Perhaps the daemon that periodically checks for new plugins in down.

Didn't get the new update for KoboTouchExtended either (Calibre 4.18 x64 on Windows 10).

However, I did get the new Job Spy update a few minutes ago.

[droopy]

Originally Posted by jgoguen

After far too long, a new version is finally published. Calibre should offer it in the next couple hours. This fixes problems with spans being added in the wrong place, and an occasional issue where calibre expects to be able to call the logger object directly.

The ancient Chinese sure weren't joking around when they called "may you live in interesting times" a curse!

Originally Posted by NiLuJe

@JSWolf: Some of @davidfor's betas *may* have been using a higher version number than the latest release. Install it manually to clear things up.

I installed a beta version of KTE to fix the span issue (manifesting as weird line breaks and weird changes in text size).
Currently, it's saying that what is installed is 3.2.9, and what's available is 3.2.7.

Joel, what version is your release from yesterday?

How much longer for yesterday's release to be installed over the beta I installed a week ago?

[DNSB]

One possibility is that if you installed the betas, Kepub Output shows version 3.2.10 compared to 3.2.9 for the new "official" version and KoboTouchExtended driver shows 3.2.9 which is the same as the new "official" version. I suspect that this will block the automatic plugin update.

[DNSB]

Originally Posted by droopy

I installed a beta version of KTE to fix the span issue (manifesting as weird line breaks and weird changes in text size).
Currently, it's saying that what is installed is 3.2.9, and what's available is 3.2.7.

Joel, what version is your release from yesterday?

How much longer for yesterday's release to be installed over the beta I installed a week ago?

Forever? The version in the first message also shows a version of 3.2.9. I'd suggest manually downloading and installing the plugin.

[droopy]

Originally Posted by DNSB

Forever? The version in the first message also shows a version of 3.2.9. I'd suggest manually downloading and installing the plugin.

Hi DNSB. thanks for your reply.
Which "first message"?
And what should the version be of the plugin I would me manually installing?

[DNSB]

Originally Posted by droopy

Hi DNSB. thanks for your reply.
Which "first message"?
And what should the version be of the plugin I would me manually installing?

The first message in a plugin thread has the current plugin downloadable. Scroll down to just below version history which is wrapped in a spoiler, click on the KoboTouchExtended.zip file and download it to your computer.

Just in case you haven't installed a plugin from a download before, here's the quick boilerplate instructions.

Once you have the file downloaded, go into calibre => preferences => Change calibre behavior => plugins and then click on Load plugin from file. Browse to the file you downloaded, select it and click Yes on the Installing plugins is a security risk popup. Restart calibre after the install and you should be good to go.

[theducks]

Originally Posted by droopy

Hi DNSB. thanks for your reply.
Which "first message"?
And what should the version be of the plugin I would me manually installing?

'production' version of plugins ( used by Get Plugins) are always (put) in the 1st post of the dedicated threads. Calibre scrapes that for Get Plugins.
Most likely, Calibre thinks you have a higher or current version.
Also, folk running down rev Calibre may not see notices because of dependencies,

[JSWolf]

Originally Posted by NiLuJe

@JSWolf: Some of @davidfor's betas *may* have been using a higher version number than the latest release. Install it manually to clear things up.

I didn't install any of the betas. So I'm wondering why I'm not seeing an update to the new version.

[jhowell]

Originally Posted by DNSB

I suspect that this will block the automatic plugin update.

As far as I know the automatic plugin update is based on the information collected periodically by a separate program that also updates the Index of calibre plugins website. That gets its information from the "Version History:" spoiler in the first post of each plugin thread, which must be formatted exactly the right way. I suspect that the last update to the that post broke the formatting since it sees that latest version as "3.2.7 Released 17 May, 2020".

EDIT: It looks like it was changed from "Version History:" to "Version History".

Edit again: I was wrong it isn't the colon. It looks like the first plugin post is parsed looking for a specific sequence of HTML elements that should result if the proper BBCODE is used to format the Version History section.

Spoiler:

    def _read_version_history_html(self, forum_link):
        br = browser()
        br.set_handle_gzip(True)
        try:
            raw = br.open_novisit(forum_link).read()
            if not raw:
                return None
        except:
            traceback.print_exc()
            return None
        raw = raw.decode('utf-8', errors='replace')
        root = html.fromstring(raw)
        spoiler_nodes = root.xpath('//div[@class="smallfont" and strong="Spoiler"]')
        for spoiler_node in spoiler_nodes:
            try:
                if spoiler_node.getprevious() is None:
                    # This is a spoiler node that has been indented using[INDENT]
                    # Need to go up to parent div, then previous node to get header
                    heading_node = spoiler_node.getparent().getprevious()
                else:
                    # This is a spoiler node after a BR tag from the heading
                    heading_node = spoiler_node.getprevious().getprevious()
                if heading_node is None:
                    continue
                if heading_node.text_content().lower().find('version history') != -1:
                    div_node = spoiler_node.xpath('div')[0]
                    text = html.tostring(div_node, method='html', encoding='unicode')
                    return re.sub(r'<div\s.*?>', '<div>', text)
            except:
                if DEBUG:
                    prints('======= MobileRead Parse Error =======')
                    traceback.print_exc()
                    prints(html.tostring(spoiler_node))
        return None

[JSWolf]

I just had a proper look and Calibre thinks the latest version is 3.2.7.

[DNSB]

Originally Posted by jhowell

As far as I know the automatic plugin update is based on the information collected periodically by a separate program that also updates the Index of calibre plugins website. That gets its information from the "Version History:" spoiler in the first post of each plugin thread, which must be formatted exactly the right way. I suspect that the last update to the that post broke the formatting since it sees that latest version as "3.2.7 Released 17 May, 2020".

The version history spoiler for the KTE driver shows:

Version 3.2.9 - 2020-06-17
Fix issue with the logger object not being callable and the conversion adding stray <br> tags
Version 3.2.7 - 2020-05-16
Fix Windows issues with Unicode strings.
Version 3.2.3 - 2020-05-11
Fix logging issue with non-ASCII characters on Windows

While the Kepub Output version history spoiler shows:

Version 3.2.9 - 2020-06-17
Fix issue with the logger object not being callable and the conversion adding stray <br> tags
Version 3.2.7 - 2020-05-16
Fix Windows issues with Unicode strings.
Version 3.2.3 - 2020-05-11
Fix logging issue with non-ASCII characters on Windows

I had the two beta plugins installed for which calibre showed 3.2.10 and 3.2.9 as the versions. From previous betas, I was under the impression that calibre would not offer a down or same level plugin as an update.

[DNSB]

Originally Posted by JSWolf

I just had a proper look and Calibre thinks the latest version is 3.2.7.

Nothing in the version history spoiler for KTE or Kepub Output looks different from previous versions or the version history for other plugins so you guess is as good as mine as to why it is not being scraped.

I'd suggest a manual install until the issue is cleared up.

[jhowell]

Originally Posted by DNSB

I had the two beta plugins installed for which calibre showed 3.2.10 and 3.2.9 as the versions. From previous betas, I was under the impression that calibre would not offer a down or same level plugin as an update.

True. If you have 3.2.10 it won't offer anything lower.

But in order to do that it has to know which version is available on MobileRead and it is not determining that correctly at the moment.