Formatter goto doesn't exist for type array

kfawcett · October 18, 2019, 4:10pm

I have the following Server Connect, which is similar to others I have on the same page. For some reason this one is not working because it’s complaining about an array and I’m not sure why. The $path variable is the current page.

<dmx-serverconnect id="userAccountDetails" url="dmxConnect/api/Data/getUserAccount.php" dmx-on:success="userAccountDetails.data.UserAccount.approved==1 && '<?php echo $path ?>' == '/get-started' ? browser1.goto('./') : ''"></dmx-serverconnect>

This is the error in the browser.
parser.js:752 Formatter goto doesn't exist for type array

Here’s what the Server Action is doing.

mebeingken · October 18, 2019, 4:17pm

With a single query, I think you can drop the .data.

on:success="userAccountDetails.UserAccount.approved==1

EDIT: Actually, that’s not true.

kfawcett · October 18, 2019, 4:19pm

That doesn’t appear to work. I don’t see the error, but I’m guessing it’s because it’s not returning a result.

kfawcett · October 18, 2019, 4:20pm

This is the structure for the data.

mebeingken · October 18, 2019, 4:20pm

Isn’t goto referring to browser1 though?

mebeingken · October 18, 2019, 4:22pm

As-in, maybe there is another browser1 on the page, so it is interpreting as an array?

kfawcett · October 18, 2019, 4:25pm

ahhhhhhhh… you da man! So I have to have a separate “browser” for each action? That seems unnecessary, but it solved my issue.

Thanks Ken!

mebeingken · October 18, 2019, 4:53pm

No need for a separate browser…just one per page, ya?

scott · October 18, 2019, 4:54pm

I think he means just name them differently. so browser1, browser2, etc.

I tend to name my components after their page, so for example, browser1 would become bwr_home or bwr_index or whatever the page name is.

mebeingken · October 18, 2019, 4:57pm

Exactly. Especially helpful when using includes.

kfawcett · October 18, 2019, 5:16pm

Thanks @scott and @mebeingken. I’m doing most of this in a header include and didn’t realize I also had a browser1 on the specific page I was working on. Removing the browser1 on the page allowed me to have one browser in the header with multiple server connect browser.goto actions.