Parameters are not working in nodejs

[AdrianoLuiz]

do you want the link with username and password to verify @patrick?

[AdrianoLuiz]

Same problem with pagination @patrick

Please this is getting in the way of my work

[AdrianoLuiz]

Hi, @patrick I know you are busy with Wappler 5 release but we need to have the parameters to work with nodejs.

[JonL]

I have no issues with retrieving query parameters so it may be something with your setup.

[AdrianoLuiz]

node js?

[JonL]

Yes.

[AdrianoLuiz]

Are you working with main layouts?

[JonL]

Yes also.

[Apple]

What NodeJS version do you have?

I think JonL may be using NodeJS 16

[AdrianoLuiz]

Nodejs vs.16

[JonL]

@Apple

I think JonL may be using NodeJS 16

I am but I believe it has nothing to do with it. The query parameters are parsed by App Connect through the meta tag named ac:route which in turn is added in the appropriate page by the UI routing panel.

[mebeingken]

Having a second ac:route meta tag will cause query to fail. Make sure there is not a second ac:route meta tag in your partials nor in your layout (as Patrick mentions above).

[mebeingken]

It can also break if you have two routes to the same page, and one of the routes does not use the parameter.

For example, if I were to reverse the position of these two routes, the :cma_id parameter would not be written into the ac:route meta tag on the content page.

[AdrianoLuiz]

Hi Wapplers, did anyone manage to solve this? I see that there are other similar topics with no solution.

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: [image] However when trying to set a dynamic value I do not see it appearing as an option: [image] Any help is always much appreciated. Thanks

Query parameters won't display in data picker

Hello, I was following this tutorial https://docs.wappler.io/t/define-url-parameters/2913 : I’ve created server action, I’ve defined query parameters [image] But when I’m trying to define input parameters in Server Connect - I just won’t appear in dynamic data pickers: [image] [image]

Query params not available on route to page under SPA

wappler 5b6 macos monterey nodejs 14 postgresql 13 problem one click of button on page 1 we are doing browser goto page 2 with a dynamic param in url. post routing, this query param is not immediately available on the page - did a browser alert on page 2 to show on page load via an autorun flow and found that we were getting ‘undefined’ for query param mapper. expected as it happens on the stable version of wappler (that we are running on PROD) the routing is flawless as the query param …

[AdrianoLuiz]

This problem still exists, any solution prediction?

[Teodor]

I can’t recreate this issue.
Routes:

Page set up:

Rendered in the browser as:

And in the dev tools you can also see the param:

So no issues at all. There must be something wrong with your page/project setup.

[guptast]

Wappler v5.1.5
MacOS, NodeJS, SPA

This is not working for me as well. I have setup a query parameter on the layout page and a dmx-on:click browser.goto event to access a content page with the url and route parameter. The route has been correctly setup and when browsing to the content page by clicking on the dynamic link button, the content page is showing the parameter with correct values. However, the query parameter is returning no value on the target content page.

The dev console is showing the query param values but dynamic binding of the query parameters is returning empty value.

Is there any solution available to resolve this issue?

[guptast]

I have got it working. I didn’t realise that I had given different names to the parameters I was using for the url and query. Once I renamed parameters in both places to the same names, the parameter values are passing between the pages correctly.

[AdrianoLuiz]

Could you show what worked? as you did? for me it only works if I do it manually

[guptast]

This is an example of the code I have when using dynamic url parameters.

1. Route Path: /painel/imovel/detalhes/:token - route on the contents page

2. On the layout page - click on App in the App Connect panel, click on Define Query Params - In the Schema editor - add a new variable named token. This var name should be the same as used in the route path token. If these are different, then url query parameters on content pages don’t work.

3. Add a button with on-click event, and add this code browser1.goto('/painel/imovel/detalhes/'+product_token). product_token is the token or id that’s being sent to the target page route as a value for the url parameter :token. This value can be accessed on the content page as query.token and can be used to filter API queries etc.