Thanks, yes they are now exporting correctly - thank you for checking. It did seem to persist for several days as a problem, and I had encountered this also when I tried exports in June, but perhaps I was just unlucky.

@Reedy Yes I see that. I'm afraid I was trying to brute force solve this problem, but all of the attempts failed. I'll remember to link to file versions in future.

In T299521#8171112, @Ankry wrote:

,snip>
An administrator can try to upload this file locally. This sometimes works as a workaround, but hides the problem.

I'm getting a similar problem with this PDF:

• at Commons it is fine
• at la Wikisource it is 0x0px;
• at en Wikisource it is 0x0px;
• at en Wikipedia it is also 0x0px

Thank you @ashley you are quite right. This is probably best fixed by explanation in the API documentation.

I’m noticing a lot of video content on the current Ukraine conflict pages; is this not causing issues and confusion for users? Would it be worth triaging the size of this problem and the difficulties it is causing users?

Hi @Jdlrobson Please read this task alongside T298515 - the webteam can't fix iOS Safari problem, given the constraints you have on acceptable codecs and standards. However, you can warn users that video and audio does not work and why. Thus this bug report should be closed, as 'won't fix', in favour of warning users as described in T298515.

Thanks @TheDJ that is helpful; so I should understand this prioritisation as just that as yet nobody has picked it up. Thank you @ovasileva therefore for moving this request on into a queue!

Hi @ovasileva would you mind giving your reasons for triaging this as 'low priority'? To me, it ought to be taken as a very serious problem.

I raised a feature request to give iOS users a warning about this; I've also tested in FF and Chrome, which presumably use WebKit, so also don't play WebM media. It can be accessed after download and played on VLC and other media players tho, but this does not include subtitles, which are supllied via the video player used by WM, no doubt because WebM does not support subtitle files natively.

Yes, so I think the position at iOS 15.1 is the same as it has been, ie, that WebM video is not supported. So this should presumably be closed as "won't fix".

Sure, the video is on this page (as screenhotted). The video is on Commons here. The screenshots were on iOS 15.1.

@Aklapper What / where can I find other video formats on Wikimedia to test? I thought you only supported WebM?

Ok, that's clear and understandable given the content on Wikibooks in general, which often is very far from a traditional book, and more like an online freeform content. However it does place a number of Wikibooks ideas I have in difficulty, and some others that I have seen. The use case is typically that some public domain content, often from Wikisource, needs to be lightly or otherwise repurposed. For instance, notation might be added, or simplifications made. This is not appropriate for Wikisource, but ought to be supportable; Wikibooks is right for that purpose from a content perspective, but it is not really viable if ebooks cannot be created.

The export fuction is still not working; it seems related to a missing subdomains that should be mapped / able to 'mirror' en.wikibooks.org

@Candalua Thanks very much; and also for fixing the problem at la.wikipedia :) I also fixed the problem at en.wikibooks.org, however exports there are still not fuctioning properly as per T269956.

@Samwilson Thanks very much, I've contacted the Template author and left a note on it.ws as well as la.ws; hopefully someone will help implement this.

Thanks for looking into this.

Maybe this is a Mac issue? I should have said on I am using Mac OS with these browsers. I've also noticed the WSExport tool is using a different server URL, not sure if that means anything, and I've contacted the person I think authored the export Template.

Here I am logged out, using top link, using FF 90.

Hi there, thank you, yes, you are right that the download links in the sidebar work; it is the export top links (above the title) that do not. In Firefox 90, Chrome, Brave and Safari and I get this error in each case, but only via the custom export tool. So the error must lie there somewhere, rather than the export tool itself.

Ping in case this can be moved on.

The error has changed to "Page not found for: [page name]"

@MSantos Does that mean Latin (and other language) labels should be imported and appearing?

I added a bug report at T269956

I have been trying to make the direct download links work, for example does not seem to work using "en-wikibooks" as the language parameter as suggested above. Should I raise this as a bug report?

I think I managed to get the code and add those files.

Hi there, I have been discussing how to implement ebook support and export on Wikibooks for a while, now see: discussion and prior discussion.

Thanks @Samwilson. I can add those pages, I am not quite understanding where to find them / where to place them.