Page Query parameters

Hi everyone,

Am I doing something wrong, I am trying to set a query parameter on a NodeJS content page but for some reason its not showing in the data pickers.

I have defined the following page query parameter:

However when trying to set a dynamic value I do not see it appearing as an option:

Any help is always much appreciated.

Thanks

Hello,
this will be fixed in today’s update.

1 Like

Is your content page linked to a main page?

And also where are the Query params defined? on the content page or on the main page?

Hi George, query params are set on the contnet page and yes its linked to a main page
image

Just an update to this @George & @Teodor it seems as though I can make this work if I define the query parameter on the Layout page (in my case layouts/main) then it will appear in the query selector. So I can use that as a work around for the moment however I just wanted to check is that something that is by design or should we be able to define query parameters on the content pages and not have to declare them on the parent layout page?

Thanks

1 Like

Sorry for bumping this old topic up, but @George can you please clarify about query parameters that @datguru is asking?

Query parameters should be configured on layout page or content page?
In my case I’ve configured query parameters on content page and I don’t see them in data binding.

2 Likes

I just came across the same question, did you figure out how to make them appear in the data binding picker?

1 Like

The query params need to be defined on the layout page in order to see them in the data picker.

2 Likes

Came across the same challenge.

If I understand correctly, I have to define all possible query params for all actions on the layout page and NOT on the content page, where are they required?

How do I manage, e.g. multiple id params? Sounds wrong to me… , e.g.

/player?id=xxx
/tournament?id=xxx
/tournament/challenge?id=xxx

Not sure i understand your question. You can have one id param in an url. Different routes/paths are not related here. Defining it on the main page will just make the query params visible in the data pickers on the content pages. They will work without defining them, but just won’t be available to pick in the data picker.

Yeah, I see, the ID was a (very) bad example :see_no_evil:

Let’s say, a page has a couple of query params for a search, e.g.
/foo/bar?param1=1&param2=2

My understanding was to bind them in “Define Query Params” and then they are available on the page for various scripts?

When using nodejs with content pages you need to define param1 and param2 on the main page.

2 Likes

Thank. I try to get my head around this :rofl: