Support » Plugin: PAYMILL for WordPress » Various (usuability) issues

  • Resolved nachtigall

    (@nachtigall)


    Hi,

    I use and like(!) the plugin, however, I see various usuability issues. I hope you do not mind if I go through them in a quick point-to-point manner:

    1. For ELV and SEPA it should be “Kontoinhaber” and not “Karteninhaber”

    2. After installation I had this logs in my www-error.log:

    [25-Jan-2015 11:54:11 UTC] WordPress-Datenbank-Fehler You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'wp_paymill_clients' at line 1 für Abfrage SHOW TABLES LIKE wp_paymill_clients von activate_plugin, include_once('/plugins/paymill/paymill.php'), require_once('/plugins/paymill/lib/setup.inc.php'), paymill_install
    [25-Jan-2015 11:54:11 UTC] WordPress-Datenbank-Fehler You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'interval <code>interval</code> longtext CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL' at line 1 für Abfrage ALTER TABLE wp_paymill_cache_offers CHANGE COLUMN interval <code>interval</code> longtext CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL von activate_plugin, include_once('/plugins/paymill/paymill.php'), require_once('/plugins/paymill/lib/setup.inc.php'), paymill_install, dbDelta

    3. After installation it said:

    Orphaned Webhooks found:
    hook_XYZ
    hook_ZXY

    These orphaned Webhooks should be deleted. Normally this will be done automaticly when saving new API keys via General Settings, but you can delete them via Paymill Dashboard, too.

    1st: In my case these were not automatically deleted after I saved the new keys. I think you mean, that I need to regenerate new keys and save these? Moreover, one cannot delete them from the Paymill Dashbord but on the Paymill site under Development => Webhooks. Maybe you can just link to https://app.paymill.com/webhooks.

    I’d propose this text:

    These orphaned Webhooks should be deleted. Normally this will be done automaticly when generating new API keys at the paymill website and saving new API keys via the wordpress Paymill General Settings, but you can delete them manuall via the Paymill Webhooks page, too.

    4. The info message “Webhook erfolgreich erstellt” looks misplaced. Please see this screenshot: https://seacloud.cc/f/b15d91fe2b/

    5. The card number is somewhat small. This is due to:

    #paymill_payment_form #paymill_card_number{
            ...
    	font-size:90%;
    }

    Any reason why not having this at 100% (i.e. should deleting the font-size here) as it is in IBAN, BIC numbers? Looks better imho.

    6. If I forget anything (like forgetting to enter a required field, or to tick the AGB) I have to re-enter all the credit card or sepa numbers. Can’t this be remembered on error as is done with all the other woocommerce related fields (name, address, phone number etc.)

    7. 3D Secure window pops up for about 3 seconds only showing a “Cancel” button, and then vanishes. Very irritating imho. Moreover, since most people have never heard of 3D Secure before anyways. Can’t this be hidden somehow because (display: none or similar) there is no form of interaction anyways.

    8. If I enter the credit card numbers with spaces in it, it gives an error: “Muss eine Nummer sein”. Can’t you just remove the spaces with javascript? In Sepa spaces are accepted. It feels very natural to enter the spaces as this is how it is written on the credit card: 1234 5678 5432 2341 (for Visa)

    9. I think it would be a usuability plus if SEPA and ELV would be combined into one input field. Have a look how the Sparkassen do it on this screenshot: https://seacloud.cc/f/49d457ceb0/
    Do you know what I mean? Would make sense because Paymill also handles SEPA and ELV the same.

    Then also please call it Lastschrift or SEPA-Lastschrift or simply Bankeinzug. Nobody has ever heard of the acronym ELV (just google for it https://www.google.de/#q=elv)

    10. I would really like to be able to have Lastschrift to be the default selected method and not creditcard. Lastschrift (or Bankeinzug) is the much more accepted method in Germany. Also, for me as a shop owner the costs for Lastschrift are much, much lower.

    11. When I enter the cursor into the input fields it is much too high. Maybe this is just a theming/css issue. If you give me your mail, then I can send you the website URL, so you can have a look at it if you want…

    Kind regards,
    Jens

    BTW: Do you have an issue tracker? Maybe you could enable the one on https://github.com/paymill/paymill-wordpress This would make it easier to submit, follow and discuss issues or feature requests.

    https://wordpress.org/plugins/paymill/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter nachtigall

    (@nachtigall)

    12. It should be “Kreditkartennummer” not “Kreditkarten Nummer”, see http://www.duden.de/rechtschreibung/Kreditkartennummer 😉

    Plugin Author straightvisions GmbH

    (@matthias-reuter)

    Hi Nachtigall,

    big thanks for your valuable feedback, it’s very appreciated. I cannot promise to get that done until next release, but these points are on my todo now. Unfortunately, some points cannot be fixed/changed by me right now:

    2. That’s a bug in WordPress’ recommened sql update routine used by my plugin. Currently no fix available, but I’ll continue to keep my eyes open.

    6. Some errors can be checked live via Javascript/Ajax, some are checked via Server scripts. Last ones require reload of payment form.

    7. Please note that 3D secure cannot be tested in Test mode, please switch to live mode. 3D secure is a security feature which I cannot influence.

    9. As Lastschrift will reach it’s end of life, I’ll not invest further time into optimizing that payment channel.

    11. That’s a theme issue

    All language/translation issues can be fixed by your own by using a custom po file. Nevertheless, your feedback is correct and will result in one of the next releases. I’ll keep you updated here until I’m done.

    Bugtracker is a great idea, but most people just don’t use them. I’ll still need to monitor this WP forum for bug reports, so no time savings on my side.

    Thread Starter nachtigall

    (@nachtigall)

    Hi Matthias,

    thanks for the prompt answer, just a quick response:

    2. + 6. ok, I see

    7. I am already in live mode. Maybe we’ll just disable 3D Secure with paymill then… Its popup somewhat “irritating”, and irritation is not good for trusty webshops

    9. I disagree. I talked to paymill on the phone and they tolded me that they handle the normal Lastschrift (ELV) basically the same like Sparkasse Online Banking is doing it (as in the screenshot): Whenever a user enters just Kontonummer and BLZ, then this is automatically translated to a SEPA-Lastschrift. That is technically there is only SEPA-Lastschrift, however, from a users point of view you only have to enter Kontonr. and BLZ. I think it will be like this for at least the next 5 years, maybe you can clarify with Paymill.

    13. 😉
    Since installing I have this in my www-error.log:
    [25-Jan-2015 17:13:15 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/data/web/vhosts/www.mysite.de/htdocs/wp-content/plugins/paymill/lib/integration/pay_button.inc.php on line 368
    [25-Jan-2015 17:41:06 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/data/web/vhosts/www.mysite.de/htdocs/wp-content/plugins/paymill/lib/integration/pay_button.inc.php on line 368
    [25-Jan-2015 17:41:36 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/data/web/vhosts/www.mysite.de/htdocs/wp-content/plugins/paymill/lib/integration/pay_button.inc.php on line 368

    Any news on these issues?

    Would be nice if at least the quick-and-easy issues like translation quirks could be solved. I know that one can do it manually but I do not like to customize and then revert again…

    Thread Starter nachtigall

    (@nachtigall)

    Hi Matthias,

    it took me quite some time to put together this bug report. I am bit disappointed to say that (almost?) none of these have been fixed in the latest 1.9 release.

    Even none of the easy to fix translation typos, not the minor CSS issue and not even the “PHP Warning: Invalid argument supplied for foreach()”

    Best,
    Jens

    Plugin Author straightvisions GmbH

    (@matthias-reuter)

    Hi Jens,

    I understand it’s not comfortable to wait for process while seeing other non mentioned issues are fixed before yours. In that case, it was important to release v1.9 before taking care for your issues, as it was a critical, payment relevant update optimizing subscription handling which includes update to new Paymill API. Even next v1.9.1 release will not contain fixes for your reported issues, as there is currently a renewal bug on some installation which has much higher priority.

    You issues are sheduled to be fixed on 1.9.2 or 1.9.3.

    Kind regards,

    Matthias

    Plugin Author straightvisions GmbH

    (@matthias-reuter)

    Finally I’ve got the time to apply some of your valuable feedback into the plugin. Please be aware that it could take a couple of weeks until next release, but some of your requests will be included into that release.

    1) fixed on next release
    2) bug of WordPress recommened plugin update routine / no plans to fix here, nothing critical
    3) I want to avoid deeplinking for security purposes
    4) currently no plans to further optimize that specific piece of code
    5) fixed on next release
    6) currently no plans to further optimize that specific piece of code
    7) works as intended
    8) Currently no plans to further optimize number input validation, as PCI DSS 3.0 compatibility will become new standard in Paymill for credit card payments
    9) Translation for ELV will be “Lastschrift” on next release.
    10) Currently, there are no plans to allow a custom primary payment option
    11) That’s a theme issue, please check your box-sizing settings in CSS.

    Thread Starter nachtigall

    (@nachtigall)

    Thanks, I very much appreciate this!

    Please do not forget about the minor 12th issue:

    12. It should be “Kreditkartennummer” not “Kreditkarten Nummer”, see http://www.duden.de/rechtschreibung/Kreditkartennummer 😉

    Plugin Author straightvisions GmbH

    (@matthias-reuter)

    oh yeah, that will be fixed, too 🙂

    Plugin Author straightvisions GmbH

    (@matthias-reuter)

    #13 will be fixed, too 🙂

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Various (usuability) issues’ is closed to new replies.