Latest discourse-akismet breaks Discourse stable (1.3.x)
A user, pjv, encountered an issue after upgrading their Discourse instance from 1.3.4 to 1.3.5, resulting in a white screen of death. After investigation, pjv discovered that the discourse-akismet plugin was the cause of the problem. By commenting out the plugin in app.yml and rebuilding, pjv was able to restore their forum.
However, pjv wanted to keep akismet active and found a workaround by forking the repo, reverting the last commit, and using the URL of their fork in app.yml. eviltrout acknowledged the issue and is working on a solution.
The problem was later identified as a backwards compatibility issue with the latest commit to the tagging plugin, which affected the discourse-akismet plugin. eviltrout has reverted the commit, and the latest version of tagging should resolve the issue.
Help; I just upgraded my forum from 1.3.4 to 1.3.5 and it seems to have killed it.
I’m using the docker install.
I tried going to /var/discourse and doing git pull and ./launcher rebuild app and it’s the same. I can see my custom header but underneath that is just white nothing.
Any suggestions on how I can get my forum back online? (I do have daily backups - though I cannot reach the backups interface).
Do you have any plugins installed? If so, try disabling them.
Do you see any JavaScript errors when loading the page?
You must have some plugins installed. I don’t see any “rewire” in the vendor file here.
I do; I have commented out and am rebuilding container now.
Seems to have been the discourse-akismet plugin. When I commented that out of app.yml and rebuilt my forum came back.
@eviltrout : I notice that you pushed a commit 6 days ago that has something to do with “rewiring” and that seems to have broken my forum.
I do want to keep akismet active though: does anyone know if there is a way to pull a specific revision of a plugin via app.yml?
Are you sure it’s akismet? It’s enabled here on meta and it works just fine.
I’m sure that when I comment out discourse-akismet and rebuild then my forum comes back.
My forum is on the stable channel (which right now means Discourse v. 1.3.5). I wonder if the HEAD version of discourse-akismet works with 1.5.x (whatever meta is running?) but not with 1.3.x.
Would be nice if there was a way to specify a particular revision of a plugin. I’m trying to find or figure out a way to do that via a github URL, but so far no luck. Maybe I’ll fork the repo, revert the last commit on my fork and use that URL instead of the official one…
There is a way, I’d just like to solve the core problem and not have to resort to that. I’m going to try and reproduce with the exact set up you have later today.
FWIW, this approach worked:
I forked and just reverted the most recent commit and then used the URL for my fork in app.yml and now I am on 1.3.5 with discourse-akismet active.
@eviltrout if you could drop a note in here when the official repo again works with stable Discourse I’d be grateful so I can move back.
Thanks to @zogstrip for taking the time to shove me in the right direction to getting back online quickly.
It looks like the latest commit to the tagging plugin wasn’t backwards compatible. I’ve reverted it and now if you install the latest version of tagging your site should work.
