Author Topic: mpForm und SP7  (Read 1049 times)

Offline astricia

  • Posts: 578
  • Gender: Female
    • netSchmiede24
mpForm und SP7
« on: September 19, 2016, 11:18:43 AM »
Noch mal, weil im falschen Forum gepostet.... sorry, das andere kann bitte gelöscht werden...

Hallo zusammen,

habe gerade noch ne Ungereimtheit entdeckt. Das Modul "mpForm" (das ich in einer Vielzahl von Domains eingesetzt habe), funktioniert unter SP7 nicht mehr. Es wird keine Mail mehr verschickt, man landet auch nicht auf der angegebenen Folgeseite, sondern z.B. auf http://domain.de/pages/kontakt.php#wb_section_41 (oder welche Abschnitt nummer auch immer).

Habe hier gesucht, ob das Thema schon mal behandelt wurde und das hier gefunden: http://forum.WebsiteBaker.org/index.php/topic,29175.msg204677.html

Ihr schreibt, dass die neuere Version 1.1.23 das Problem beheben würde. Die neuere Version würde man hier finden: http://forum.WebsiteBaker.org/index.php/topic,28496.50.html - hier finde ich aber auch Version 1.2.0 - was ich jetzt installiert habe.

Problem: Vor dem Kontaktformular wird jetzt der folgende Text angezeigt:
. Bug fixes --------- The results tables are correctly removed now, when a mpform section is removed. In the past unused results tables were kept in the database after removing the forms until one eventually uninstalls the module. This change also implies that you should make a backup of the submissions when you remove the form. The results table is of course kept in the case when multiple forms write to the same results table. General Changes --------------- Promised a long time ago and finally finished: The module works in sql strict mode now. In general the code has been reworked a lot. Long lines have been wrapped and properly indented for better readability of the code and to assist users when they try to identify a bug. It is not a complete rewrite of the code but nearly. Module specific global variables are not used anmore. Old code for WB 2.7 has been removed and code for backwards compatibility to versions of WB 2.8 earlier than 2.8.3 have been made consistent throughout the whole code. IDKEY and FTAN are two examples. These features are only used when the core supports them. In general it is not recommended to run old versions without such security features. But anyhow, in the previous versions of mpform, there were checks which allowed to run without them, but not in all parts of the module. When sending http headers to redirect the user to another page, there is an additional check now, if the headers have already been sent. If so, an alternative redirection link is presented to the user. This can help when other modules/snippets interfere with the way how the content is buffered or sent to the user.'). Bug fixes --------- The results tables are correctly removed now, when a mpform section is removed. In the past unused results tables were kept in the database after removing the forms until one eventually uninstalls the module. This change also implies that you should make a backup of the submissions when you remove the form. The results table is of course kept in the case when multiple forms write to the same results table. General Changes --------------- Promised a long time ago and finally finished: The module works in sql strict mode now. In general the code has been reworked a lot. Long lines have been wrapped and properly indented for better readability of the code and to assist users when they try to identify a bug. It is not a complete rewrite of the code but nearly. Module specific global variables are not used anmore. Old code for WB 2.7 has been removed and code for backwards compatibility to versions of WB 2.8 earlier than 2.8.3 have been made consistent throughout the whole code. IDKEY and FTAN are two examples. These features are only used when the core supports them. In general it is not recommended to run old versions without such security features. But anyhow, in the previous versions of mpform, there were checks which allowed to run without them, but not in all parts of the module. When sending http headers to redirect the user to another page, there is an additional check now, if the headers have already been sent. If so, an alternative redirection link is presented to the user. This can help when other modules/snippets interfere with the way how the content is buffered or sent to the user.'). Bug fixes --------- The results tables are correctly removed now, when a mpform section is removed. In the past unused results tables were kept in the database after removing the forms until one eventually uninstalls the module. This change also implies that you should make a backup of the submissions when you remove the form. The results table is of course kept in the case when multiple forms write to the same results table. General Changes --------------- Promised a long time ago and finally finished: The module works in sql strict mode now. In general the code has been reworked a lot. Long lines have been wrapped and properly indented for better readability of the code and to assist users when they try to identify a bug. It is not a complete rewrite of the code but nearly. Module specific global variables are not used anmore. Old code for WB 2.7 has been removed and code for backwards compatibility to versions of WB 2.8 earlier than 2.8.3 have been made consistent throughout the whole code. IDKEY and FTAN are two examples. These features are only used when the core supports them. In general it is not recommended to run old versions without such security features. But anyhow, in the previous versions of mpform, there were checks which allowed to run without them, but not in all parts of the module. When sending http headers to redirect the user to another page, there is an additional check now, if the headers have already been sent. If so, an alternative redirection link is presented to the user. This can help when other modules/snippets interfere with the way how the content is buffered or sent to the user.'). Bug fixes --------- The results tables are correctly removed now, when a mpform section is removed. In the past unused results tables were kept in the database after removing the forms until one eventually uninstalls the module. This change also implies that you should make a backup of the submissions when you remove the form. The results table is of course kept in the case when multiple forms write to the same results table. General Changes --------------- Promised a long time ago and finally finished: The module works in sql strict mode now. In general the code has been reworked a lot. Long lines have been wrapped and properly indented for better readability of the code and to assist users when they try to identify a bug. It is not a complete rewrite of the code but nearly. Module specific global variables are not used anmore. Old code for WB 2.7 has been removed and code for backwards compatibility to versions of WB 2.8 earlier than 2.8.3 have been made consistent throughout the whole code. IDKEY and FTAN are two examples. These features are only used when the core supports them. In general it is not recommended to run old versions without such security features. But anyhow, in the previous versions of mpform, there were checks which allowed to run without them, but not in all parts of the module. When sending http headers to redirect the user to another page, there is an additional check now, if the headers have already been sent. If so, an alternative redirection link is presented to the user. This can help when other modules/snippets interfere with the way how the content is buffered or sent to the user.'). Bug fixes --------- The results tables are correctly removed now, when a mpform section is removed. In the past unused results tables were kept in the database after removing the forms until one eventually uninstalls the module. This change also implies that you should make a backup of the submissions when you remove the form. The results table is of course kept in the case when multiple forms write to the same results table. General Changes --------------- Promised a long time ago and finally finished: The module works in sql strict mode now. In general the code has been reworked a lot. Long lines have been wrapped and properly indented for better readability of the code and to assist users when they try to identify a bug. It is not a complete rewrite of the code but nearly. Module specific global variables are not used anmore. Old code for WB 2.7 has been removed and code for backwards compatibility to versions of WB 2.8 earlier than 2.8.3 have been made consistent throughout the whole code. IDKEY and FTAN are two examples. These features are only used when the core supports them. In general it is not recommended to run old versions without such security features. But anyhow, in the previous versions of mpform, there were checks which allowed to run without them, but not in all parts of the module. When sending http headers to redirect the user to another page, there is an additional check now, if the headers have already been sent. If so, an alternative redirection link is presented to the user. This can help when other modules/snippets interfere with the way how the content is buffered or sent to the user.'). Bug fixes --------- The results tables are correctly removed now, when a mpform section is removed. In the past unused results tables were kept in the database after removing the forms until one eventually uninstalls the module. This change also implies that you should make a backup of the submissions when you remove the form. The results table is of course kept in the case when multiple forms write to the same results table. General Changes --------------- Promised a long time ago and finally finished: The module works in sql strict mode now. In general the code has been reworked a lot. Long lines have been wrapped and properly indented for better readability of the code and to assist users when they try to identify a bug. It is not a complete rewrite of the code but nearly. Module specific global variables are not used anmore. Old code for WB 2.7 has been removed and code for backwards compatibility to versions of WB 2.8 earlier than 2.8.3 have been made consistent throughout the whole code. IDKEY and FTAN are two examples. These features are only used when the core supports them. In general it is not recommended to run old versions without such security features. But anyhow, in the previous versions of mpform, there were checks which allowed to run without them, but not in all parts of the module. When sending http headers to redirect the user to another page, there is an additional check now, if the headers have already been sent. If so, an alternative redirection link is presented to the user. This can help when other modules/snippets interfere with the way how the content is buffered or sent to the user.')

