Formatter load doesn't exist for type string

Wappler General
1

I’m having two issue. I’m building a forum with list of Topics, clicking a topic goes to topic with comments. Similar to wappler forum.

I am using two region with Show/hide. First Topics are shown, when a topic is clicked, the individual topic section is Shown with comments bellow.

1- Cannot get Data Details to show in Wappler. It works fine in browser.
I have a repeater with titles. Click title > show data details (and hide titles).
The circled region should be populated with record details . Works in Chrome.

3
3.PNG1732×888 60.4 KB

2- Also when a Title is clicked i want a Server Action to Run to pull comment associated with that topic.
I created a Action with $_GET.feed_id variable, set Server connect to “not AUTO RUN”. But when i use this on click event: comments.load({feed_id: feed_id}) I get error

“parser.js:752 Formatter load doesn’t exist for type string” in Chrome.

The server connect loads if i set a default value with $_GET.feed.id so the LOAD part works but it’s not sending the variable with value.

Also i just noticed the variable names don’t match so i renamed but still same issue.

5
5.PNG1875×648 67.4 KB

6
6.PNG711×543 15.4 KB

I give up for now.

2

Why use a custom query when a basic wappler query would do this? You are just making things complicated for yourself

3

I find custom query easier to work with. but also i forgot i could do joins in normal queries :grinning:

4

Ok, seems something is missing in the content page preventing Data Details showing any results. It must be a component i need to add to the header, haven’t figured it out yet :slight_smile:

5

main issue is this error when i Load a server connect:

parser.js:752 Formatter load doesn’t exist for type string

6

Narrowed my issue down to that i cannot load a Server connect from within a Repeat Region

So basically, i have a list of topics, with onlick > Load server throws above error.

Putting the onclick outside the repeat works. still struggling…

7

Finally!

It seems ‘Comments’ is a reserved word. Renamed the server connect to server_comment and got it working. jeeze that was a long day

1 Like