Jump to content

Topic on Extension talk:GoogleCustomWikiSearch/Flow

Not working with 1.35?

11
Summary by Tosfos

At any rate, 1.35 is no longer supported.

Kghbln (talkcontribs)

Special page "GoogleCustomWikiSearch" fails silently. Reported with task T274708

X-Savitar (talkcontribs)
Аргскригициониец (talkcontribs)

Also not working with 1.36.

Dachy (talkcontribs)

Same for 1.36

X-Savitar (talkcontribs)

@Аргскригициониец & @Dachy, are you using the master version of the extension or the release that matches the running install of MediaWiki core?

Per the compatibility policy, "Follows the MediaWiki version lifecycle. Master is not backward compatible.".


Let me know if that solves the problems for you! Thanks!

Dachy (talkcontribs)
X-Savitar (talkcontribs)

If you're using fit, then you must have the master branch running by default and in that case, you need the master branch of the extension too.


If you are downloading release bundles, the version of the extension should match the version of MediaWiki. Like so: REL1_35

Dachy (talkcontribs)
Dachy (talkcontribs)

I manually replaced it with 1.36 and now it seems to work, because the console prints a different caveat:


Mixed Content: The page at '....' was loaded over HTTPS, but requested an insecure script 'http://www.google.com/cse/cse.js?theme=V2_DEFAULT&language=.....'. This request has been blocked; the content must be served over HTTPS.


I got the point, but where should I edit? I saw this line in the main php file:

document.location.protocol == 'https' ? 'https:' : 'http:'

but my site is indeed at HTTPS now. I edited both options as HTTPS and uploaded it, still not working, like a cache somewhere still keeps the HTTP.

X-Savitar (talkcontribs)

Did you try a hard refresh after performing the edit? JS/CSS assets are cached by the browser, so a hard refresh should clear the cache.

This post was hidden by Dachy (history)