Issue with Paypal Complete Payments on OSEL

[wajake41]

We have migrated to the PayPal Complete payment on our OPAY page not OSEL OOPS I titled it OSEL incorrectly.
After doing so we find the code shown below hass been installed into our OPAY template.
The code is not working correctly as the payment fields for card number, expiration date, and CVV canot be keyed into. The code inserted is not anything I have experience with so we are looking for a solution to the issue. Mia support is stonewalling us on this (have refused to help us) so I hope someone on the forum has a solution. This is the code:
Thanks for any help that is provided! Larry
<mvt:comment>Fields for PPCP</mvt:comment>
<br>
<mvt:if expr="g.PaymentMethod EQ 'paypalcp:cc'">
<div id="payment-fields" class="t-payment-form t-paypalcp">
<div class="t-payment-form__heading">
<span class="c-heading--subheading--x-small u-icon-secure" aria-hidden="true"></span>
</div>
<div class="t-payment-form__fields c-form-fields--compact">
<mvt:foreach array="payment:fields" iterator="field">
<mvt:assign name="l.settings:field:html:class:invalid" value="ternary( l.settings:field:invalid, 'u-color-red', '' )" />
<mvt:if expr="l.settings:field:code EQ 'cc_exp'">
<div class="t-payment-form__field-set t-payment-form__field-&mvte:field:code;">
<label class="c-form-label &mvte:field:html:class:invalid;" for="&mvte:field:code;" title="&mvte:field:prompt;">&mvt:field:prompt;</label>
<mvt:item name="payment" param="field:code" />
</div>
<mvt:elseif expr="l.settings:field:code EQ 'cc_number'">
<div class="t-payment-form__field-set t-payment-form__field-&mvte:field:code;">
<label class="c-form-label &mvte:field:html:class:invalid;" for="&mvte:field:code;" title="&mvte:field:prompt;">&mvt:field:prompt;</label>
<mvt:item name="payment" param="field:code" />
</div>
<mvt:elseif expr="l.settings:field:code EQ 'cc_cvv'">
<div class="t-payment-form__field-set t-payment-form__field-&mvte:field:code;">
<label class="c-form-label &mvte:field:html:class:invalid;" for="&mvte:field:code;" title="&mvte:field:prompt;">&mvt:field:prompt;</label>
<mvt:item name="payment" param="field:code"/>
&mvt:cvv_dialog;
</div>
<mvt:else>
<div class="t-payment-form__field-set t-payment-form__field-&mvte:field:code;" data-hook="mvt-input" data-mvt-id="&mvte:field:code;" data-mvt-classlist="c-form-input" data-mvt-autocomplete="cc-name">
<label class="c-form-label &mvte:field:html:class:invalid;" for="&mvte:field:code;" title="&mvte:field:prompt;">&mvt:field:prompt;</label>
<mvt:item name="payment" param="field:code" />
</div>
</mvt:if>
</mvt:foreach>
</div>
</mvt:if>

[wajake41]

Miva support has told us they will not support us because we are running MMUI. Are we the only site running MMUI?

[Rick Wilson]

We deprecated MMUI just under 10 years ago, so there's a few of you left out there, but it's been unsupported for a decade now.

[wajake41]

Question: Why is Miva still doing new releases for obsolete MMUI sites. We just received a notice of another release for our MMUI sites? Very puzzling.

[wajake41]

We would like a bid from someone who is capable of fixing the Miva code shown above. Any takers?
We had the same experience on a prior move to Complete Payments on another site and Miva did the repair that time.
They have washed their hands on this fix though.
In the image above it shows the 4 payment fields created by the Miva Complete payments code, The problem is that only name on card field is keyable, the card number, exp date, and cvv cannot be keyed into.

[Rick Wilson]

That's not true, The core platform update was released to everyone. Back when we deprecated MMUI in 2015 we explained that. We've been very public about this.

Here was the release note on July 29th 2015:

• MMUI is now deprecated. It has been removed from new installations and will not receive updates for new features or bug fixes in the future. Existing stores using MMUI will continue to function.

[wajake41]

Hello Rick: Actually I misspoke. Our orange-traffic-cones.com site is a CSS site, not MMUI and is up to date on all releases.
We would like to contract with Miva to solve this issue. Any change of that since it is CSS?
Thanks,
Larry

[Rick Wilson]

You can use CSS on an MMUI store, so just cause you have CSS doesn't mean you're on CSSUI and using Shadows (which is the supported version)

David Hubbard tells me you're on MMUI, so I suspect he's correct. Working with him through Support is your best path, but from what I've been told you didn't want to follow his suggestion.

The best short term path here is to roll back before you broke it. The best long term path is to do a new fresh build on Shadows using Page Builder.