-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
html class generation from payment processor type (machine) name (was "Display issues") #367
Comments
Fascinating, and a new issue to me. What version(s) of civicrm/iats are you using here? |
CiviCRM : 5.28.1 |
@KarinG This causes problems in wordpress not drupal. |
I'm not convinced this is an iATS extension issue. Although all the examples you're listing have machine names that can just be used as a class, that's not part of the requirements/contract of the payment processor machine name. If I'm correct, it's a wordpress-civicrm issue that it's not converting the names to be "class safe". Happy to be corrected ... |
That doesn't seem like quite the same issue - but in any case, it's not extension specific right? |
Just setting up iATS for the first time, and I confirm that this is an issue with Joomla, not just WP. Display on the site shows exactly like yashodha's image above where the radio button input is displayed above its label due to .card class display=block Joomla! 3.9.24, Civi 5.39.0, iATS extension 1.7.4 |
Hey @philmb - I wonder if I need to be more clear? This issue is about the generation of html by civicrm (in combination with it's CMS). It appears that some of that html generation is making an assumption about the machine name of processors as "class safe", which is not correct. It shows up for IATS because iATS (unlike most core processors) has a space in it's machine name. It's not an iATS issue, or something that can even be corrected within the extension. I can leave this issue open for others, but there's nothing I can do to fix your issue within the extension code. In order to fix it, please post (referring to this issue) in the civicrm-joomla issue queue, here: |
I'm wrong! It's a CiviCRM Core issue from this commit: which was part of this PR Thanks for your persistence ... |
@adixon will you be filing a ticket for the same? |
This was fixed in core a few weeks ago. |
There is a display issue with the payment processor selector for Credit Card payment.
The issue seems to be with the new version of CiviCRM that is adding a class "name of payment processor" in the code when there was only the class "crm-form-radio" before.
For Paypal, it's adding a class "payment_processor_paypal_standard" where all spaces in processor name have been replaced with underscoress, which is fine.
But for iATS 1st pay, the system is not adding underscores to the payment processor name when adding the class, which creates all these useless classes including the "card" class, when really it should be "payment_processor_iats_payments_1stpay_credit_card"
See attached files to compare
Older version
![payment processor selector class ALH](https://user-images.githubusercontent.com/3455173/120355665-fd270880-c2f2-11eb-9b48-a1d191ad1899.jpg)
Latest version
![payment processor selector class FFF_issue](https://user-images.githubusercontent.com/3455173/120355689-031ce980-c2f3-11eb-9b0f-1bb287d769f9.jpg)
The text was updated successfully, but these errors were encountered: