Strange conflict with WPForms and TD Composer

Posted in: Newspaper
Post count: 72

Hello TagDiv,

WPForms requires the uses of AJAX to submit credit card forms to Stripe. Recently they updated their Stripe add-on plugin and you updated TD Composer a few days earlier.

Some part of the code changes made between these two plugins now causes WPForms forms with Stripe payment buttons on them to no longer process payments. You can click on the submit button but the AJAX command needed to make the form submit will not fire.

I have WPForms looking into this as well but I wanted to get your input as well since I doubt that I’m the only site affected by this conflict. If I am then I can assure you it isn’t an honor – 🙂

If you can contact me via email I would be happy to share credentials with you so you can log into the test site and see for yourselves the problem.

Best,
Kim

Post count: 21065

Hello!

Unfortunately, this plugin is not a tested one. We tested Contact Form 7 plugin with our theme and it is working well.
Please note that we don’t offer support for untested plugins.

Thank you for your understanding!

Post count: 72

Hi Bettina,

I am so disappointed in your reply. That is a terrible response.
I came to you with a tested and confirmed bug that was caused by TD Composer and your response is “that’s your problem, not ours”.

Well here is an update for you:
I downloaded and tested every single Stripe payment option for WordPress from the repository.
ALL OF THEM FAILED WHEN TD COMPOSER WAS ENABLED except one.
The only one that worked is “Stripe Payments Plugin”.
The rest of them failed. Another one initiated a session with Stripe but then failed to open up the actual window to enter CC info.

So the problem the problem is with TD Composer v2.8 blocking the javascript that Stripe uses to connect to their credit card processors. This started after I applied the 10.4 theme update.

Another wrinkle is that since the JS is being blocked, the log files from WPForms showed no errors, the JS just never fired.

WPForms is just one of the users of said JavaScript. Why it works with “Stripe Payments Plugin” is unknown at this time, but also irrelevant to me because if TD Composer wasn’t blocking the JS that Stripe relies on I wouldn’t be using any other Stripe plugins.

Let’s try this again shall we and actually see if we can find a solution or at least a general direction for a solution? I would hate to have to roll back Newspaper to 10.3.9 but I will if this isn’t taken seriously by TagDiv.

Best,
Kim

  • This reply was modified 5 years by imkimc.
Post count: 21065

Hello!

I’m sorry to inform you in this way, but if we didn’t test this plugin, we can’t say if it will work or not. You will have to test and see. I can recommend only something that is tested and it is working 100%. There can be a plugin conflict with every untested plugin, but we are building this theme to work with the tested plugins. So, our theme was tested with those plugins: https://www.screencast.com/t/TLZqOCb6F
I hope you understand my point of view!
Also, we have some requirements for using this theme. Make sure that all the settings are like in our requirements, please follow the guide carefully: https://forum.tagdiv.com/requirements-for-newspaper/
and please increase all requirements that are lower, and follow all steps.

Our interest is to help our clients efficiently and provide solutions which are working 100%. For this we need more information to understand the issue and we try as possible as we can to reply in a short time. So, I didn’t mean this: : “that’s your problem, not ours” , and I will never say these words to our clients because we want to help anyone even if they don’t have paid support.

Regarding to your issue, after update if you just use our newest tool without reading some information about it before, you can probably destroy your work(website). This tool was built to help and not to damage your speed and quality of your website. Some clients don’t have any problem after update, but some clients has a lot and I know it is not nice to see your work damaged. That’s why we recommend all the time a full backup before every update.

If you didn’t run our tool and also you have some issues about plugin compatibility with our tested plugins, then this means it is our fault and we will solve the problem.
Also, if you don’t have the plugins up to date, any solution will not work for you that’s why I suggest to give it a try and check because if you had an old version to your updates, then the theme update is not updating your plugins automatically.
Also, you should reinstall the TagDiv Composer again and delete your cache(even from your browser).

