Hyperlinks failing using dynamic data

I’ve been through this over & over
Following the tutorial videos, particularly Brian’s

But this code does NOT CREATE Browser hyperlinks
It is not clickable and does not pass along the extra value

<td><a href="#" dmx-bind:href="edituni.php?id={{UniID}}">{{UniversityName}}</a></td>

The output of values is working

In Brian’s video he enters the dynamic string to create the redirect with values in the URL
but in my Wappler this opens up by DEFAULT to TEMPLATE –

When the href links didn’t happen I tried entering the same dynamic string only with the “Expression” input selected. Nothing helped with that, too.

The dmx binding evidently “overrides” the “#” in the a href= “#” but not as wished.

That code is correct and should generate links. Do you have a link to the page we can see?

Actually I just saw your error …

you have <td dmx-text="eventhotel">

Remove that binding so it is just <td>

Thank you, Brad!

It instantly took care of it — outputted the links with url values immediately!

Should I make the other TD list items such as

<td dmx-text="event_id"></td>
      <td dmx-text="event_date.formatDate(&quot;dd-MM-yyyy&quot;)"></td>
      <td dmx-text="eventday"></td>

also into simple <td> 's as well?

This is how the bootstrap 4 component outputted the table–

<tbody is="dmx-repeat" dmx-generator="bs4table" dmx-bind:repeat="serverconnect1.data.query1" id="tableRepeat1">
    <tr>

The other ones are fine. Glad it’s fixed for you! :beer:

Well, just one more thing then –

Passing that value gives me what I wanted –

http://localhost:8888/akd/mykade_events.php?reg_event=1

but I haven’t found the value that will sit in that form now –

I finally tried using {{$_GET.reg_event}} as the dynamic attribute of the input I am aiming at –
I also used {{reg_event}}

but I can’t get that value loaded into the target form input that is called up –

This must be a simple one.

Should most likely be just {{reg_event}}

Also looks like you are missing your server connect query unless it is further down in your app connect tree.

Can you post a screenshot of what you see when you click on the lightning bolt to bind your data?

Here’s my problem – I am trying to receive a value passed from one form to another form that then needs to take the input value that was passed and POST it to a database.

This post-to-database Insert presently has this code for that input field “reg_event”

<div class="form-group">
  <label for="inp_reg_event">Reg event</label>
  <input type="number" class="form-control" id="inp_reg_event" name="reg_event" aria-describedby="inp_reg_event_help" placeholder="Enter Reg event" dmx-bind:value="{{reg_event}}" value="{{$_GET.reg_event}}">
</div>

I have also tried this without the $_GET. –

<div class="form-group">
  <label for="inp_reg_event">Reg event</label>
  <input type="number" class="form-control" id="inp_reg_event" name="reg_event" aria-describedby="inp_reg_event_help" placeholder="Enter Reg event" dmx-bind:value="{{reg_event}}" value="{{reg_event}}">
</div>

This is the link that opens up this post form

http://localhost:8888/akd/mykade_events.php?reg_event=1

In any case the Numeric Value for “reg_event” is not displaying – the reg_event input is blank

You asked about the dynamic values available and this is what I get for the post form
Selecting here does not place any value at all.

The query is bound to the connection otherwise this bootstrap generator would not have built this form.

The value to this input can only be a dynamic value that recognizes
http://localhost:8888/akd/mykade_events.php?reg_event=1 which I have tried to set a Dynamic Attribute for …

I can only set {{reg_event}} in the Dynamic Attribute by manually typing it.

This problem is HUGE
Hours of work trying to fix
WAY behind schedule
I have tried solutions that work in php when Wappler didn’t work
Something about dmx-bind

dmx-bind:value="{{reg_event}}"
This is the critical part in the page code that simply doesn’t recognize the

link value passed that opens this post form page
from
http://localhost:8888/akd/mykade_events.php?reg_event=2

Now I’ve made the input “hidden” The inspector console shows this is what is output on the page when it loads with dmx-bind:value={{reg_event}}

The syntax seems to be a little off from what i can see.
dmx-bind:value="reg_event" is in my opinion what it should be, please try that and let me know.

I believe I have tried this before, but I saved the code as this for that input reg_event

<div class="form-group">
  <label for="inp_reg_event">Reg event</label>
  <input class="form-control" id="inp_reg_event" name="reg_event" aria-describedby="inp_reg_event_help" placeholder="Enter Reg event" dmx-bind:value="reg_event">
</div>

And nothing happened on passing that value
Inspect console showed same end result --Nada Value is blank

In Wappler, Click on App inside the App Structure panel, then look inside the App Properties, click Define Query Params and please show me a screenshot of whats inside there.

This is all I have

Because there is nothing inside your defined query parameters then try this please

<div class="form-group">
  <label for="inp_reg_event">Reg event</label>
  <input class="form-control" id="inp_reg_event" name="reg_event" aria-describedby="inp_reg_event_help" placeholder="Enter Reg event" dmx-bind:value="$_GET.reg_event">
