Solved plugin bug


I’m on latest tests-passed (1.5.0beta7 +48) discourse with latest “solved” plugin and I have some problems while creating a new category.

Steps to repro (checked that on latest stable Chrome and IE11):

  1. Create a new category
  2. Tick “Allow users to accept answers” checkbox
  3. Images and Templates after ticking are not clickable

updates: Also many elements are not clickable - search icon, hamburger menu, profile, avatars…

After trying this I get error on /logs:

4 x Uncaught Error: Property set failed: object in path "custom_fields" could not be found or was destroyed. Url: Line: 8 Column


Error: Property set failed: object in path "custom_fields" could not be found or was destroyed.
    at new Error (native)
    at Error.r (
    at l (
    at Object.u [as set] (
    at e.default.s.Mixin.create.set (
    at set (
    at null.<anonymous> (
    at a.d._set (
    at a.d.set (
    at Object.u [as set] (

PS: I don’t have any custom fields.

Do you have any other third party plugins installed? If so disable them all.

No. I have just tagging and solved plugin.

Was the site in English or another language?

Oops, I thought I already replied to this topic.

Few days ago I was looking into this issue and was able to repro this consistently. In fact I can repro this right now here on meta!

Repro Steps:

  1. Click “Create a new category” button.
  2. Open “Settings” tab.
  3. Tick “Allow topic owner and staff to mark a reply as the solution” checkbox.
  4. Notice there will be an error in console.

I tried to fix this issue and was able to pinpoint the code causing this issue:

this.set("custom_fields.enable_accepted_answers", value);

^^ custom_fields is not defined when creating new category, however it is defined when editing the category.

I spent considerable time on this issue and was not sure how to fix this. :frowning:

@eviltrout can you look into this?

Also related:


Is this still an issue @techapj?

Yes, this bug still exists. Can repro here on meta.


I recently tried using the same code for adding category custom fields to a plugin and ended up getting the same error when attempting to add the custom field while creating a new category. The feature-voting plugin also uses the same pattern and produces the same error. Is there a way to get this to work so that custom fields can be added when creating a new category?

Quick and easy solutions are either disable the checkbox in the category-custom-fields connector if category.custom_fields is not defined, or to move the plugin’s category selection into site-settings.

1 Like

Hi, any progress on this? Is category.custom_fields still not defined while creating a new category?