[katw]

Hi @DASub

The best way would be to use a REGULAR EXPRESSION (REGEXP) and add that to the field element Validator.

There are heaps online you can source and test out.

Watch out for old expressions that are not aware of new and legitimate TLD’s like .me, .support, .info etc

You also need to think about the HTTP/HTTPS prefix check and the presence of a subdomain v’s www starting pattern.

All the best

[katw]

Hi, saw your post and thought I could help you out.

I think you will find the variable token {url} will provide what you want.

Add the token as displayed in the body of your notification email.

Have a look at the [</>] button next to the message box field in your notification settings for others you can insert.

I haven’t checked how accurate it is; so do some testing.

Attachments:

You must be logged in to view attached files.

[katw]

Hi @carlease, saw your query.

Yes it is totally feasible.

You would need:

1. Their explicit permission (opt-in for SMS)
2. Mobile field with an internationally formatted number
3. An account with a SMS service offering an sending API (to allow you to programatically tap into their system and send the message
4. Write custom code for QuForm to:
   • generate the SMS message
   • Forward message to the service using API
   • Handle API return messages (eg sent ok, not sent, unsubscribe)

The later step would probably involve writing code using the quform_post_process hook.

Do you have an existing account with a SMS service? If so, check what API they have available you could tap into.

[katw]

Yep, the message at footer above sums up my feeling too… ahh.

BTW the error message “not in a recognised format” occurs upon choosing the file; not at form [submit].

So Quform hasn’t checked the servers modified MIME approval list at form initialisation is my guess.

• This reply was modified 6 years, 9 months ago by katw. Reason: add more info

[katw]

Unfortunately, the problem was not solved by adding the mime type to the WP_mime_list.

I check it was added by var_dump(wp_get_mime_types()). I can confirm it was added.

After doing this, I am now seeing the error message: not in a recognised format.

Which has changed.. but one I had seen before I added the EML MIME type to .htaccess.

I again checked .htaccess to ensure my addtype entry was present. Yes

I also tried a different browser for upload.

Sample EML file attached for your testing. Please delete this file once you get it. Thanks

[katw]

I did some code digging and see your routines (rightly) use the ‘allowed’ MIME file list in the WP core.

So solution is to add ‘EML’ to permitted list by either:

Adding a Plugin – e.g WP Add Mime Types

OR

Functions.php code insert:

function my_theme_custom_upload_mimes( $existing_mimes ) {
	// add EML to the list of mime types
	$existing_mimes['eml'] = 'message/rfc822';
	// return the updated array
	return $existing_mimes;
}
add_filter( 'mime_types', 'my_theme_custom_upload_mimes' );

Shared for others… who may have a similar situation

[katw]

Hi fred, saw your post and thought I could offer a suggestion.

Have you seen the migrating from V1 doc?

It may help to give you an idea of what may be involved.

Cheers

Kat

[katw]

I should also mention the Form > Settings > [Database] button/tab .

You will notice it says the other database and suitable fields must already exist before this can be used. But once they do posting data into another database can happen here.

[katw]

Saw your post and thought these links may help you get started on item 1 and 3.

Refer: create-and-edit-custom-database-rows AND adjust using hints here. If you search forums for “Custom DB” you may find other tips.

Item 3: Troubleshooting email guide.

All the best

[katw]

1. HOOK to extend Field Validators and Filters, so we can add our own.
2. HOOK for setting field defaults in ADMIN mode (for fields that have visibility Admin)

Thanks

[katw]

I just lost my post on submit (login timeout). grrr

I have a TEXT ELEMENT field for a Business Number (ABN)

Filters: Digits (no whitespace), Trim
Validators: Length Max 11|Min 11, Digits (no whitespace)

ON edit entry, I typed “No thanks” in field.

Hit save, message “Entry Saved”. No errors shown.

Exit to View Entry the field has not been changed (which is good as text not allowed).

So clearly there is a bug here. No validators or error messaging on [save/submit]

[katw]

Thanks.

1. Not sure what benefit file upload is without file being uploaded?? My head hurts on this one

2,3. Awesome, the link helps heaps

4. Ok, thought so

5. Was aware of this but didn’t know how it would affect the plugin when saving files. Is it excused from security check?

[katw]

Hi @maxim, saw your query and thought I could offer a suggestion.

Are we redirecting to a “Thank you page” for a customer OR a page to do post-processing of form data?

If THANKs page:

From what I understand the quform_confirmation_redirect_url hook is used by ALL confirmations.

If you have multiple confirmations setup and/or multiple forms you will need to add code within this function to check the form id and the confirmation id for the one you want to change before changing the url returned.

It may be better to use quform_confirmation_redirect_url_X_X hook and replace the X_X with the confirmation ID you want to trap and work on. Much easier as detection work already done.

Basic structure refer: quform_confirmation_redirect_url doc.

Within the function you need to return a fully formed URL which is the path to the page you created.

If post processing page:

Have you seen the docs:

1. Passing data from one form to another
2. Sending form data to another script

If you have written code as you have suggested. Sharing it may speed up the solution process.

[katw]

@generail Check the link. It has been disabled

[katw]

Hi,

The treatment of Group elements and their layout functionality in Edit Entry mode is absent, so plenty of opportunities for improvements if you ever run out of fun things to do <grin>.

Just to let you know I have come up with a solution to make Group Visibility work on admin v’s front-end mode.

1. Hidden field with default value = ‘Public’
2. On form submit change state flag to ‘Admin’ (or empty if preferred)
3. Conditional logic on group element to show/hide according to this field value.

Yes it unfortunately means a ‘variable’ field is on show in admin but I can live with it.

Close ticket

[Author]

Posts