# El sitio no se está compilando después de la beta 5 de 2.3.0

**URL:** https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762
**Category:** Support
**Created:** [16 Marzo, 2019 03:51 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762 "2019-03-16T03:51:25Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![Destry\_Hunt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/destry_hunt/32/132757_2.png) [@Destry\_Hunt](https://meta.discourse.org/u/Destry_Hunt)
#### Post date: [16 Marzo, 2019 03:51 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/1 "2019-03-16T03:51:25Z")

</div>

I opened an issue earlier, but unfortunately it was closed before it was resolved:

[https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5-update-unless-i-disable-discourse-solved-plugin/111737/3](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5-update-unless-i-disable-discourse-solved-plugin/111737/3)

The issue is that the new Discourse version does not resolve unless Discourse-solved plugin is disabled. I found the error:

StandardError (Attempting to access a non preloaded custom field, this is disallowed to prevent N+1 queries.)  
/var/www/discourse/app/models/concerns/has\_custom\_fields.rb:158:in `’

Here is the link to the rest of the error log (let me know if I am endangering my site by showing this…I could not find anything that looked sensitive, but then again I am not a hacker)

---

<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: [16 Marzo, 2019 04:17 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/2 "2019-03-16T04:17:46Z")

</div>

Did you get latest and rebuild as requested?

---

<div class="post-metadata">

### Author: ![Destry\_Hunt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/destry_hunt/32/132757_2.png) [@Destry\_Hunt](https://meta.discourse.org/u/Destry_Hunt)
#### Post date: [16 Marzo, 2019 04:21 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/3 "2019-03-16T04:21:09Z")

</div>

To my knowledge, yes.

 ![Capture](https://global.discourse-cdn.com/meta/original/3X/6/d/6d9e62a91dedbde3c4d4d96f222a47db6015ff2d.png)

---

<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: [16 Marzo, 2019 04:23 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/4 "2019-03-16T04:23:59Z")

</div>

Any idea here @vinothkannans?

---

<div class="post-metadata">

### Author: ![Destry\_Hunt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/destry_hunt/32/132757_2.png) [@Destry\_Hunt](https://meta.discourse.org/u/Destry_Hunt)
#### Post date: [16 Marzo, 2019 04:26 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/5 "2019-03-16T04:26:25Z")

</div>

I have rebuilt, cleaned, updated, upgraded, rebuilt, cleaned, enabled, dis-enabled…I’m not sure if there is another command I can run to tune up my install.

---

<div class="post-metadata">

### Author: ![Stranik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stranik/32/85638_2.png) [@Stranik](https://meta.discourse.org/u/Stranik)
#### Post date: [16 Marzo, 2019 04:27 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/6 "2019-03-16T04:27:21Z")

</div>

I completely rebuilt the site 5 minutes ago and additionally installed it again on the computer (with the Discourse-solved plug-in). Strange, but I have no errors, everything works (in both cases). As I wrote earlier, I cannot repeat the mistake. (

---

<div class="post-metadata">

### Author: ![Destry\_Hunt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/destry_hunt/32/132757_2.png) [@Destry\_Hunt](https://meta.discourse.org/u/Destry_Hunt)
#### Post date: [16 Marzo, 2019 04:29 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/7 "2019-03-16T04:29:33Z")

</div>

I will disable every plugin, except the solved plugin and report back in 10 minutes.

---

<div class="post-metadata">

### Author: ![Destry\_Hunt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/destry_hunt/32/132757_2.png) [@Destry\_Hunt](https://meta.discourse.org/u/Destry_Hunt)
#### Post date: [16 Marzo, 2019 04:39 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/8 "2019-03-16T04:39:57Z")

</div>

I am in the middle of a rebuild, but it occurred to me that one thing I have not tried is to disable/remove the theme (Material Design Stock Theme). I suppose I can try that as well since that is another variable unique to my install.

---

<div class="post-metadata">

### Author: ![Destry\_Hunt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/destry_hunt/32/132757_2.png) [@Destry\_Hunt](https://meta.discourse.org/u/Destry_Hunt)
#### Post date: [16 Marzo, 2019 04:43 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/9 "2019-03-16T04:43:22Z")

</div>

Hooray, the rebuild worked with only the solved plugin and docker manager plugin. I will enable each plugin, one by one, and rebuild in between. I will then report back.

---

<div class="post-metadata">

### Author: ![Destry\_Hunt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/destry_hunt/32/132757_2.png) [@Destry\_Hunt](https://meta.discourse.org/u/Destry_Hunt)
#### Post date: [16 Marzo, 2019 04:58 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/10 "2019-03-16T04:58:27Z")

</div>

It looks like it broke again after I enabled the discourse-locations plugin. The only three plugins enabled now are docker manager, solved, and locations.

[https://solvecrimeinrealtime.us/logs/show/96bf242f6d353223809eb4b17ea6f16d](https://solvecrimeinrealtime.us/logs/show/96bf242f6d353223809eb4b17ea6f16d)

---

<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: [16 Marzo, 2019 04:59 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/11 "2019-03-16T04:59:07Z")

</div>

So file an issue on that plugin, it is third party.

---

<div class="post-metadata">

### Author: ![Destry\_Hunt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/destry_hunt/32/132757_2.png) [@Destry\_Hunt](https://meta.discourse.org/u/Destry_Hunt)
#### Post date: [16 Marzo, 2019 05:00 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/12 "2019-03-16T05:00:39Z")

</div>

Will do…thank you! Problem solved. I really appreciate your patience with me on this. Thanks again.

---

<div class="post-metadata">

### Author: ![vinothkannans](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vinothkannans/32/86465_2.png) [@vinothkannans](https://meta.discourse.org/u/vinothkannans)
#### Post date: [16 Marzo, 2019 09:41 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/13 "2019-03-16T09:41:57Z")

</div>

Yes, the issue is coming from the “discourse-locations” plugin. But this is related to the recent changes in solved plugin to prevent N+1 queries. Currently locations plugin also having the N+1 issue. I will make a proper way to include category custom fields in site serializer. Then @angus have to change the locations plugin code according to that.

---

<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: [16 Marzo, 2019 11:30 UTC](https://meta.discourse.org/t/site-not-building-after-2-3-0-beta-5/111762/14 "2019-03-16T11:30:52Z")

</div>