Im Backend UND im Frontend!!!!!!

Die Version 1.1.23 (die ja offensichtlich davor gepostet wurde), kann ich jetzt nicht mehr installieren, weil die Versionsnummer kleiner ist - bekomme die Meldung "Bereits installiert".

Was tun?????

LG,
Astrid
Modify message

Offline dbs

  • Betatester
  • **
  • Posts: 7790
  • Gender: Male
  • tioz4ever
    • WebsiteBaker - jQuery-Plugins - Module - Droplets - Tests
Re: mpForm und SP7
« Reply #1 on: September 19, 2016, 11:56:37 AM »
Hi, in dem Thread ist ganz unten die Version 1.2.3, welche dein Darstellungs-Problem behebt. Die lässt sich also drüberinstallieren.

Wenn du unbedingt eine kleinere Versionsnummer installieren willst könntest du in deinem installierten mpform die Versionsnummer in der info.php einfach kleiner machen und dann normal die andere Version installieren.

Offline jacobi22

  • Posts: 5685
  • Gender: Male
  • Support also via PM or EMail
    • Jacobi22
Re: mpForm und SP7
« Reply #2 on: September 19, 2016, 11:59:31 AM »
Wozu gibt es einen Addon-Bereich, wenn keiner reinschaut?   :roll: :roll:

