Fehlermeldung im Bankend, keine BLZ abrufbar, Bankdaten werden nicht gespeichert!

[Jorsan]

Habe das aktuelle Modul unter Magento CE 1.7.0.2.installiert!
Die Bankdaten können im Benutzerkonto von den Kunden nicht gespeichert werden und das Abrufen der BLZ funktioniert auch nicht. Des Weitern erscheint in den Bestellungen (im Bankend) folgende Fehlermeldung:
.........................
Fehler! Die eingegebenen Bankdaten können fehlerhaft sein!
Bitte setzen Sie sich mit dem Kunden in Verbindung!
.........................
Nach dem deinstallieren und installieren der alten Version 0.5.3 funktioniert zwar wieder alles aber die Fehlermeldung:
........Fehler! Die eingegebenen Bankdaten .......
ist immer noch da ist und die Bankdaten werden immer noch nicht in den E-Mails mitgesendet.

Ich wäre über eine Anleitung erfreut, die eine vollständige Datenbankbereinigung des Moduls DebitPayment ermöglicht. Da die Anleitung auf Gidhub das Modul nicht vollständig aus der Datenbank bereinigt. Über Hilfe wäre ich sehr dankbar!

Gruß
Michael Schmitt

[netscape22]

Ich habe das gleiche Problem.

Magento 1.7.0.1 CE und das aktuelle debitPayment 1.0.4 Modul. Installation/Upgrade des Moduls lief ohne Fehler.

Wenn ich dann die Zahlart von Bankverbindung auf SEPA umstelle, erhalte ich ebenfalls diese Fehlermeldung (Fehler! Die eingegebenen Bankdaten können fehlerhaft sein!
Bitte setzen Sie sich mit dem Kunden in Verbindung!).

Wenn ich das Modul aber auf "Bankverbindung" stelle funktioniert es. Nur bei SEPA gibt´s ein Problem.

[webster76]

In my case, this error occured too (in backend AND frontend), but i was able to solve it.
My previous version of this module before upgrading was 0.5.4 (MageDebit). The problem with the upgrade was a wrong named upgrade file. You can find this file in your installation here:
app/code/community/Itabs/Debit/sql/debit_setup/mysql4-upgrade-0.5.2-1.0.0.php

It seems that the upgrade file was not executed because of a higher version number (0.5.4) in the 'core_resource' table.

What you might wanna do:
In your database check the table eav_attribute for two new entries with the attribute_codes

'debit_payment_account_swift' and 'debit_payment_account_iban'

If you can not find these data rows, you have to switch to the table 'core_resource'. Search the data row with code='debit_setup'. Version and data_version are probably at '1.0.4'. Change these values to 0.5.2 so that the upgrade file will be executed and databse updates will be done.

Then clean cache and check the table eav_attribute again. If you find the two new fields, make a test order and everything in frontend and backend should be fine.

[vianetz]

Thanks very much @webster76, this solved the problem for me too!

[perler]

For me it didn't solve the problem. I have the entries debit_payment_account_iban and debit_payment_account_swift , my version was at 1.0.4, I reset it anyways to 0.5.1 and run the upgrade again to no avail. what can we do here?

[devtim123]

I did the bugfix for the database, the two entries were added successfully, but the error in the backend still exist. The backend still shows: 'Error! ... wrong data...'.

What can i do now?

[devtim123]

Also when i use the old module now (version 0.5.4) the error still exists. thats really bad because now i have to diable this payment solution until i get it work again. thanks for any help

[perler]

same here, still waiting for a solution. i let the customer enter BLZ/Account number and use an IBAn calculator to create the IBAN. very annoying.

[devtim123]

how u let enter the information? because the old module (v 0.5.4) does not work now. That means i cant view the information BLZ/Account in the backend. Do you use a different module?

[perler]

this works here: http://screencast.com/t/RBGCLyQuk

On Fri, Feb 7, 2014 at 5:33 PM, devtim123 notifications@github.com wrote:

how u let enter the information? because the old module (v 0.5.4) does not
work now. That means i cant view the information BLZ/Account in the
backend. Do you use a different module?

Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-34463327
.

Pat Erler
Gtalk/G+: perler@gmail.com
perler@gmail.comSkype: pat_erler

[devtim123]

Does not work for me, still the same error :(

[ssh-pw]

Hello,
has anybody found a solution for this problem? After the database updates suggested by @webster76 the fields appears in the tables but after a new order no IBAN/SWIFT data is shown in the order details.

After placing an order the debit_swift, debit_iban and debit_type fields in the sales_flat_order table not have any values (only NULL).

Thanks to all
patric

[devtim123]

i also have the error... someone has a solution? thanks

[therouv]

@devtim123 @ssh-pw What are you trying to accomplish?

[perler]

we try to actually use the extension.

as described, when using SEPA mode, the BLZ/Kto numbers are not displayed in the backend (only the error message, see OP) and as far as i see it, they are not even stored in the db.

[therouv]

With backend you mean viewing an existing order in the backend which was submitted via "bank" mode, right?

[ssh-pw]

Correct.

Witch current version of the extension in SEPA mode and Magento 1.7 the issues are:

• no bank data was saved to the database (whether not with the database update hack from @webster76 see above)
• the bank data was not viewed in the backend order detail page (in older versions of the extension the Bank Name, Account number and holder are displayed, now I get a error message "Fehler! Die eingegebenen Bankdaten können fehlerhaft sein!..." see above)
• the SEPA data in the custumer confirmation email are not encrypted, although the encrypt option are enabled in the configuration

Or had I update magento to 1.8 so solve these problems?

many thanks and best regards,
patric

[perler]

"bank" mode in opposite to what? in my words: customer pays with payment method Magento-DebitPayment (Lastschrift), the extension is in mode SEPA.

[loswochos]

Is there any solution? I still have the problem after setting the extentsion into SEPA Mode.