Author Topic: mpForm  (Read 8485 times)

Offline jacobi22

  • Posts: 5836
  • Gender: Male
  • Support also via PM or EMail
    • Jacobi22
Re: mpForm
« Reply #75 on: July 29, 2016, 02:00:54 PM »
please look into the zip-file from your last here  ;-)

a screenshot from add.php, the php-section starts here in line 37. in some file are shorter text, in other are longer text, but its in nearly every file



i think, the captcha-patch is not longer needed. if i remember correct, the problem exist only in 2.8.3 (Rev 1611) and 2.8.3 SP1 (Rev 1638) and was fixed in the next versions

P.S.:  a very big image... sorry, but i cannot change the image size :|
Probleme sind da, um sie zu lösen, nicht, um nach Ausreden zu suchen.

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
Re: mpForm
« Reply #76 on: July 29, 2016, 02:34:40 PM »
oh, damned, something in the build process went wrong. Also the link to the documentation in the backend didn't correctly redirect.
both is fixed in the attached version. sorry, it was late yesterday
« Last Edit: September 20, 2016, 03:46:20 PM by Luisehahne »

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
mpForm Update
« Reply #77 on: August 02, 2016, 10:53:34 PM »
I have received the feedback that in the new private.default.php a curly brace was missing.
This is fixed in the final version of the 1.2 branch now.
Also I have noticed that the help link in the backend didn't work correctly under all circumstances.
I have pushed the release to github now:

https://github.com/WebsiteBaker-modules/mpform/releases/tag/1.2.1

From there you can download a full package which includes the module and the documentation in German and English.
Unfortunately I can't post such a zip file here due to the limitation of the forum settings.

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
mpForm update
« Reply #78 on: August 21, 2016, 12:18:57 AM »
I have updated mpForm on the github repo:
https://github.com/WebsiteBaker-modules/mpform/releases/tag/1.2.3

for convenience I have also attached the (smaller) zip archive which does not include the documentation (However, there were no changes to the docu this time), just a few minor fixes to the code:

  -      fix query for position in upgrade script, thanks to norhei for reporting
  -      fix drag and drop in ajax helper, thanks to florian for reporting
  -      honor redirection_timer in ajax notifications, thanks to florian for this hint
  -      two typo fixes in view_submissions, thanks to norhei for reporting

Cheers, Martin

Offline noname8

  • Posts: 145
Re: mpForm
« Reply #79 on: October 11, 2016, 10:14:57 AM »
I upgraded from old version 1.1.17
and worked nice, but missed couple images, import.png, export.png
but found those from the master, thanks!

Offline jacobi22

  • Posts: 5836
  • Gender: Male
  • Support also via PM or EMail
    • Jacobi22
Re: mpForm
« Reply #80 on: October 11, 2016, 11:24:28 AM »
i add this pictures to the Download-Version in Addon-Area -> http://addon.WebsiteBaker.org/pages/en/browse-add-ons.php?id=0A702411
Probleme sind da, um sie zu lösen, nicht, um nach Ausreden zu suchen.

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
Re: mpForm
« Reply #81 on: October 11, 2016, 04:06:50 PM »
...but found those from the master, thanks!
yes, the github is a little bit beyond the 1.2.3 version published here. Based on the feedback that I have received I'm currently working  on a new release which will hopefully be ready soon.

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
mpForm Update
« Reply #82 on: October 16, 2016, 12:16:02 AM »
I have prepared a new version of mpForm:

Release Notes for mpForm 1.3.x

General Changes
---------------
By default switched to a div-based layout. All pages created with earlier versions
of course keep their layout as it is (by default it was a table based layout in the past)

The style file has been cleaned up and a few new definitions have been added
for the help popup dialog in div-based layout. Remember to copy the default style
files manually (or merge the changes into your local modifications) in order to
pick up the improved style settings.

New Features
------------
In multi page forms the access to following pages is denied to all following pages
unless the previous page has been submitted successfully