</div>

Test it, if still not working maybe try

<div class="form-group">
  <label for="inp_reg_event">Reg event</label>
  <input class="form-control" id="inp_reg_event" name="reg_event" aria-describedby="inp_reg_event_help" placeholder="Enter Reg event" dmx-bind:value="$_GET.reg_event.value">
</div>

I have tried both – here is the 2nd try with the .value added

Inspect console still shows value> empty

<div class="form-group">
  <label for="inp_reg_event">Reg event</label>
  <input class="form-control" id="inp_reg_event" name="reg_event" aria-describedby="inp_reg_event_help" placeholder="Enter Reg event" dmx-bind:value="$_GET_reg_event.value">
</div>

Since the passing document is NOT a form – only passing a value in the hyperlink

and my receiving file is a POST form I was trying all kinds of things in both Firefox & Brave browsers including testing if the url should be with single quotes or double quotes on the values

such as http://localhost:8888/akd/mykade_events.php?reg_event=‘1’
or
http://localhost:8888/akd/mykade_events.php?reg_event=“1”

but it doesn’t make any difference

I have used the URL for HUNDREDS of FORMS where I have passed along up to 20 values at a time

I always get it working to automatically FILL IN the inputs of the next POST form

http://localhost:8888/akd/mykade_events.php?reg_event=1&my_values=24&first_name=Clark etc etc

Wappler is driving me NUTS

Ok, one moment let me make up an actual test page quickly so i can direct you better, unfortunately I am not getting it right from memory, give me a moment please.

Ok, so lets make this easier for you.

You need to define you query parameters first.

On your page click App from the App Structure panel, click define query params, you will see one entry called query, click the query entry then click the + button, click add variable, enter the variable name, in your case it will be reg_event, click save.

In you page change to this

<div class="form-group">
  <label for="inp_reg_event">Reg event</label>
  <input class="form-control" id="inp_reg_event" name="reg_event" aria-describedby="inp_reg_event_help" placeholder="Enter Reg event" dmx-bind:value="query.reg_event">
</div>

Test and let me know, here is the supporting documentation on the procedure that will help and give more detail if you need it.

THAT is IT!

Thank you so much for your expertise and patience!

Enormous gratitude, Paul !!

If you want to use URL parameters on the page - for example to filter a database query or to show/hide specific page elements depending on URL parameter value, you’ll first need to define them in App Connect.

If there had been just a tad more examples I would have gotten that immediately when I first saw this "Documentation"

This didn't make clear by "If you want to use URL parameters on the page"
to someone using Wappler that the URL PARAMETERS was a REFERENCE to an URL on another page -- the PRECEDING page where the URL was generated.

This is an example of where the existing documentation simply drops in to the middle of something to "explain" a concept without INCLUDING the CONTEXT

which would have been the PRECEDING page where the URL was generated to be passed to "THE PAGE"

and then Step 3 Show the Consequence in this same documentation --

"The defined URL Parameter will now appear in the dynamic data pickers and you can use it for your dynamic expressions." is absolutely unhelpful

because I don't see the FLOW -- show me the specific example of HOW you will next Use this technique.

DEFINE URL PARAMETERS should have been for people like me

HOW TO USE URL PARAMETERS -- Several Examples

  1. Set up URL values on Page One
  2. Show Page 2 where we have to DEFINE these "extraneous" values so that they are recognized when the page the URL points to loads
  3. Show the common uses in the AFTER defining extra Query values

The point I have griped about concerning Wappler is that PHP knowledge & standard techiniques that have proven useful and fool proof for years of experience
Are so often DISABLED inside the Wappler environment

Once you commit to Wappler ABANDON everything that PHP manuals teach on how to use familiar Classes, functions, variables, etc.

I wouldn't have suspected that Code inside Wappler would invalidate so many standard ways that PHP has always handled dynamic values.

At any rate, Paul, thanks so much for wrestling with this.
I would guess this has just given you an extra piece of information, too
even though you are so experienced with Wappler.

I know what you are saying, I have had a hand in trying to assist with Documentation, and to be honest, it is quite a nightmare, as just like any coding language, there are probably 5 ways you could do the same thing and achieve the same result, however 1 way may work better than the other, or one way may give you more scalability, so it is all just so dependant on what the user is making.

When we used DMX Zone singular extensions in the past, it was a little simpler to understand for a person porting over from a language like PHP as if I purchased a single extension for SlideShows, then I really only needed to do that one singe part differently to the rest of my page.
With Wappler, you need to pretend you are an end user with very little to no knowledge of code and try use it in that sort of way.

I have been using DMX Zone for absolute years, and Wappler since the day one, and after an initial teething period, and initial frustrations, I finally just sort of clicked one day, and it all made much more sense.
I would not look back now, as I can literally do 3 times the amount of work daily than i used to manually coding, so your time wastage initially should become less and less as you progress and at some point you will just love it, if you stick through the hard start.

1 Like