I have a Repeater field which creates "jobs"
each job has title, text as sub-fields
and also a contact form 7 form which sends jobs applications.
I want to add hidden field which will also send the sub-field "title"
so whenever form is submitted we know which job the sender sent the application from
Tried to use:
Contact Form 7 Dynamic Text Extension
but it is not working with ACF as far as I'm concern
any help will be appreciated
you could use CF7's 'wpcf7_form_hidden_fields' filter before your form is displayed,
add_filter('wpcf7_form_hidden_fields', 'add_job_title');
function add_job_title($hidden){
//$current_job is the currenlty job loaded.
$hidden['job_title']= $current_job->sub_title;
return $hidden;
}
when the form is submitted, $_POST['job_title'] will have the value of the hidden field.
Related
i’ve set up an online form using contact form 7 that posts to my secret postie email address. each email gets collected and listed in draft format for moderation.
the post_type i’m using is one called testimonials that comes with my theme, which doesn’t have a body section as such, instead it has four custom fields – ‘author_name’, ‘author_company’ [not required], ‘author_url’ [also not required] and ‘author_quote’.
what i would like to do is have postie auto-fill the author_name and author_quote fields instead of trying to fill the [non-existent] body, using the your-name and your-message fields in contact form 7. that is, i want the values of the contact form your-name and your-message fields to be injected into the database as the meta_values of the pyre_author_name and pyre_author_quote meta_keys
i hope that makes sense?
i tried tweaking the add_custom_field function in the filterPostie.php file to see if anything worked, but no
function add_custom_field($post) {
if (‘testimonials’ == get_post_type()) {
add_post_meta($post[‘ID’], ‘pyre_author_name’, ‘$your_name’);
add_post_meta($post[‘ID’], ‘pyre_author_quote’, ‘your-message’);
return $your_name;
return your-message;
}
}
can anyone see what i'm doing wrong, or know what i might have to try to achieve what i want?
the site i'm working on is here: https://sistascarpentry.co.uk/testimonials/
thanks in advance
if you have
<button class="button yellow" type="submit"
name="button">Log in</button>
and you submit it, what gets posted to the server for the button which has a name but no value attribute?
The reason I ask is that I'm parsing HTML forms, and need to post the named values that send data to the server. I got the others covered, but wasn't sure about button.
According to the HTML Spec, a button's value is either determined by its value attribute or is an empty string. A button's value is only submitted with the form if the button has a name and is used to initiate form submission. If the button in your example is clicked, the resultant submission will be:
"button=" (quotes added)
Some browsers (mainly older IE versions) have incorrect implementations of this button behaviour that either set the value to the button's contents or submit all button values regardless of initiation source.
button does not get posted to server when the form is posted. Only input type's like text, password, select elements etc., which accepts user inputs will be posted to the server
Button never supplies value to form. It just provides a submit event that tells the browser to submit that form with all the input tags to the action attribute inside your form tag using the method attribute value. Button only provides the event and not the values.
There will be nothing posted to the server for buttons. When you click a button, it invokes the action of submit, that is all.
I tried it out by printing the request.POST in django.
This image shows a "Log in" button with no value but name="button", as asked
The console shows
< QueryDict: {u'csrfmiddlewaretoken': [u'9aAx..'], u'sensor': [u'sd1'], u'button':[u'']}>
So, in this case, the form is sent as a dictionary and for the buttons the key, value pair is "button" : " ". So, if you try to get value of this button with request.POST.get, you will get NULL.
So, the answer to your question is the form consolidates all the input values, which can be accessed with their 'name' including buttons. If no value is provided, it returns NULL.
I am looking for a way that I can create custom text on an HTML page dependent on user input from a submit form. I've looked at similar threads online but can't figure out how to do this on my own page.
Basically I have a text area with this default text "My name is and I want to give $10 to charity".
If I have a submit form button how do I get it to take the name entered from the form and then put that value in to the portion of the text?
Thanks
Andrew
This is probably what you are looking for:
http://jsfiddle.net/NbuF6/2/
Basically, you have a textarea (id: final-text) and an input (id: name). The button (this can be changed to the form's onsubmit function if you want to) calls the following JavaScript function to fill the textarea:
function fill_textarea() {
document.getElementById('final-text').value = 'My name is ' + document.getElementById('name').value + ' and I want to give $10 to charity';
}
I have a table that lists items. I have a form tag that surrounds this table. In this table I have ADD buttons that adds new rows to the database. I have EDIT buttons that edits a row as well. The form posts to the same action on the controller.
Now I need to add a filter row on the first which means I need to add a Filter button to submit the form with the filter parameters. Since this is still inside the main form, I now have the following problem: When I click the Filter button, the inputs that are used for the ADD button are being validated before anything gets posted. How can I prevent the validation from occurring when the user clicks the Filter button?
Make sure the Filter button is of type "button" not "submit" and do filter using ajax
As i see it, the easy way would be to fire the submit via js with:
.submit();
The other way would be to disable validation on that form with this:
$('#form').validate({
onsubmit : false
});
or
$('#form').unbind('submit')
I have one suggestion. Name Add button inputs differently and add row using javascript/ajax. When posting, Add button inputs will not be validated because they have different names
My ASP.NET MVC 3 website has code on the server side that checks for the name of the submit button clicked to submit the form. The code works when I use the mouse to click the button, but when I use the Enter key, the form gets posted, but the request doesn't contain the name of the submit button.
Is there some attribute I can set on the submit button to get this to work for both clicking and using the Enter key?
Here is my HTML:
<div>Search:</div>
<form action="/Item/Search" method="post">
<input class="fulltextsearch" id="FTSearchText" name="FTSearchText" type="text" value="" />
<input type="submit" value="Go" name="FTSearchButton" />
</form>
</div>
On the server side, I have a custom model binder that uses the following code to determine if the user clicked the submit button.
// See if the value provider has the required prefix
var hasPrefix = bindingContext.ValueProvider.ContainsPrefix(bindingContext.ModelName);
var searchPrefix = (hasPrefix) ? bindingContext.ModelName + "." : string.Empty;
var searchButton = GetValue(bindingContext, searchPrefix, "FTSearchButton");
// If this value doesn't have value, the user didn't click the button so exit
if (string.IsNullOrEmpty(searchButton)) {
return null;
}
private static string GetValue(ModelBindingContext context, string prefix, string key) {
var result = context.ValueProvider.GetValue(prefix + key);
return result == null ? null : result.AttemptedValue;
}
Here is the problem I'm having with this. I have a page that displays a list of items. I have a 'search' textbox and a submit button in an HTML form. When the user enters text in the textbox and clicks the search button or uses the enter key, the page posts the form data via HTML GET, and returns the first eight records found. The page then displays page links for additional pages. The problems is that when the user clicks a page link, the form data is all blank, and my filter information is lost (the form isn't posted with the form value when using these links). So, I end up displaying a blank list of items (blank searches returns zero results) instead of paging the data.
By adding the check for the button name in my form data, I could determine whether or not to simply page the data, or do a new look up.
I wouldn't rely on this. There are plenty of documented bugs with this scenario. Just add a hidden field with name='submit'. That way it wouldn't be too hard to recode the backend.
<input type='hidden' name='submit' value='FTSearchButton'/>
So, I researched this last night and almost got somewhere. Then this morning, I really did get somewhere and here's where I ended up.
Apparently the W3C standards for form submission are pretty lax when describing the functionality as it relates to the Enter button and submitting forms. It seems they determined that
When there is only one single-line text input field in a form, the user agent should accept Enter in that field as a request to submit the form.
So that leaves a lot of wiggle room for the browser makers. Today, virtually all browsers support using the Enter key to submit a form, whether the form contains one or more single line text input boxes.
The problem I'm having is more or less unique to Internet Explorer, and only when the form contains one, single-line text input control. For whatever reason, Microsoft decided that when Internet Explorer submits a form like this, it doesn't include the submit button's name/value pair in the post body. However, it does include the button's name/value pair if the user clicks the submit button --or-- uses the Enter key, and the form contains more than one single-line text input control.
So, the only solution I can think of or find suggested is to add a second single-line text input to my form, and then set the the style to
visibility: hidden; display: none;
My form now has two single-line text input controls, so the form will post with the name/value pair in the form body, regardless of whether or not the user used the Enter key or clicked the submit button.
So, we have a workaround that was discovered by ASP.NET developers. It seems the key/value pair is required by ASP.NET web-forms to fire the click event, so this work around isn't something new, albeit not my favorite way to do things.