Feature Improvements
--------------------
In multi page forms submissions are handed over between the individual pages so that
the last page can send confirmation mails about all the submissions of the current page
and now also all previous pages. The data is stored in the session indexed by the
submission id and could in principle be used in the private functions as well.

The {HELP} placeholder works not only in table based layouts, but in general now.

French and Italian language support did not cover the error messages in the pear
file uploader tool. These missing language files have been added now.

Security Enhancements
---------------------

IDKEYs were not used throughout the module. In fact they were only used when
Javascript and therefore Ajax was disabled. Now the Ajax-Helpers also use IDKEYs.
Also the Noscript-fallbacks for moving fields up and down use IDKEYs now.

Documentation
-------------
The feature changes described here are also reflected in the documentation.
The standard forms have also been updated and are based on div-layout now.

Bug fixes
---------
In the 1.2.x releases the icons for import/export for these buttons have been missing.
Now they are included in the module package.

The ajax drag&drop helper did use a wrong url for a icon in one of the message boxes.
It has been corrected now.

A few other minor fixes in Ajax-Helpers, and their Noscript-fallbacks.

Due to the limitations of the forum I have to provide the documentation in a separate zip Archive

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
Update of the German Documentation
« Reply #83 on: October 16, 2016, 12:17:35 AM »
here the updated German Documentation

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
Update of the English Documentation
« Reply #84 on: October 16, 2016, 12:19:08 AM »
and here the English documentation package

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
mpForm Update
« Reply #85 on: October 16, 2016, 12:35:34 AM »
the full package mpform 1.3.0 including the documentation is available at github now

Offline jacobi22

  • Posts: 5836
  • Gender: Male
  • Support also via PM or EMail
    • Jacobi22
Re: mpForm
« Reply #86 on: October 16, 2016, 10:31:35 AM »
Probleme sind da, um sie zu lösen, nicht, um nach Ausreden zu suchen.

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
Re: mpForm
« Reply #87 on: October 20, 2016, 09:42:01 PM »
I have just pushed an updated version to the github-repository

from the changelog (only changes between 1.3.0 and this release):
        add export for results table
        introduce constants.user.php and move the defaults for the field loop there
        let delete_submission.p hp also delete entries from the results table
        for this, also introduce submission_id in new results tables
        fix javascript bug in view_submission.php
        update documentation, especially the faq page

For a more prosa-like version see the description at the above-link. It is however a combined description of all changes in the 1.3.x branch with respect to prior versions.

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
mpForm Update
« Reply #88 on: December 08, 2016, 10:49:53 PM »
I have released a new version of mpForm on github.

here the changelog
        fix language files (thanks to florian for reporting)
        merge Bugfix for deleting fields in backend (Dietrich Roland Pehlke: 14-Nov-2016)
        added maxlength option for textareas (thanks to alexx for suggesting)
        add place holder {EMAIL} within mail templates (thanks to John for suggesting)
        introduce field templates to locally override the field loop if desired
        support mod_opf_Email as a replacement of the classical email output filter
        updated documentation in a few places and the hints in the backend
        highlight missing required radio/checkbox fields (thanks to alexx for reporting)
        keep uploaded files when returning to paintform (thanks to alexx for suggesting)
        correctly enclose  body in tags in html mails (thanks to astrid for reporting)
        add more css classes for more styling flexibility (gottfried, florian)
        insert newlines in xml export for better readability (request by gottfried)
        insert field number in backend overview (thanks to gottfried for suggesting)

cheers, Martin

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
mpForm Update
« Reply #89 on: December 21, 2016, 11:37:07 PM »
I have updated mpForm to Version 1.3.3 on Github

