@MikeV Are you referring to your private wiki only or also your public wiki?

Both are indicated in the title. What's the correct way to identify the site(s)?

You won't be able to use pdf rendering on https://ndg.nenawiki.org/wiki/Main_Page (as it's private and rest base only supports public wikis).

https://nenawiki.org/wiki/Main_Page Doesn't appear to have electron enabled (but if you do enable it, you can use pdf rendering). You can also enable Collection (PDF) too.

Thanks. I didn't know that it is not supported on private sites. I was going to test it there before enabling it on the public site.

I still get this error on nenawiki.org:

We have technical problems with the function we use to create PDFs. We unfortunately have to replace it. This affects the styling and features of the books function. For more information and feedback, visit the project page.

    Leave feedbackRead more

When you go to the link indicated, you get the message that I referenced earlier about a new PDF rendering thing:

PDF Rendering has been improved as of 6/4/2019: https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality

@MikeV works for me (i restarted the electron service).

When I go to this page: https://nenawiki.org/wiki/EIDO_%26_IDX_FAQ_(Frequently_Asked_Questions)

and click on "Download as PDF", I get the error

Please note... MediaWiki says they deployed a new renderer on June 4, 2019, only a few days ago.

https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality#Update_on_PDF_rendering,_June_4,_2019

Has Miraheze installed it?

@MikeV even though it says that, if you click download, it will work. That message is for the older infrastructure. We use Electron. And the post is for the newer infrastructure (newer then electron which we haven't installed yet).

Error messages like this confuse, annoy, and discourage many of our users. Can we fix it?

John, does this mean that Miraheze is up-to-date on the PDF rendering changes from MediaWiki on June 4?

@MikeV hi, nope We use "Electron" which predates "Proton". (i.e "proton" is the newer infrastructure) which i plan to upgrade to later.

OK. I don't know the correct protocol or etiquette to follow here. Do I change this task to request installation of Proton or do I abandon this task and start a new one to request Proton? Put another way, what is the best way to get a better PDF rendering capability?

You can change this to requesting the installation of "Proton".

@Paladox What's the status on the Proton upgrade? When will it be done?

I need to install it, then replace it in RESTBASE.

Note that proton still uses RESTBASE so private wikis will still not work.

PDF rendering is becoming a critical factor with our users. An update on status would be appreciated. Thanks.

In T4445#84980, @Paladox wrote:

I need to install it, then replace it in RESTBASE.

Note that proton still uses RESTBASE so private wikis will still not work.

@Paladox Status on this?

Update: I would like to install that very soon. I just need to look at the install docs and try to install it.

@Paladox Status?

A few points:

• Electron generates an error message that users believe. It discourages them from continuing to "Download as PDF."
• If you ignore the error, it creates PDFs that cannot be used without editing. For example, it now inserts a block that says "Cookies help us deliver out services. By using our services, you agree to our use of cookies. More Information OK." This message overwrites the PDF material.
• This page indicates that Proton has apparently been successfully deployed as an improvement to electron: https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality

We appreciate any effort to fix the "Download as PDF" function. We hope that changing the priority from High to Normal doesn't result in significant delays in deployment.

Thanks.

Oh, that's the extension it's self (which the new renderer still uses).

The extension has had that message removed (https://github.com/wikimedia/mediawiki-extensions-ElectronPdfService/commit/1f0494a6a8d6e3d6fa2349b7d43d2ee457c45e3b).

Sorry, Paladox. I do not understand your response.

Please go to this page and then click "Download to PDF" from the menu: https://nenawiki.org/wiki/NENA_NG9-1-1_Go-To_Handbook_(Review_Draft)

First, you get an error message. Then the downloaded PDF not acceptable.

Now, if you go to the Widipedia page for PDF, and click "Downlad to PDF", you don't get the error message and you get a good downloaded PDF version of the page.

Can Miraheze make our "Download to PDF" work as well as Wikipedia does?

I tried to install the new pdf renderer but couldn’t get it to work. So will need to work on that again.

And also to point out, I just tried to download a PDF and it worked.

Reception, Please look at it. There's a banner at the top of the screen that doesn't belong: "Cookies help us deliver ou tservices. By using our sevices, you agree to our use of cookies. More information OK".

So there are two problems... Error message and banner.

These two problems do not happen for "Download to PDF" on Wikipedia.

@Paladox is it possible to exempt IPs/services from the cookie warning so that it no longer appears on the generated PDF?

@MikeV I hope I'm understanding correctly, but is your issue only that there's an error message before you click the download button? If that is the case that can be removed by editing https://nenawiki.org/wiki/MediaWiki:ElectronPDFService-warning-message

In T4445#88687, @Reception123 wrote:

@Paladox is it possible to exempt IPs/services from the cookie warning so that it no longer appears on the generated PDF?

@MikeV I hope I'm understanding correctly, but is your issue only that there's an error message before you click the download button? If that is the case that can be removed by editing https://nenawiki.org/wiki/MediaWiki:ElectronPDFService-warning-message

Oh, I've found the answer to my first question. That seems to depend on Upstream task: https://phabricator.wikimedia.org/T193716

Technical comment:

ping @Southparkfan

We've tried blacklisting restbase so that when the service captures the page it ignores CookieWarning but that seems to not be working with REMOTE_ADDR due to Varnish (It works on test1).

@MikeV It seems that we have made it work. Could you please check and confirm that it works as intended for you?

A test of a downloaded PDF now does not show the warning banner. Thank you for fixing this.

In T4445#89202, @MikeV wrote:

A test of a downloaded PDF now does not show the warning banner. Thank you for fixing this.

You're welcome! Do you still need anything else regarding the PDF function?

Two things -

The cookie monster is back.

Clicking "Download as PDF" on our nenawiki.org home page generates a PDF with the attached cookie message.

Has there been any progress enabling PDF rendering on private sites?

In T4445#99117, @MikeV wrote:

Two things -

The cookie monster is back.

Clicking "Download as PDF" on our nenawiki.org home page generates a PDF with the attached cookie message.

Has there been any progress enabling PDF rendering on private sites?

@Paladox

Fixed.

@MikeV Can confirm that the cookie issue is now gone!

Yes. The cookie banner is gone from nenawiki.org. Thanks, Paladox! and Reception.

The other question remains. Has there been any progress enabling PDF rendering on private sites?

MikeV