# Latest discourse-akismet breaks Discourse stable (1.3.x)

**URL:** https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100
**Category:** Support
**Tags:** akismet
**Created:** [10 september 2015 om 13:41 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100 "2015-09-10T13:41:51Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![pjv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pjv/32/115994_2.png) [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [10 september 2015 om 13:41 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/1 "2015-09-10T13:41:51Z")

</div>

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).

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [10 september 2015 om 14:41 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/4 "2015-09-10T14:41:20Z")

</div>

Do you have any plugins installed? If so, try disabling them.

Do you see any JavaScript errors when loading the page?

---

<div class="post-metadata">

### Author: ![pjv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pjv/32/115994_2.png) [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [10 september 2015 om 14:43 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/5 "2015-09-10T14:43:12Z")

</div>

> [@zogstrip](#):
>
> Do you see any JavaScript errors when loading the page?

yes:

 ![](https://global.discourse-cdn.com/meta/original/3X/2/7/278e4bfb84a6502f64a3e43ee1629df602bf9ce7.png)

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [10 september 2015 om 14:44 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/6 "2015-09-10T14:44:55Z")

</div>

You must have some plugins installed. I don’t see any “`rewire`” in the vendor file here.

---

<div class="post-metadata">

### Author: ![pjv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pjv/32/115994_2.png) [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [10 september 2015 om 14:48 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/7 "2015-09-10T14:48:33Z")

</div>

> [@zogstrip](#):
>
> 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.

---

<div class="post-metadata">

### Author: ![pjv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pjv/32/115994_2.png) [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [10 september 2015 om 15:01 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/8 "2015-09-10T15:01:40Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [10 september 2015 om 15:27 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/9 "2015-09-10T15:27:11Z")

</div>

Are you sure it’s akismet? It’s enabled here on meta and it works just fine.

---

<div class="post-metadata">

### Author: ![pjv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pjv/32/115994_2.png) [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [10 september 2015 om 15:35 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/10 "2015-09-10T15:35:44Z")

</div>

> [@zogstrip](#):
>
> 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…

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [10 september 2015 om 15:41 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/11 "2015-09-10T15:41:01Z")

</div>

> [@pjv](#):
>
> Would be nice if there was a way to specify a particular revision of a plugin.

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.

---

<div class="post-metadata">

### Author: ![pjv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pjv/32/115994_2.png) [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [10 september 2015 om 16:02 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/12 "2015-09-10T16:02:35Z")

</div>

FWIW, this approach worked:

> [@pjv](#):
>
> Maybe I’ll fork the repo, revert the last commit on my fork and use that URL instead of the official one…

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.

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [10 september 2015 om 17:17 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/13 "2015-09-10T17:17:47Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [11 september 2015 om 00:10 UTC](https://meta.discourse.org/t/latest-discourse-akismet-breaks-discourse-stable-1-3-x/33100/14 "2015-09-11T00:10:58Z")

</div>


