Fred Settings aren't rendering

[frankie_tech]

Here’s the html and option sets so far:

<section class="bg-">
    <div class="container">
        <div class="row justify-content-center">
            <div class="col-lg-8 col-md-10">
                <h2>{{ title }}</h2>
            </div>
        </div>
    </div>
</section>

{
  "remote": true,
  "settings": [
    {
      "name": "title",
      "label": "Section Title",
      "type": "text",
      "value": "Lorem Ipsum"
    }
  ]
}

When I drag this into the Fred dropzone, and open the settings it opens a blank sidebar without any inputs in it. I’m pretty sure I followed the docs about optionsets correctly.

[halftrainedharry]

I tested this code and can’t reproduce any issues. It seems to work as expected.

What versions of MODX and Fred are you using?

[frankie_tech]

I knew I was forgetting to add something. MODX 3.0.5 and Fred 3.1.5

[halftrainedharry]

Where did you define the option? Directly in the Fred-Element (tab “Options”) or in the vertical tab “Option Sets”?

---

Do you see any errors in the developer tools of the browser (tab “Console”) or requests that fail (in the “Network” tab)?

[frankie_tech]

Where did you define the option? Directly in the Fred-Element (tab “Options”) or in the vertical tab “Option Sets”?

Both actually, is there a preferred way to do it?

Do you see any errors in the developer tools of the browser (tab “Console”) or requests that fail (in the “Network” tab)?

The only error appears after clicking on open settings and it is about proper use of aria-hidden.

Blocked aria-hidden on an element because its descendant retained focus. 
The focus must not be hidden from assistive technology users. 
Avoid using aria-hidden on a focused element or its ancestor. 
Consider using the inert attribute instead, which will also prevent focus. 
For more details, see the aria-hidden section of the 
WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: dt
Ancestor with aria-hidden:  <div class=​"fred--sidebar" aria-hidden=​"false">​…​</div>​

[halftrainedharry]

@frankie_tech

is there a preferred way to do it?

No, I just thought maybe you created an option set (under the vertical tab “Option Sets”) and didn’t connect it to the element (with the dropdown in the tab “Options”), as the reason why you can’t see the setting on the front-end.

I still can’t reproduce any issues (using the same MODX and Fred versions), so I am out of ideas.

[frankie_tech]

Yeah, it’s a real head scratcher. Could it be permissions or something that aren’t set? It feels like it is too granular of a place to suddenly not have permissions for when I can grab the elements and put them in the template.

[halftrainedharry]

@frankie_tech

Could it be permissions or something that aren’t set?

Unlikely. You could check it with a sudo user to be sure.

---

On the front-end when you click the “Elements” button, the code should make an AJAX-request with the action = “get-elements”. Can you see the “title” setting (you defined) in the JSON response?

[frankie_tech]

Okay then it’s not permissions since I’m already a sudo user.
This is the response I got, I have updated the name on the off shot that title was reserved which is why the name is different.

I just had my coworker try it on her computer and it also shows a blank side panel for her.

Mid-reply edit: It was CSS. There was a selector that was a little too broad in it’s definition that was adding display: none -_- Thank you for your help anyways!