WebsiteBaker Community Forum

WebsiteBaker Support (2.8.x) => Modules => Topic started by: Stefek on September 07, 2012, 10:59:44 AM

Title: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Stefek on September 07, 2012, 10:59:44 AM
Hello,

this is the new version of mpForm Module.
Updates created in collaboration with user NorHei to match our needs.
We share the work as we think it may benefit your work and the speed of form creation.

The german thread can be found here:
http://www.websitebaker2.org/forum/index.php/topic,24617.0.html

See the Screenshot below to see the most recent changes.

Please report any issues you may run into.

Have fun with the module.

Kind regards,
Stefek

[ Download mpForm from the WebsiteBaker Addons Repository ] (http://addons.websitebaker2.org/pages/en/browse-add-ons.php?id=0A702411)
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Hans on September 08, 2012, 08:59:42 PM
Maybe you should mention that this wonderful script is also in the addon Repository http://addons.websitebaker2.org/pages/en/browse-add-ons.php?filter=mpForm%20-%20Multi%20Purpose%20Form%20Module&id=0A702411 (http://addons.websitebaker2.org/pages/en/browse-add-ons.php?filter=mpForm%20-%20Multi%20Purpose%20Form%20Module&id=0A702411) Hope that's the place where updates can be found too.
Thanks again
Hans
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Stefek on September 08, 2012, 09:24:31 PM
Hello Hans,

thank you.
I didn't know the repository is open for public access now. So this was a good hint.
I'll update the first post and link straight to the download page.


Kind regards,
Stefek
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: NorHei on September 13, 2012, 11:10:10 PM
New version whith several Bugfixes.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: NorHei on September 15, 2012, 08:48:36 PM
Bugfix for the bugfix  :lol:
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Stefek on September 16, 2012, 04:30:32 PM
Thanks for the quick fixes Norbert.

I uploaded the new version to the WB Repository

[ Download mpForm from the WebsiteBaker Addons Repository ] (http://addons.websitebaker2.org/pages/en/browse-add-ons.php?id=0A702411)

Stefek
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: phil.hawkins on October 08, 2012, 11:32:05 PM
This module looks great! I was wondering though, if there is a way to customize the subject line of the email sent to the site owner to include one of the fields filled out in the form. More precisely I have a field called lastname that I would like to append to the end of a static subject line. So I want the notification email's subject line to read "New response from: [lastname]" Is this a possibility?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: NorHei on October 09, 2012, 09:00:23 PM
Something like that will be added in next version , good idea!
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: kbob on October 20, 2012, 12:52:53 PM
Hi there

Is there a way of having multiple file upload boxes, but without the repeat of the file size/file type info below each one?

Thanks!
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: NorHei on October 20, 2012, 07:21:13 PM
Yes , you can  :-D

Use CSS to deactivate that message for a single field:

.fid869 .mpform_field span {display:none;}   

Go into the source view of your browser to get the ids of all fields you need to deactivate.
then simply deactivate em .

Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Sokhim Sim on November 10, 2012, 09:10:36 AM
Thanks for this module, it very useful for all WB user. But I have question regarding to this module.

1 - How to Change Calendar Style?
2 - How to do email Verify E-mail?
3 - How to add code to input box?
Ex: default input box:

Code: [Select]
<input type="text" name="field9" id="field9" value="" class="mpform_date" />
want to modify to

Code: [Select]
<input type="text" name="field9" id="field9" value="" class="mpform_date" readonly="true" />
One more thing when I try to delete record it not working. Kindly help to fix.

Best Regards,
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: bupaje on November 22, 2012, 08:25:26 AM
I have a suggestion for this - it is a little out there so may not be of interest but I offer the idea. I have thought it would be interesting to have special fields that could concatenate or perform simple math. So you could create a form, add 3 text fields, set them to integer and set 'field 1 + field 2 = field 3' then the user could build a simple calculator. For example see the calculator at the bottom of this page http://www.allfrom1supply.com/merchant2/merchant.mvc?Screen=PROD&Store_Code=AF1S&Product_Code=D1-Slate&Category_Code=Decoria so if there was a way to allow a form builder to build a simple calculator it would be useful.

The other use is for example you want to create a form to generate HTML code for your visitors ie "to generate an HTML heading enter your title and press submit". Then in the admin you might create a form that has hidden fields

hidden_1 = "< h1 style="font-size: 28pt; color: red" >
[user-input-text]
hidden_2 = "< / h1 >"

then in the text area set it to text-area = hidden_1 + hidden_2

This would allow non-programmers to create simple interactive wizards and calculators.

Anyway just an idea. I find mpForm works very well and is very easy to use so thank you!
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Argos on November 23, 2012, 01:24:47 PM
The ajax drag/drop function in the latest version is not there in IE9.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Stefek on November 23, 2012, 03:12:43 PM
The ajax drag/drop function in the latest version is not there in IE9.
Yeah, I'll bet. They allways find a way to give you a pain in the *ss.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Argos on November 23, 2012, 03:22:44 PM
No, other browsers give us a pain in the ass by doing stuff that IE doesn't support  :roll:
Developers should make shure all works fine in IE, instead of focussing on those pesky other ones. IE is still by far the most used browser, especially in business use. You cannot ignore that as a developer, simply because you don't like the browser. Well, actually, you can, LOL. But that's another (endless & useless) discussion...  :wink:
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Jacquine on November 30, 2012, 11:53:15 AM
Hi all,
I tried to use this module on the website am working on.
When I click on the Add field button is given me this error

Cannot modify header information - headers already sent by (output started at /home/..../public_html/...../include/phplib/template.inc:668) in /home/.....r/modules/mpform/add_field.php on line 54

this is the code in add_field.php

(WB_VERSION >= "2.8.2") ? $fid = $admin->getIDKEY($field_id) : $fid = $field_id;
// Say that a new record has been added, then redirect to modify page
$sUrlToGo =  WB_URL.'/modules/mpform/modify_field.php?page_id='.$page_id.'&section_id='.$section_id.'&field_id='.$fid.'&success=add';
if(!$database->is_error()) {   
   #$admin->print_success($TEXT['SUCCESS'],);
   header("Location: ". $sUrlToGo);
   } else {   
   $admin->print_header();
   $admin->print_error($database->get_error(), $sUrlToGo);   
   $admin->print_footer();
}

 I am new to website baker and have check all the previous comment no solution.
Please help.
Thanks
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Stefek on December 01, 2012, 12:08:06 PM
You probably use WebsiteBaker in a version prior to 2.8.3
In that case you'll need to upgrade the CMS.

Kind regards,
Stefek
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Jacquine on December 03, 2012, 02:09:38 PM
Thanks Stefek, I have fixed it.
Regards
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Argos on December 04, 2012, 11:47:07 PM
The ajax drag/drop function in the latest version is not there in IE9.

I also found out that the delete function doesn't work in IE9. You can add a field, but not delete it.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: quinto on March 03, 2015, 10:23:19 PM
hello, in v1.1.7.9 there's a bug preventing correct display of the css for error messages :
in the file paintform.php at line 185 :
Code: [Select]
            echo '<div class="'.MPFORM_CLASS_PREFIX.'"missing">'.$msg.'</div>';

code fix is :
Code: [Select]
            echo '<div class="'.MPFORM_CLASS_PREFIX.'missing">'.$msg.'</div>';
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on March 05, 2015, 04:48:43 PM
Hi quinto,

thank you for the bug report. I'll update the module. I have two more fixes (one of them a quite similar issue) reported in the German thread. I was just waiting for while to collect things before I release a new version.

Kind regards,
Martin
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: quinto on March 05, 2015, 06:58:38 PM
Hi quinto,

thank you for the bug report. I'll update the module. I have two more fixes (one of them a quite similar issue) reported in the German thread. I was just waiting for while to collect things before I release a new version.

Kind regards,
Martin

hello I'm currently working on the french translation of mpform (90% done), i will publish my work on this thread once finished.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on March 05, 2015, 09:19:49 PM
Hi quinto,

I have posted an updated mpform-package in the German thread:
http://forum.WebsiteBaker.org/index.php/topic,24617.msg195802.html#msg195802

shall I wait for the French translation before I updating the Add-ons repository?

best regards,
Martin
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: quinto on March 06, 2015, 12:31:49 AM
Hi quinto,

I have posted an updated mpform-package in the German thread:
http://forum.WebsiteBaker.org/index.php/topic,24617.msg195802.html#msg195802

shall I wait for the French translation before I updating the Add-ons repository?

best regards,
Martin


My translation will be finished tomorrow, i noticed a forgotten word in the template file "backend_modify_sett ings.htt" (word "Layout" at line 55), this word must be converted in a template placeholder and its should be reflected in all the language files of mpform.
Are you agree if i make myself this correction on the last version taken from the german thread and then i send you the corrected version (with the fr language files plus the fix i suggested about "backend_modify_sett ings.htt") ?

i think it won't be long..
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on March 06, 2015, 10:12:47 AM
My translation will be finished tomorrow, i noticed a forgotten word in the template file "backend_modify_sett ings.htt" (word "Layout" at line 55), this word must be converted in a template placeholder and its should be reflected in all the language files of mpform.
Are you agree if i make myself this correction on the last version taken from the german thread and then i send you the corrected version (with the fr language files plus the fix i suggested about "backend_modify_sett ings.htt") ?

i think it won't be long..
ok, perfect. thanks for your contribution to the mpform module.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: quinto on March 06, 2015, 12:05:35 PM
hello, here are the version 1.1.8.2b of mpform (in attachment):

here are the improvements :

Quote
*** 1.1.8.2 BETA (Quinto: 06-Mar-2015) ***
        added FR.php language file
        bugfix in backend_modify_sett ings.htt and in all the language files (placeholder {TXT_LAYOUT_SETTINGS} added)

Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on March 06, 2015, 09:59:26 PM
Hi Quinto,

I have updated my templates and added you to the list of authors. Merci bien pour la traduction en Francais!

Martin

http://forum.WebsiteBaker.org/index.php/topic,24617.msg195833.html#msg195833
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: quinto on March 07, 2015, 12:39:47 AM
Hi Quinto,

I have updated my templates and added you to the list of authors. Merci bien pour la traduction en Francais!

Martin

http://forum.WebsiteBaker.org/index.php/topic,24617.msg195833.html#msg195833

ooops, i found another little bug (unclosed html tag on default success text) here the fix :
in file "add.php" at lines 54 and 55
Code: [Select]
$success_text = '<div class="mpform_results">Thank you for submitting your data. We received the following data:<br />{DATA}
<br />';
replace it by
Code: [Select]
$success_text = '<div class="mpform_results">Thank you for submitting your data. We received the following data:<br />{DATA}
<br /></div>';
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on March 07, 2015, 01:39:31 PM
Hi Quinto,

Ruud has already uploaded it to the Addons repository. Often this tracks quite some attention to the module and many people update it in their web pages.  I'd suggest that we wait a bit for further feedback before releasing another version.

Anyhow, I have updated my sources. Thanks for reporting.

best regards, Martin
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on March 30, 2015, 10:08:19 PM
since I have received no other feedback in the meantime, I have decided to issue a new release which simply adds this missing closing 'div'-tag. It's in the addons-repository now.
Title: mpForm Module Upgrade (Version 1.1.10)
Post by: Martin Hecht on July 13, 2015, 01:24:56 PM
Please find attached an updated version of mpform.

This version fixes several security issues (for details see the changelog).

Thanks to instantflorian for testing and for reporting some of these issues.
Title: mpForm Module Upgrade
Post by: Martin Hecht on July 18, 2015, 10:46:05 PM
Hi,

in the German forum dbs has reported about a problem introduced in the latest version of the mpform module when saving the settings. All quotes are prepended by a backslash when saving the settings, because I was a bit too enthusiastic about sanitizing the database queries against sql injections. The values at this place were already properly escaped. So, I have reverted that change and posted a new version 1.1.11 of mpform here:

http://forum.WebsiteBaker.org/index.php/topic,28496.0.html

due to the new forum rules, according to which this thread is for support only, I have created a new thread in the development area. Please subscribe to the new thread in order to be informed about future updates.

Martin
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: noname8 on February 15, 2016, 06:52:58 PM
Hello!
Thanks for your great module!

Is it possible for you to add some kind of logic that the there will be REPLY-TO address place also in the settings.

This is because some anti-spam checks stops mail if the sender email is invalid or from another server.
And i'd still like to hit the reply button for the customer's email to reply him.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on February 16, 2016, 11:59:26 AM
Hello,

The "reply-to" field is currently filled with the same email address as the from field (if the php mailer supports this). The from field is filled from the field of type "email Address".
If you use this already, and the email you receive has that "from", but no "Reply-To" header, it probably means that your server doesn't support that.
On my hoster it works but my email-client doesn't display the 'Reply-To" header (probably because it is identical with the From-field.

However, I don't know if I have understood your problem correctly. I could add a new field type for the Reply-To field which is used instead of the from-field when such a field is present. Would that help for your use-case?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on February 21, 2016, 08:29:12 PM
Hi noname8,

after a closer look at the source code, it actually was easier to implement an additional settings field.
I have published the updated version 1.1.20 ("1.1.twenty" not to confuse with 1.1.2) in this new development thread:
http://forum.WebsiteBaker.org/index.php/topic,28496.msg203376.html#msg203376

I hope this is what you were looking for.
 
best regards,
Martin
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: tobyw7 on June 29, 2016, 08:47:13 PM
Hello,

The captcha currently isn't loading on my contact form using this module, showing page not loading in the captcha box.

Anyone else?   :-(
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on June 29, 2016, 10:51:41 PM
please go for a check to admintools -> captcha settings (Captcha and Spam-Protection (ASP) Control) and try there the different settings in the select box. two of them shows the captcha picture after saving the setting

(https://i.gyazo.com/5f18b76850f4ec878d2a363b0c6ba27a.png)

if you dont see the captcha there, its possible, that the php-plugin gd-library not loaded on your server. you see it also in your server settings (phpinfo() like this in the next picture. if you confirm, that the gd-lib is loaded/enabled, we can look to mpform

(https://i.gyazo.com/2e7084bf778cb16473a01995e363c24c.png)
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: tobyw7 on July 14, 2016, 08:12:30 PM
Hi,

Thanks for the reply and delay in mine... I have checked and the captcha from admin tools seems to be loading.

I have uploaded a zip of screen shots which hopefully help?

I loaded the frame in a new tab and the full link is http://include.com/captcha/captcha.php?display_captcha_X98 6E21=1&s=10 (http://include.com/captcha/captcha.php?display_captcha_X986E21=1&s=10)

Hope that helps?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on July 14, 2016, 11:31:13 PM
Quote
and the full link is http://include.com/captcha/captcha.php?display_captcha_X98 6E21=1&s=10

maybe a link-error in your posting?
my link to the image is
http://www.domain.com/web/wb1/include/captcha/captchas/calc_ttf_image.php?t=1468530153

or to the captcha.php -> http://www.domain.com/web/wb1/include/captcha/captcha.php?display_captcha_... ....

web/wb1/ are two subfolders here

to the process
the view.php of the form module included the file /include/captcha/captcha.php and generated on the bottom of the form the captcha with the function call_captcha().
the file framework/initialize.php read the captcha settings and submitted this to the same file /include/captcha/captcha.php
this file loads now the selected file and build the image.
your backend use the same procedure in the captcha settings and builds and shows the images there.

is it possible, that your admin-url (Backend-login) is different to the frontend-url (WB_URL), maybe with and without www?
if its possible for you, make a right mouse-click on this captcha-image in the frontend-form and there to "examining element" like my picture here.
there you see the path to the image. copy that path and compare it with the path from the image in admin tools -> captcha settings

(https://i.gyazo.com/cec13352a015b0e256543b758c5e5e28.png)

if you need more help, send my a link to the problem
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: tobyw7 on July 30, 2016, 12:36:36 PM
I have checked again. When I go to the Admin Tools page, the captcha link here reads as http://frantik-web.co.uk//include/captcha/captchas/ttf_image.png and location is http://www.frantik-web.co.uk//include/captcha/captcha.php?

I checked the element and this is the link when going to inspect it;
Code: [Select]
<iframe class="captcha_iframe" style="overflow:hidden;border: 1px solid #999;" name="captcha_iframe_10" src="//include/captcha/captcha.php?display_captcha_X986E21=1&amp;s=10 " height="75" width="185">
                        <img src="//include/captcha/captchas/ttf_image.php?t=1469874596&amp;s=10" alt="Captcha" style="margin: auto;padding:  0;" />
                        </iframe>

I noticed yours had the full URL on the frontend?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on July 31, 2016, 01:59:18 PM
@tobyw7 - is it possible, that you work with activated REL_URL-Filter?? See AdminTools -> FrontendOutputFilte r
this filter works only in the frontend and remove the WB_URL to build relative links

Quote
http://frantik-web.co.uk//include/captcha/captchas/ttf_image.png

remove the ending slash on your WB_URL in config.php
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: tobyw7 on July 31, 2016, 02:07:41 PM
Okay, great  :-D

I did have the RELURL filter enabled, so I disabled that now. The captcha is working!!

I also removed the trailing / from the WB_URL

Thank you for your help!
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on July 31, 2016, 06:57:57 PM
Quote
I did have the RELURL filter enabled

i know
its standard after installation or upgrade. Problem was here the double Slash from the WB_URL at the beginn of this link to the captcha-image. a double slash inside of a URL is no problem for the most browsers, if there is a domainname in the front, but a double slash at the begin  is not a valid url

now, after removing the ending slash in your WB_URL, you can activate the REL-URL-filter again, if wished

 
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: tobyw7 on August 03, 2016, 08:01:50 PM
Ah great :)

I'll enable that again then in that case!
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: noname8 on September 06, 2016, 09:10:43 AM
I have 1.1.17 version of this
and wb is 2.8.3? from beginning of this year
captcha is enabled

I made 2 pages (hidden, wysiwyg containing also mpform section) to work in the multi-page form way
1. form ("Has a predecessing form: Yes", "Following page: form page 2")
2. form page 2: Has a predecessing form: No, "Following page: none")

When submitting 1. form it just reloads with hash added #wb_section_67 into url
Also tried without captha and still the page just reloads and does not even show errors or anything
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on September 06, 2016, 11:15:40 AM
I made 2 pages (hidden, wysiwyg containing also mpform section) to work in the multi-page form way
1. form ("Has a predecessing form: Yes", "Following page: form page 2")
2. form page 2: Has a predecessing form: No, "Following page: none")
If I'm not completely confused about the English language, it should be the other way round:
The first form has no preceding form, but the following page is the second form page.
The  second page has a preceding form, and maybe another "thank-you" page as following page.

BTW, recently I have updated the module and also the documentation (see the  Development Thread (http://forum.WebsiteBaker.org/index.php/topic,28496.0.html))

@DV: Maybe this thread here (the one containing the message that I'm writing at the moment) could be closed, because the new version of mpForm could be considered nearly a rewrite of the module, and development continues in the above mentioned thread, so please subscribe to that one to stay informed
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: noname8 on September 06, 2016, 01:15:35 PM
I made 2 pages (hidden, wysiwyg containing also mpform section) to work in the multi-page form way
1. form ("Has a predecessing form: Yes", "Following page: form page 2")
2. form page 2: Has a predecessing form: No, "Following page: none")
If I'm not completely confused about the English language, it should be the other way round:
The first form has no preceding form, but the following page is the second form page.
The  second page has a preceding form, and maybe another "thank-you" page as following page.

BTW, recently I have updated the module and also the documentation (see the  Development Thread (http://forum.WebsiteBaker.org/index.php/topic,28496.0.html))

@DV: Maybe this thread here (the one containing the message that I'm writing at the moment) could be closed, because the new version of mpForm could be considered nearly a rewrite of the module, and development continues in the above mentioned thread, so please subscribe to that one to stay informed

Thanks!

I got it somehow working when disabling preceeding option from the 1.st

Where is that option even used ?
I can still go directly to page2 and after the 1.st form the email is sent imediately..
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on September 06, 2016, 10:25:00 PM
I got it somehow working when disabling preceeding option from the 1.st

Where is that option even used ?
it's used on all other pages of a multipage form such that these pages reuse the session and don't start a new entry in the results table.
Quote
I can still go directly to page2 and after the 1.st form the email is sent immediately..
the email is always sent when a form is submitted (provided that you have enabled email-notifications), and the email contains only the fields from the current page.
With the mpform 1.2 series you have the possibility to add hidden fields to the second page. In the private.php you can insert the values submitted by the first page into these hidden fields. This way you can construct such a multipage form with email submission of all fields. Admittedly, it is quite some effort... maybe it's easier to disable the mails from the module and send them   in private_function_on _success and query the whole submission again from the database. Of course this needs a bit of coding. 
I have put it on my todo list to include an example in one of the next releases.
Title: multipage forms with mpform
Post by: Martin Hecht on October 16, 2016, 12:51:24 AM
In the latest Version 1.3.0 (http://forum.WebsiteBaker.org/index.php/topic,28496.msg207078.html#msg207078) of mpForm I have addressed these shortcomings we have discussed here before: The following pages can only be accessed after the preceding form page has been submitted successfully. Mails sent at the end of a multi page form contain the whole data of all preceding pages now. So, no need for lengthy explanations how to hand through the submissions... Ah, and by the way, you should disable the mail options on all other pages except for the last page
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: noname8 on October 16, 2016, 07:02:03 PM
Thanks!

If i make long form, lets say 5 pages, i know it's complicated to code it so that the last page will send everything.
For my purpose, i think i will use only one large mpform, and the separators / headers ? in between.
Then use jquery & bootstrap to dynamically convert those separators into tabs in one php-page.
That way user can move back and forward without POST warnings and other stuff. Perhaps it could be done also in php, but I think it's more easy with jquery.
It might be difficult to do, but I'll let you know how it goes after the work is done..
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on October 16, 2016, 10:23:36 PM

If i make long form, lets say 5 pages, i know it's complicated to code it so that the last page will send everything.
Maybe I wasn't that clear in my previous post: you don't have to worry about handing through the data to the last page anymore. In the mpform 1.3 series each page appends its data to a variable in the users session and the last page simply has to send the email. In prior versions it was complicate to code, but now it should be sufficient to switch off email notifications on all pages except for the last one.

Quote
For my purpose, i think i will use only one large mpform, and the separators / headers ? in between.
Then use jquery & bootstrap to dynamically convert those separators into tabs in one php-page.
That way user can move back and forward without POST warnings and other stuff. Perhaps it could be done also in php, but I think it's more easy with jquery. It might be difficult to do, but I'll let you know how it goes after the work is done..
If you still decide to go in that direction, the wizard for "conditional blocks" might be useful for this task, especially for a div-based layout.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: noname8 on November 25, 2016, 08:13:33 PM
I got this to work now with using one long form (just initial tests, not ready yet) and using jquery to append and wrap each fieldset into separate jquery tab.
It's working nicely at the moment but needs alot more programming.

How ever, i have problem.
Chrome console show in page admin edit this
Code: [Select]
Uncaught Error: cannot call methods on sortable prior to initialization; attempted to call method 'serialize'(…)
So the sorting of the fields do not work.

I'm using baker 2.8.3 and some SP, cannot remember which one..
and it's modification of "advancedThemeWbFlat" as admin template.
it has jquery version of /*! jQuery v1.11.1 | (c) 2005, 2014 jQuery Foundation, Inc. | jquery.org/license */
which works fine in other sites i have made earlier.

What could be the problem ?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on November 28, 2016, 03:40:34 PM
How ever, i have problem.
Chrome console show in page admin edit this
Code: [Select]
Uncaught Error: cannot call methods on sortable prior to initialization; attempted to call method 'serialize'(…)
The error console at least in firefox tells you the exact line where the error occurs. This would be helpful for finding the root cause of this. Also, the version of the module you are currently using would be important.

Anyhow,  I believe that I have fixed this error in one of the recent versions, maybe some of the 1.2 or 1.3 releases (at least it somehow sounds familiar to me). There was some debugging code which one of the previous maintainers had left in the module and which started to cause trouble either with newer jQuery versions or with stricter implementations in modern browsers. The solution was just to remove that code. It did prepare something which was meant to be printed out, but the final alert that has shown the content of the variables was commented out anyway.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: noname8 on November 29, 2016, 09:13:56 PM
Yes, thank you
that was the problem, error was triggered in jquery.js
but now i saw the anonymous function:

What could i do here ?

https://snag.gy/920mQ4.jpg


CMS Versie 2.8.3 SP5
Revisie 1644

How ever, i have problem.
Chrome console show in page admin edit this
Code: [Select]
Uncaught Error: cannot call methods on sortable prior to initialization; attempted to call method 'serialize'(…)
The error console at least in firefox tells you the exact line where the error occurs. This would be helpful for finding the root cause of this. Also, the version of the module you are currently using would be important.

Anyhow,  I believe that I have fixed this error in one of the recent versions, maybe some of the 1.2 or 1.3 releases (at least it somehow sounds familiar to me). There was some debugging code which one of the previous maintainers had left in the module and which started to cause trouble either with newer jQuery versions or with stricter implementations in modern browsers. The solution was just to remove that code. It did prepare something which was meant to be printed out, but the final alert that has shown the content of the variables was commented out anyway.


Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on November 30, 2016, 03:09:57 PM
well, you could update mpform to a more recent version in which these problems are fixed.

...or simply remove the line where sDataString is defined (it was only used in the alert which anyway was commented out)
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: zirzy on May 05, 2017, 11:16:44 AM
Hi,

I have upload limit 50mb and now 9mb file don't upload, why? Earlier bigger files uploaded correctly..
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on May 05, 2017, 12:20:55 PM
maybe an PHP-Upgrade??

P.S.: its not only the upload-limit
- memory_limit (used memory)
- file_uploads (on/off - allow HTTP file uploads)
- post_max_size (max size of the body from a formular with all text + attachements)
- upload_max_filesize (maximum allowed size for uploaded files)
- max_file_uploads (maximum number of files that can be uploaded via a single request)
etc....
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: zirzy on May 05, 2017, 12:32:58 PM
So there has been php upgrede on server provider or wb needs better php version?  :-o What?  :lol:
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: zirzy on May 05, 2017, 12:33:53 PM
Same problem is with miniform upload..
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on May 05, 2017, 01:08:07 PM
wb has nothing to do with this - wb use the php-settings. the latest wb-version (and the delivered modules) can work with the latest php-version, no problem - not sure about other modules

example: if your provider updated your php-version, you've also new settings in php-ini. a upload_max_filesize with 50mb is not a standard setting, default is 8mb, post_max_size must be equal or higher, default is also 8mb. check all this settings in a phpinfo, simple code example

<?php
phpinfo();
?>

if you dont have a addon like Ruud's phpinfo (https://dev4me.com/modules-snippets/opensource/phpinfo/) or systeminfo (https://dev4me.com/modules-snippets/opensource/sysinfo/), copy that code, add it in a empty file, save it as info.php , upload it to your server and call it in your browser

P.S.: only a tip: if something on your website doesnt work, but it works in the last visit, and YOU have not changed anything since the last visit, looks, what is different - in the most times a server upgrade (new php- or mysql-version's with new settings
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: zirzy on May 05, 2017, 01:43:10 PM
Ok, I uploaded that phpinfo module. Where or which row can I see max file upload? Is it max_file_uploads?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on May 05, 2017, 01:54:52 PM
Quote
Is it max_file_uploads?

yes, it is - search in the left row to the key names (like max_file_uploads or the others from my first answer) - use also the browser-search with STRG + F
in the middle row the default setting from the server, in right row the setting for this account

Edit: the middle row shows the locale settings for this server only, the right row the general php-settings
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: zirzy on May 05, 2017, 02:00:26 PM
Ok, I try to do that. Thanx buddy (Y)

If php.ini max upload is 8mb, how can I change it to let's say 50mb?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on May 05, 2017, 03:01:48 PM
If php.ini max upload is 8mb, how can I change it to let's say 50mb?

directly in your server settings, but not every server give the access to this option or to this special setting.
maybe you use Google etc, to search for it, maybe in combination "your provider + change php.ini" (for example)
maybe its also allowed, to use a own/private php.ini to set this options temporally

here a screenshot from the view, left row the key name, called as "directive", middle row the locale setting with a possible private php.ini, right row the default setting from the php.ini

thread is here: Core
(https://i.gyazo.com/916320c0a88aa57b9c947629d24aede2.png)
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: zirzy on May 11, 2017, 12:31:55 PM
Seems like max upload is 128m in php.ini..

(https://preview.ibb.co/g7mgt5/Sieppaa.png) (https://ibb.co/n9QwRQ)


What next?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Ruud on May 11, 2017, 12:51:13 PM
There is a second on that overrides the max_file_size:  post_max_size

This setting defines the total POST size.. where max_file_size sets the maximum per file.


Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: jacobi22 on May 11, 2017, 01:01:35 PM
see also my post here -> http://forum.WebsiteBaker.org/index.php/topic,24658.msg211158.html#msg211158 and check this settings

P.S.: mpForm has a own upload-size-setting - do you see it in the advanced settings?
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: zirzy on May 12, 2017, 12:32:04 PM
- memory_limit 192
- file_uploads on
- post_max_size 8
- upload_max_filesize 128
- max_file_uploads 20


So that post_max_size is 8mb.. I must take a contact with service provider.
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: zirzy on May 17, 2017, 01:10:59 PM
Yes, now post_max_size is set to 60M and file upload is working correct again. Thanx for your help  (Y) 
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Roych on August 21, 2017, 11:53:41 AM
Hello,


I've just updated the MPform to the latest 1.3.9 from repository, it is working fine but the exported submitions are a complete mess. The questions should be in a first (header) row and separated in columns. Submitions should be in a columns, right? Mine looks like a mess. The questions are all in one column and some of them has a name (Fieldxx) not the real name. and submitions are all in a same column. Submition rows are working every submition in it's own row.


So it is really hard to read through submitions. Any fix for that maybe. I tried looking on a forum but no success.


Thank you
R
Title: Re: mpForm Module Upgrade | version 1.1.2 (EN thread)
Post by: Martin Hecht on August 21, 2017, 10:33:15 PM
Hello Roych,

the export of the submissions is simply a csv dump of the results table, where the columns have been re-ordered according to the current position of the fields. The structure of this results table may become messy over time when you create, delete and move fields. There may be columns left over from fields which have already been deleted, and if you have upgraded just recently, there may even be columns missing for fields that were added after the first submission.

In recent versions of mpform you can clean that up quite easily: Just open the general settings, and save them again, without changing anything. By doing so, the missing columns should be re-created.

Obsolete columns however are not removed. If you want to do that, you can change the results table suffix. Old submissions however are not moved to a new table with that suffix, but this would be an easy way to start from a fresh table for future submissions.

Please let me know if these steps helped you to clean up the mess that you have described. If the "mess" persists, do you see a chance that you can create an sql dump of your mpform tables and share them with me (preferably by email) so that I can have a look what exactly is causing the trouble in your case?

kind regards,
Martin