greenrooster

Amazing. Thanks, @wpmudev-support9. It seems to have appeared around the 1.15.0.1 release for us. I went back to check our email logs for form submissions and it seems to line up with the release of that version. I’m only just now recognizing it.

Hi @wpmudevsupport12,

Below is a link to the form. You’ll notice that {html-6} outputs an example URL with variables. Issues arise on this form with {select-1} {select-2} {select-3} as they’re visually hidden unless conditions are met. They pass 0s if they are hidden at the time of submission, but do not appear as such on the front end html render. Also, the 0 values save to the database.

https://drive.google.com/file/d/11c7rBE8YZ5OB1EhpkYo1g9uotDgfUjm_/view?usp=sharing

Thanks for your great support!

@wpmudevsupport15 This does exactly as I need it to. Thank you! I’m going to close this ticket now.

@wpmudev-support9 This works exactly like I need it to. Thank you! I’m closing this ticket now.

Thanks, @wpmudev-support9, I’ll try this out when I am able.

@filak18, I agree, long term this would be great to have and utilize in areas like the email body and subject. For now, this will be a fine solution for me.

Cool! Thank you @wpmudevsupport15, for this. I will try this out as soon as I am able.

I was about to respond with something, but I see what you mean. Once a form is created with User Registration, you can’t remove that section. Very strange. Can you export the form and edit the JSON to remove:

"form-type": "registration",

and

"site-registration": "disabled",
"site-registration-name-field": "text-1",
"site-registration-title-field": "text-1",
"site-registration-role-field": "administrator",
"activation-method": "default",
"activation-email": "default",
"registration-username-field": "text-1",
"registration-email-field": "email-1",
"registration-password-field": "password-1",
"registration-role-field": "subscriber",
"confirmation-page": "2927",
"automatic-login": "",

And then you should be able to import the JSON. That’ll remove the “User Registration” menu and keep your form intact.

Probably an oversite in the development process. Should probably still be addressed in a future update.

Edit: by “intact” I mean you’ll have a new form with all the values/fields you’ve already created.

• This reply was modified 3 years, 9 months ago by greenrooster.

Just to let you know, I think the solution you mentioned for the multiple urls works basically. However, it doesn’t work if you’re trying to pass different query variables based on user input. I can’t seem to be able to pass field data into field values, which would make your solution work and allow for more advanced situations.

#2 could potentially be solved with #1. I wouldn’t need to pass data into value fields if I was able to conditionally use hidden field values.

There might not be a solution to this at the moment. It might not exist. And that’s okay, that’s why it’s a feature request ??

Thanks!

Hi @wpmudevsupport16,

#1: not exactly. I know you can populate hidden values with other fields already. This is more setting a hidden value and using it’s value based on another field’s selection.

For a sudo-code example, if you chose a blue shirt in the option below:

<select name="shirts" id="shirts">
  <option value="5">Blue Shirt</option>
  <option value="10">Red Shirt</option>
  <option value="15">Green Shirt</option>
</select>

<?php
function condition($option){

  $hidden-1, $hidden-2, $hidden-3 = null;

  if( $option == 'Blue Shirt' ) {
    return $hidden-1 = 'Blue Jeans';
  } elseif( $option == 'Red Shirt' ) {
    return $hidden-2 = 'Red Jeans';
  } elseif( $option == 'Green Shirt' ) {
    return $hidden-3 = 'Green Jeans';
  }

  echo 'Your' . $option . 'costs $' . $option[value] . 'and would look good with' . $hidden-1 . $hidden-2 . $hidden-3;

// 'Your Blue Shirt costs $5 and would look good with Blue Jeans.
// Only $hidden-1 is specified, thus is the only hidden value pulled.

Caldera Form’s conditions are more robust in that you can essentially disable hidden values if a condition isn’t met. (maybe that would have been simpler to say from the get go.

#2 Field macro in the URL field. Huh. I’ll take a look. That might be exactly what I’m looking for.

Thanks so much!

• This reply was modified 3 years, 9 months ago by greenrooster.

Great. Thanks for the update! I’ll figure something out in the mean time.

Hi. I’m closing this ticket. This issue has been resolved in 1.9.2.

I don’t know how to help with the technical side. Not in my knowledge base. But I can say from experience that rolling back the plugin for me in the last two updates has not negatively affected UM and WP. I would suggest trying it on a backup of your site before trying it on your live site.

But it does sound like there is some corruption (backend or frontend, I don’t know) of the information in your “Member” role. It might be that the only solution is to recreate it. In the grand scheme of the world, that’s a small, but unfortunate and frustrating, price to pay.

As a note for posting issues and requests for support, it’s helpful to know the version you were on and the version you have updated to. It helps pinpoint where issues might have been introduced, how to solve them, and if it is a known issue or not.

Hope this helps.

• This reply was modified 4 years, 4 months ago by greenrooster.

Sorry for the slow response. The resolution is a stopgap at best. Rolling back to 1.8.11 will fix the saving issue for the time being. So for now I will close this. Thanks for the support everyone!

• This reply was modified 4 years, 4 months ago by greenrooster.