Medran

Hi again guys,

Can I ask a few questions because your test video does not seem to completely replicate the issue all of us are seeing.

I see in the video that you are using the WooPay plugin at the same time as the standard stripe plugin and I don’t see the standard card fields so its doubtful weither those themes would not show the same issue if it was used in the same way?

Also are you using the old school cart with the woocom short code or the new block editor? To replicate the issue I would recommend the following:

Only have the stripe gateway active
ensure its actually populating the card fields on the checkout
ensure LINK is enabled as this might also play a role in the bug
ensure the cart page is using the old woocom shortcode to populate the cart page not the new block editor.

hi @carolm29

to be quite honest what is so frustrating is that I’ve now not once, twice but three times pointed out that one of their developers actually commented on this exact post after all of us flagged the issue.

ive also highlighted to you that in this thread he has given you the exact details of what’s causing the issue and has said it has to be fixed by yourself not by them as it’s loading a Java script file that should not be loaded on the basket page but only on the checkout page.

please note this is a specific issue of the old woocom basket page not the new block one!

Hey @anastas10s

If you look further up in the thread?@jimapp?(one of the developers behind flatsome!) has already identified that this is being caused by unexpected loading of JavaScript by the stripe plugin. And has told us to reach out to you guys to get it fixed.

This only happens when the new stripe checkout experience is active in the stripe plugin. Can I check you all tested it with the new checkout experience active? As this is what seems to hide the coupon field!

Quite frankly at a loss here as to how to proceed considering you guys keep sending us back to flatsome and flatsome keeps sending us back to you guys. Maybe it’s time for one of your team to talk to @jimapp directly? ??

Thanks,

Marc

• This reply was modified 8 months, 3 weeks ago by Medran.

@doublezed2 can you have a look at the statement of @jimapp that your plugin is loading unexpected javascript on the cart page?

@jimapp so why is this only impacting flatsome and not various themes, such as Storefront, Twenty Twenty-Four, Astra, Blocksy, GeneratePress, and Botiga as tested by Woo Support?

Are you sure that your theme is using the current most up to date cart template? And if not should this not be patched through a flatsome update rather than asking us to create a child theme?

@shameemreza @jimapp rather than pointing us all into different directions could you two maybe liaise and identify HOW to fix this issue on your end?

Otherwise I am afraid I’ll have to switch to a different payment provider and theme as it currently feels like you are both blaming the other development team rather than work together to identify and fix the issue. ??

Same problem – only way to fix it is to use the legacy stripe checkout option! Can someone look into this?

Same issue for me… everything was working fine until the latest update…

Now I am getting this:

Error Details
=============
An error of type E_ERROR was caused in line 98 of the file /var/www/vhosts/katzenworld.co.uk/httpdocs/wp-content/plugins/mailpoet/lib/Segments/DynamicSegments/FilterFactory.php. Error message: Uncaught MailPoet\Segments\DynamicSegments\Exceptions\InvalidFilterException: Invalid type in /var/www/vhosts/katzenworld.co.uk/httpdocs/wp-content/plugins/mailpoet/lib/Segments/DynamicSegments/FilterFactory.php:98
Stack trace:
#0 /var/www/vhosts/katzenworld.co.uk/httpdocs/wp-content/plugins/mailpoet/lib/Segments/DynamicSegments/FilterHandler.php(50): MailPoet\Segments\DynamicSegments\FilterFactory->getFilterForFilterEntity(Object(MailPoet\Entities\DynamicSegmentFilterEntity))
#1 /var/www/vhosts/katzenworld.co.uk/httpdocs/wp-content/plugins/mailpoet/lib/Segments/SegmentSubscribersRepository.php(403): MailPoet\Segments\DynamicSegments\FilterHandler->apply(Object(MailPoetVendor\Doctrine\DBAL\Query\QueryBuilder), Object(MailPoet\Entities\SegmentEntity))
#2 /var/www/vhosts/katzenworld.co.uk/httpdocs/wp-content/plugins/mailpoet/lib/Segments/SegmentSubscribersRepository.php(448): MailPoet\Segments\SegmentSubscribersRepository->filterSubscribersInDynamicSegment(Object(MailPoetVendor\Doctrine\DBAL\Query\QueryBuilder)

Hi @algolplus ,

Would you be willing to help us write the PHP Code to make the output match our file format?

We would be happy to purchase the premium plugin of course, how much is it?

Thanks,

Marc

• This reply was modified 4 years, 4 months ago by Medran.
• This reply was modified 4 years, 4 months ago by Medran.

it’s using the custom functions option to create a custom XML file, does that still work?

Ok further narrowed it down. It works with all plugins active if on a default theme.

if flatsome is active the specific conflict only occurs if flatsome and YITH WooCommerce Wishlist Premium are active at the same time!

Ok, the incompatibility comes from flatsome! Are you able to fix it to work with flatsome’s checkout method?

Same problem for us as well…

that is almost working now…

I just need to find out the $ equivalents for 2 custom fields but not entirely sure how to obtain those?

That works thank you ??