PaulH

Just a quick update to say this is still inserting duplicate forms when attempting to swap the form in TinyMCE in WordPress 4.9

Update:

I’ve worked out whats going on. When the form is validated the default built in validation rules are checked and errors are displayed but the custom processors are not.

If none of the default validation rules trigger a validation error then the custom processors are performed and those validation errors are shown.

This isn’t what should happen as far as I know. All validations should be performed and results displayed – otherwise the user will fill in the form, resolve any validation issues (required fields, etc), click submit and then find new validation errors to fix.

Can this be corrected easily?

Definitely. This has happened twice before when I’ve used the contact form on the jigoshop.com site. I’ll try the email address instead.

Contact form submitted.

Not to worry. I’ve added a bit of jQuery to get the form to do what I’m after:

jQuery('#how_did_you_find option:first').attr('value','');

Thanks.

It doesn’t appear to correct the other issue I was having whereby cross sell items are not showing on the cart page:

https://www.ads-software.com/support/topic/cross-sell-items-not-showing-on-cart-page?replies=2

Updated the plugin to 2.0.1 but the cross sell items still don’t show on the cart page.

Update:

I managed to fix it. It turns out the path on line 53 of bootstrap.php is incorrect and should be shortened to:

require_once(JIGOSHOP_UP_SELL_CROSS_SELL_DIR . ‘/jigoshop_up_sell_cross_sell.php’);

I renamed the other file back to the default.

Tabs are showing again.

Contact form submitted.

I’ve sent it using the support @ email address this time instead of the contact form.

Contact form submitted.

Is Authorize.net the same as SagePay?

I’ve asked my client, I’ll update shortly.

Any update yet, as this is on a live web store?

I think I’ve worked out the problem. Just waiting for confirmation from client.

They had renamed the product to include a colon character in it’s title.

I know that SagePay uses the colon as a delimiter, once I’d realised what they’d done I renamed the product and the basket error went away.

Silly clients ??

I thought that would probably be the case.

Unfortunately it looks like the Regular Price field when editing the product strips the decimals for whole numbers, so even though I entered 1.00 on updating the product it reverts to 1

I checked it anyway and it still displayed the basket error.

As a side note, it appears that 1.50 is also changed to 1.5 in the jigoshop Regular Price field when editing a product (displays fine on frontend, but the number is formatted for display)