WebsiteBaker Support (2.13.x) > General Help & Support
Problems with mpForm 1.3.4x
hgs:
--- Quote from: mikejd on November 10, 2022, 01:37:10 PM ---I have recently been updating one of these sites and have updated WB to the latest version, v2.13.1. Many of the additional modules unfortunately have not been updated for some years. I have updated a couple, e.g. MPForm and Topics, to the latest versions listed but have found that it appears that they no longer function in the same way that they did. I have been in contact with the developers to try to address some difficulties. I think some of the problems might relate to the updating of WB no longer supporting all pre-existing modules.
--- End quote ---
Which version of mpForm are you working with?Here running mpForm 1.3.40 with the latest WebsiteBaker 2.13.2 with php 8.1
The rest has crnogorac081 already explained and in a few days the next stage of php comes with version 8.2.
mikejd:
@hgs
I am using MPForm 1.3.42 with WB 2.13.0.
The latest form I have produced looks fine but trying to submit just produces an error with Mailer. This also now happens with a previous form which used to work OK. I have been in contact with Martin Hecht, the developer, who has been trying to sort the issue but he is having to set up a complete WB installation to be able to test it.
It has been suggested to try another CMS, WBCE, which is a branch of WB. However it seems that this may have been easy to convert to from WBv2.8 but not from v2.13. I am also not sure I want to spend the necessary time to learn this.
I have just received another MPForm update from Martin which I shall be trying shortly.
hgs:
Please attach Martin's new version here so we can test that too.
Thank you.
But it doesn't make much sense to test it with an outdated WB version.
Current version of WB is 2.13.2 r133
Martin Hecht:
The WBMailer has been moved into another namespace and at a different location. I have added code to take this into account, but I might have misunderstood the WB developers messages - or they have changed their plans afterwards.
In addition there is a problem with the phplib template engine, which doesn't support php > 8.0 properly. I ran into these phplib problemes yesterday with php 8.1. I should give 8.0 a try, but still it's not clear to me how to call the wbmailer in WB 2.13.2. Attached is my latest approach to address this (the version that Mike has tested).
@hgs, if you have mpform 1.3.40 running with WB 2.13.2 and php 8.1, I would assume that there were either some (little) changes needed, or you just didn't stumble over the problems (yet) - frontend and backend looks ok at the first glance, but e.g. changing settings didn't work for me with php8.1, and Mike has run into the problem that the wbmailer is not working
hgs:
ok, I have updated the test page with mpForm.
There was this success message:
--- Quote ---Updating database for module: mpForm
Adding new fields to the settings table
Adding new fields to the fields table
Search function updated successfully
Adding new field(s) to the submissions table
Adding putting css files in place
Module mpForm updated to version: 1.3.42.1
--- End quote ---
In the backend I added a field, the error message looks like this:
--- Code: ---"created: [Fri, 11 Nov 2022 13:05:56 +0000]
Fri, 11 Nov 2022 13:06:00 +0000 [E_DEPRECATED] /modules/mpform/save_field.php:[448] from /modules/mpform/save_field.php:[448] str_replace "str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated""
--- End code ---
In the frontend I was able to submit the form.
Addendum:
When submitting it still comes up this ErrorLog
--- Code: ---Fri, 11 Nov 2022 13:10:27 +0000 [E_USER_DEPRECATED] /framework/class.wb.php:[537] from /framework/class.wb.php:[537] trigger_error "invalid method call: bin\wb::get_user_id change it to getUserId()"
--- End code ---
to fix in this file
--- Code: --- mpform-1.3.42.1\evalform.php (2 hits)
Line 460: if(isset($admin) AND $admin->is_authenticated() AND $admin->get_user_id() > 0) {
Line 461: $submitted_by = $admin->get_user_id();
--- End code ---
2nd addendum
For the phplip template problem this line at the beginning of the template section should help, so the module is usable in both worlds
--- Code: ---if (!class_exists('Template')){ require(WB_PATH.'/include/phplib/template.inc');}
--- End code ---
Navigation
[0] Message Index
[#] Next page
Go to full version