here the change log entry:

        *** 1.3.3 (Martin Hecht: 19-Dec-2016) ***
        fix the local template so that indeed all place holders are allowed there
        introduce {TEMPLATE1} ... {TEMPLATE9} for a single line of the local template
        correctly decode html special characters for html emails (thanks to astrid)
        allow to specify success_email_from by field or by logged on user (astrid)
        for consistency also allow to specify success_email_fromn ame by field
        fix missing single quote in most of the language files (thanks to colinax)
        allow to select multiple name fields for the sender name (astrid)
        allow place holders {FIELD...} in subject lines (request by astrid)
        fixed default form footer and correctly implement place holder {SUBMIT}
        correct the html code in the backend template for the basic settings
        offer a setting for user defined classes inside the fields and
        introduce place holder {FORMATTED_FIELD} in the field loop for that (florian, gottfried)
        avoid collision of the {TEMPLATE} place holder with the template for heading fields
        correctly detect if we use table layout or not for the output of headings
        repair update script to add the column for the field template (colinax)
        avoid multiply including the department in notification mails
        trim email_to when saving basic settings
        update documentation and example forms

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
mpForm Update
« Reply #90 on: January 30, 2017, 08:14:30 PM »
Hello,

I have just published an update for mpform on Github

implemented feature requests:
    allow use of {TEMPLATE} place holders in notification mails (request by gottfried)
    implement css for mails (to site owner and to submitter)
bugfixes:
    fix warning in disabled file upload fields (thanks to dbs for reporting)
    fix warning when saving fields

cheers, Martin

Offline hgs

  • Betatester
  • **
  • Posts: 1102
    • EFG MG
Re: mpForm
« Reply #91 on: January 31, 2017, 12:16:25 PM »
LG Harald

"Fange nie an, aufzuhören - höre nie auf, anzufangen." Marcus Tullius Cicero (106-43 v.Chr.)

Offline jacobi22

  • Posts: 5836
  • Gender: Male
  • Support also via PM or EMail
    • Jacobi22
Re: mpForm
« Reply #92 on: January 31, 2017, 11:00:43 PM »
@hgs: bitte vorher in das ZIP schauen. Das Paket von GitHub ist keine in WB installierbare Datei. Github baut systembedingt einen Ordner mit Modulnamen um die Dateien, der mit gezippt wird. Dadurch stimmt die Struktur nicht mehr, die WB und die Forks erwarten
Habe das Paket heute mittag ausgetauscht (31.01.17)

@ Martin: bitte in den nächsten Versionen übernehmen

evalform.php  ~Zeile 173
erstellt ein Sendeprotokoll mit eingeschaltetem DEBUG-Modus. Weitere Info in class.phpmailer.php * Zeile 318

Code: [Select]
$myMail->set('SMTPDebug', ((defined('DEBUG') && DEBUG)?2:0));    // Enable verbose debug output
$myMail->set('Debugoutput', 'error_log');

Nach Stand heute wird es mit der nächsten WB-Version Probleme mit mpForm geben  - aber möglich, das sich noch etwas ändert
Probleme sind da, um sie zu lösen, nicht, um nach Ausreden zu suchen.

Offline hgs

  • Betatester
  • **
  • Posts: 1102
    • EFG MG
Re: mpForm
« Reply #93 on: February 01, 2017, 08:32:33 AM »
Danke, bist der Beste. (Y)
LG Harald

"Fange nie an, aufzuhören - höre nie auf, anzufangen." Marcus Tullius Cicero (106-43 v.Chr.)

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
Re: mpForm
« Reply #94 on: February 01, 2017, 06:55:15 PM »
Hallo,

Github baut systembedingt einen Ordner mit Modulnamen um die Dateien, der mit gezippt wird. Dadurch stimmt die Struktur nicht mehr, die WB und die Forks erwarten
ja, leider. Aber man kann glaub ich den Link nicht so angeben, dass github das anders packen würde. Und hier im Forum gibt es das 512 kB Limit. Zusammen mit der Doku krieg ich das Modul nicht so klein gequetscht.

Quote
@ Martin: bitte in den nächsten Versionen übernehmen...
hab ich mir vorgemerkt

Quote
Nach Stand heute wird es mit der nächsten WB-Version Probleme mit mpForm geben  - aber möglich, das sich noch etwas ändert
kannst du mir Detials zukommen lassen? Was genau wird sich ändern und wie muss ich mpForm anpassen, damit es unter der nächsten Version noch läuft?

viele Grüße,
Martin

Offline jacobi22

  • Posts: 5836
  • Gender: Male
  • Support also via PM or EMail
    • Jacobi22
Re: mpForm
« Reply #95 on: February 01, 2017, 08:14:36 PM »
Github baut systembedingt einen Ordner mit Modulnamen um die Dateien, der mit gezippt wird. Dadurch stimmt die Struktur nicht mehr, die WB und die Forks erwarten
ja, leider. Aber man kann glaub ich den Link nicht so angeben, dass github das anders packen würde. Und hier im Forum gibt es das 512 kB Limit. Zusammen mit der Doku krieg ich das Modul nicht so klein gequetscht.

laß mal die Methode so, wie sie ist. Link zu GitHub posten reicht vollkommen.  (Y)
Probleme sind da, um sie zu lösen, nicht, um nach Ausreden zu suchen.

Offline DarkViper

  • Forum administrator
  • *****
  • Posts: 3015
  • Gender: Female
Re: mpForm
« Reply #96 on: September 28, 2017, 09:54:44 PM »
**push**
Der blaue Planet - er ist nicht unser Eigentum - wir haben ihn nur von unseren Nachkommen geliehen

"You have to take the men as they are… but you can not leave them like that !" :-P
Das tägliche Stoßgebet: Oh Herr, wirf Hirn vom Himmel !

Offline hgs

  • Betatester
  • **
  • Posts: 1102
    • EFG MG
Re: mpForm
« Reply #97 on: September 29, 2017, 07:48:30 AM »
neuste Version von mpForm 1.3.10 unter der neuen Version von WB erfolgreich getestet.
LG Harald

"Fange nie an, aufzuhören - höre nie auf, anzufangen." Marcus Tullius Cicero (106-43 v.Chr.)

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 581
  • Gender: Male
    • meine Homepage
mpForm
« Reply #98 on: September 29, 2017, 10:09:31 AM »
Hi,

nachdem der Foren-Thread jetzt wieder offen ist (Danke an DV), kann ich die von hgs erwähnte neue Version 1.3.10 auch ankündigen. Momentan gibt es sie auf github und man muss wie dort üblich erst die Dateien entpacken und in ein neues Zip mit flacherer Verzeichnisstruktur wieder einpacken.

Es sind ein paar Kleinigkeiten gefixt:

Beim Anlegen von Feldern sollte es nun egal sein, ob zuerst Feldname oder Feldtyp ausgewählt wurde. Das war zwar bisher auch der Fall, nur musste man nach Eingabe des Namens noch die Textbox mit dem Cursor verlassen (z.B. durch Drücken von TAB), um den Speichern-Button aktiviert zu bekommen. In der neuen Version reicht es auch, mit der Maus über den Speichern-Button zu fahren (was man ja macht, wenn man diesen anklicken will).

Das upgrade-Skript prüft jetzt am Anfang gleich ob die Konstante TP_MPFORM definiert ist und ob es eine dazu passende Settings-Tabelle gibt und gibt klare Fehler aus,wenn eines von beiden nicht erfüllt ist. Wenn jemand TP_MPFORM umdefiniert hatte und diese Einstellung beim Upgrade verloren ging, dann hat das in der Vergangenheit zu nicht ganz leicht verständlichen Fehlern geführt :-)

Ein Leerzeichen hat in der Ausgabe von Email Input Feldern im erzeugten HTML code gefehlt (github issue #4)

Eine Version des Moduls, bei der die Dokumentation nicht enthalten ist, hänge ich mit an diesen Post an (mit Doku wäre das Zip zu groß fürs Forum, aber an der Doku hat sich diesmal auch nix geändert).

Martin

Offline hgs

  • Betatester
  • **
  • Posts: 1102
    • EFG MG
Re: mpForm
« Reply #99 on: September 29, 2017, 11:53:00 AM »
LG Harald

"Fange nie an, aufzuhören - höre nie auf, anzufangen." Marcus Tullius Cicero (106-43 v.Chr.)

 

postern-length