After running runJobs.php the job queue was emptied in my test wiki (had 2944 entries, oops!) and the pages showed up on the category page. So that problem is gone.

I have removed the mscatselect extension for additional testing to see if there are no issues with adding categories to a page, and I do have this issue, even without mscatselect. According to here https://www.mediawiki.org/wiki/Topic:T8jd8uxlq4jqb0np the issue maybe with a backlog on the job queue (which I currently have).
Will report back later (or withdraw the bug report here).

Thank you @Reedy for putting in the code changes in Gerrit. As I said before I am new to contributing to open source. Learning along the way, while helping my client.

In T162264#3177837, @Reedy wrote:

In T162264#3177426, @PeterBodifee wrote:

@Reedy Not familiar yet with the process, is there something I can do to update the code on github (see above)? Also note that I had to change it to manifest_version 1 as my wiki on 1.27.1 didn't like version 2.

Well, in that case, you're obviously using the incorrect branch/version of the extension to go with your MediaWiki version. It's generally not expected that random (older or newer) versions of an extension will work with random versions of MediaWiki

REL1_27 doesn't have an extension.json https://github.com/wikimedia/mediawiki-extensions-DiscussionThreading/tree/REL1_27 commit f9cc186

Also the addOnloadHook in the javaScript to select the text to be replaced is obsolete and needs to be replaced with jQuery (and elseif is not proper JS)

@Reedy Not familiar yet with the process, is there something I can do to update the code on github (see above)? Also note that I had to change it to manifest_version 1 as my wiki on 1.27.1 didn't like version 2.

First updated to 1.6.0 (b9da420)

The warnings are caused by not setting $hint on line 34 in DiscussionThreading.class.php with an array value.

Using the WikiEditor extension the icons and drag&drop area are added.

@Krinkle: cool! I suggest you update https://en.wikipedia.org/wiki/Template:Navpop as well (if appropriate) as it is referenced in the documentation.

@Krinkle Agree, and find that also in other extensions the documentation should stay better up to date. Now we as ' mediawiki deployments outside wikipedia' maintainers could certainly contribute, however the mentioned page is protected, so is my only option to provide additional information (e.g. that the manual installation method isn't working since 1.27+ and the resource loader options are specified in MediaWiki:Gadgets-definition) on the talk page?

@Aklapper I wasn't using any custom version importScript. My use of importScript in common.js worked flawlessly in 1.26.2 and not in 1.27.1 (where it caused an error). Not sure if we can conclude if there is no issue in the MediaWiki code. Or I am completely not understanding what I ran into.

@Krinkle I don't see any errors. It was late last night, forgot to clear cache on my browser. I have it working!

@Krinkle Turned out the extension Gadgets was on the server, but not loaded in LocalSettings.php. So added the load statement.
Also corrected MediaWiki:Gadgets-definition per your description, added page MediaWiki:Gadget-Navigation popups and I do now have the Gadgets tab on my preferences, and checked the 'Navigation Popup' . Special pages Gadgets and GadgetUsage exist and work properly. So assuming extension Gadgets is set up properly.

@Krinkle I found navigation popups on Wikipedia at a time when I had no shell access and couldn't install extensions (luckily that has somewhat changed!)
So I copied the content on MediaWiki:Gadget-popups.js and MediaWiki:Gadget-navpop.css (I do have edit right for this namespace) from Wikipedia and used the 'manual installation' as described in section Installation here.
It worked fine on our production MW 1.26.2. Prepping now to upgrade to 1.27.1 on our test environment where I run into the issue as described above. But I have received shell access on our test env so I can now install the Gadget extension.
Will report back.

@Krinkle Not 100% sure if I understood you correctly. I added the page below. Still getting the reference error on importScript.

Opened this issue on Github for SMW: https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/2392

Good question!

I understood the actions above were for us to be able to clone just extension PdfBook from Organic Designs' Github, however the "clone or download" link is at the top-level of their complete Repo including even non-mediawiki code.

Unfortunately

git clone https://github.com/OrganicDesign/extensions/tree/master/MediaWiki/PdfBook

results in

fatal: repository 'https://github.com/OrganicDesign/extensions/tree/master/MediaWiki/PdfBook' not found.

Am I missing something?

YES! Both Safari (Mac) and IE 11 (on Win7) are now working as well for autocomplete.
input type=tree is also good. Case can be closed.

Unfortunately it didn't. Still no autocomplete in Safari and IE. Maybe because the 'offending' line is still in the code (now on line 100)?

Still puzzled why 'importScript' gives me error in my TEST wiki (1.27.1). In my Production wiki (1.26.2) also using PageForms 4.1(22cc121) , I don't see this error. And this is consistent over the various browsers I have. Any pointers where I can post this bug?

This is what "&debug=true" gives me: (Qqqq is the title of the test page with the form failing).

Adding ?debug=true doesn't provide additional information on the console as far as I can see.

Mar 9 and Mar 29 code exhibits same problem in IE 11.0.9600.

This is what I see when I start deleting characters in the field with autocomplete (Editor):

See attached screen capture. Is this what you wanted to see?

Thank you Cindy, the debug statements helped me to see that there were errors made both in the parameter as well as in the value in LocalSettings.php. Have it now working that it will login.
You got to love interpreted code without syntax and type checking...

We finally got the debug information to be logged; this is from a full cycle of mediawiki login (Aanmelden) to the external IdP host and back. The message in the red box we get on the mediawiki login screen reads: "Authentication or authorization failure."
Attached is de MediaWiki debug log file as well as the simplesamlphp log file.
We applied all the suggestions we could find around caching and sessions, but are now stuck. Any help/pointers are appreciated!

Thanks Yaron for your help. The suggested patch works!

I have a suspicion the person who downloaded the code didn't activate(?) it properly. If I look Special:Version, am I supposed to see a something like " 4.1. (xxxxxx) Mar 8, 2017 " in the version column. I only see "4.1."

I had the latest version of Page Forms downloaded as instructed. I also had verified that the code changes are indeed on our test site but I see no change in behaviour. The site is accessible from the internet but username/password protected. I can grant you access, email me at pbodifee@bauhaus.nl. I will also point you to my specific test where you are free to play around. Thanks for the help!

Thanks Yoran, but I need some help in instructing my technical application support person to download/install this fix, so I can test it on our test wiki. I am a n00b to this part of the game :-)

I am wondering how we can map a SAML attribute (Group) we get from ADFS to a Mediawiki group. Is this possible with this extension, if yes, how?