http://addon.WebsiteBaker.org/pages/en/browse-add-ons.php?filter=mpform&id=0A702411
Probleme sind da, um sie zu lösen, nicht, um nach Ausreden zu suchen.

Offline astricia

  • Posts: 578
  • Gender: Female
    • netSchmiede24
Re: mpForm und SP7
« Reply #3 on: September 19, 2016, 01:14:35 PM »
Ahhh... sorry.. hatte nicht gesehen, dass in dem Thread noch ne Seite dahinter ist.... ;-)

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 580
  • Gender: Male
    • meine Homepage
Re: mpForm und SP7
« Reply #4 on: September 20, 2016, 02:07:52 PM »
Wozu gibt es einen Addon-Bereich, wenn keiner reinschaut?   :roll: :roll:

http://addon.WebsiteBaker.org/pages/en/browse-add-ons.php?filter=mpform&id=0A702411
ah, cool, dass es dort inzwischen auch aktualisiert wurde.
Kann jemand das Zip-File mit der verkorksten 1.2.0 hier im Forum löschen? Mir fehlt da leider die Berechtigung, auch wenn's mein eigener Post ist :-(

Offline jacobi22

  • Posts: 5685
  • Gender: Male
  • Support also via PM or EMail
    • Jacobi22
Re: mpForm und SP7
« Reply #5 on: September 20, 2016, 02:21:48 PM »
Quote
inzwischen auch

ein paar Stunden nach deiner Veröffentlichung? zu Langsam?

Quote
Kann jemand das Zip-File mit der verkorksten 1.2.0 hier im Forum löschen? Mir fehlt da leider die Berechtigung, auch wenn's mein eigener Post ist

im Zweifel immer den MELDEN-Button benutzen, der an jedem Beitrag mit angezeigt wird, das geht zumindest am Schnellsten. (hab ich mal gemacht)
Sprech doch mal mit Dietmar, ich denk, da gibt es doch bestimmt Möglichkeiten, deinen Thread zu pflegen
Probleme sind da, um sie zu lösen, nicht, um nach Ausreden zu suchen.

Offline Martin Hecht

  • Betatester
  • **
  • Posts: 580
  • Gender: Male
    • meine Homepage
Re: mpForm und SP7
« Reply #6 on: September 20, 2016, 02:37:31 PM »
ein paar Stunden nach deiner Veröffentlichung? zu Langsam?
sorry, das war von mir vorschnell gepostet. Ich hätte selbst den Link mal angucken sollen. Das sollte kein Angriff auf Dich sein, sondern im positiven Sinne meine Verwunderung zum Ausdruck bringen. Irgendwie hatte ich noch in Erinnerung, dass das Repo lange offline war, dann von Dietmar extern gehostet wurde und irgendwann wieder zurück kam und zunächst einen  etwas angestaubten Eindruck gemacht hat. Aber schön, dass das Repo aktiv gepflegt wird. Danke!

Quote
im Zweifel immer den MELDEN-Button benutzen, der an jedem Beitrag mit angezeigt wird, das geht zumindest am Schnellsten...
danke

Offline jacobi22

  • Posts: 5685
  • Gender: Male
  • Support also via PM or EMail
    • Jacobi22
Re: mpForm und SP7
« Reply #7 on: September 20, 2016, 03:47:22 PM »
war eigentlich eine ernstgemeinte Frage ohne irgendwelche Befindlichkeiten  :wink:

P.S.: hatte dir im Frühjahr schon mal eine PN dazu geschrieben mit der Info über den Addon-Bereich und der Bitte um eine kurze Nachricht, falls eine neue Version deiner Module veröffentlicht wurde. Wäre zumindest sicherer.
Probleme sind da, um sie zu lösen, nicht, um nach Ausreden zu suchen.