In conclusion, if you really want to use those plugins which are not tested with our theme, then of course it is your choice and you can use it, but our support policy mentions: https://forum.tagdiv.com/newspaper-theme-support/ that we can not provide support for un-tested plugins. What you can do is to contact our custom work team here: https://tagdiv.com/premium-customization-services/ and let them know which plugins you want to use and they can change even our theme files for you and solve your issues.

Thank you for your understanding!

Post count: 13

I’m having the same problem only after installing 10.4. The payment form now won’t go through. I’m using woocommerce with stripe gateway

Post count: 72

Hi Bettina,

Our server meets exceeds requirements by a considerable margin, this is a fairly busy website (1.3+ million page views per month).

We upgraded the theme to v10.4 from 10.3.9 using the built in upgrade tool.
I did NOT run your CSS consolidation tool.

I would have rolled BACK to 10.3.9 but TagDiv bundled in an XSS vulnerability security fix in the 10.4 update. So now I cannot roll back without exposing our site to a possible XSS attack.

Let’s be clear, I am NOT asking you to support a plugin that isn’t on your list and I’m not asking you to do custom development work.

I found a serious bug in TD Composer that affects all stand alone Stripe payment plugins except one. And apparently is now affecting a WooCommerce Stripe plugin.

The bug: If you have TD Composer v2.8 active on your site, the javascript that needs to execute to process Stripe credit card payments fails to execute. There is no logfile or other errors given, the javascript just fails to run.
To determine that TD Composer caused the problem:
-I setup all stripe plugins on a dev site and tested.
-I turned off ALL plugins except TD Composer.
-I tried 6 Stripe credit card processing plugins one by one.
-5 of them failed to process payments as long as TD Composer was on.
-All of them worked just fine with TD Composer off.

So TagDiv needs to take this seriously. Please get this info to your Devs and see if they can validate the problem. I may be the first to have contacted you about this, however I doubt I’ll be that last. Someone else has already posted that they have the same problem in this thread.

I’m happy to provide more info, access to our dev site or answer questions if we are working toward a solution.

Best,
Kim

Post count: 21065

Hi,

Please send an email at contact@tagdiv.com and provide wp-admin and Cpanel access, so we can investigate more into this issue and provide a great solution for you. Also paste a link to this topic so we can easily identify you.
Let us know and we will gladly assist you.

Thanks!

Post count: 7

I have just rolled back from 10.4 to 10.3.19 to fix this Stripe payment problem and now it all seems OK.

This is a massive disaster of an error situation. We have lost thousands of dollars in revenue as a result.

I will go looking for the exact cause if I have time, but this is a very very serious matter.

Post count: 7

Thanks for documenting this, Kim.

Post count: 11

I do have the same issue with Woocommerce and Woocommerce Stripe module … So I guess we can consider those plugins as “tested” plugins ?

So ? Is there a bug ???

Post count: 11

Hi Bettina,

I do have the same problem with Woocommerce and strip which is a tested plugin. I have been able to downgrade to 10.3.19 to fix the problem …

Can you tell me if you consider to look at this issue asap ?

Thanks

Eric

Post count: 21065

Hello!

Please make sure you have all plugins up to date and start looking for a plugin conflict also, please deactivate ALL plugins except tagDiv ones, also if you are using child theme or cache plugin, deactivate them, clear all cache and try again.
If this problem is not solved after that, then we need to take a look and see what happened there.
Please contact us via email at contact@tagdiv.com and provide the following:
– admin url and credentials
– a link to this topic in order to identify you
Our team will take a look!

Thank you!

Post count: 72

Hi Bettina,

Since I found a plugin that works and we’re still going in circles here I’ve had to move on.

For everyone’s reference the only Stripe plugin that I found to work with TD Composer 2.8 is “Accept Stripe Payments” from wptipsntricks.

Their addons enabled me to setup payment options that are now a single click instead of using WPForms. Which is an overall improvement for our site.

I do hope that your devs find the issue, especially since it seems several users are now affected (possibly many more without knowing it)

Good luck everyone! Hope they get this fixed soon.

Best Regards,
Kim

Viewing 13 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic.