Andre Gagnon
Forum Replies Created
-
Link.com is entirely controlled by Stripe. If you need assistance, they should be able to help with this.
You should be able to disable it on your Payment Method settings page: https://dashboard.stripe.com/settings/payment_methods
Forum: Plugins
In reply to: [Presto Player] Video Size AdjustmentHi There,
Presto Player will expand to fit whatever container it’s in. That means it’s probably the container that contains your video that’s expanding. If you wanted to share a live link to your page, I’m happy to take a look.
Forum: Plugins
In reply to: [Presto Player] The following required query string data is missing: api_keyHi There,
Hmmm… this error is not coming from our plugin. Can you try temporarily deactivating other plugins? It would help you identify the problematic one.
Thanks for following up. It looks like a bug in our display logic there. I think we will have to push out a release for this. Thanks for reporting!
Forum: Plugins
In reply to: [Presto Player] Mark as Completed Learn Dash Integration BrokenHi Zac,
Can you update to 2.0.8? It should fix some issues with progression in newer versions of Learndash.
Hi George,
This is already supported. The pricing block will display the compare at price:
https://share.zight.com/rRumoeoR
Or were you referring to something else?
Forum: Plugins
In reply to: [Presto Player] Overlapping on mobileHi Alex,
It looks like an issue specifically with your containers. This container is set to
flex-direction: column, which is fine. But this is also paired withflex-wrap: wrap, which is going to collapse content like this (image, etc. that are resized to be responsive. In your elementor settings, you need to removewrapfrom your mobile settings:
https://share.zight.com/4guRyk2O@dpeyou I am also getting this error. It is a conflict with Jetpack.
It is adding_wca_initiator=action#038to the url. Since it is encoding&to#038, theaccess_keycannot be read with$_REQUESTfor some reason. You may want to push out an update. Perhaps you need tohtml_entity_decodeto make sure these urls work properly.Hi There,
Thanks for reporting this issue, and we’re very sorry for the disturbance. It looks like a change to our security layer resulted in your requests to our servers being blocked for a short while. This issue has been resolved and everything should be working as expected for you. But please let me know if you are still having issues.Thanks for reaching out. At first glance it sounds like a php8.2 compatibility issue with Guzzle. Are you using php8.2?
Keep in mind, WordPress itself only has beta compatibility with php 8.2, so you may experience other hiccups there.
https://make.ww.wp.xz.cn/core/handbook/references/php-compatibility-and-wordpress-versions/
Thanks for following up. Can you check to make sure you didn’t regenerate WordPress salts? We use one of these salts to encrypt the API token in your database. Regenerating WordPress salts can have the unintended consequence of needing to reconnect your store since the encryption salt changed. You can instead, set this as a constant if you plan on rotating WordPress salts, which not not common practice.
For the webhook, yes, you will want to keep that. It lets SureCart communicate with your WordPress installation when subscriptions update, etc.
Hi @anphira
Ah, looks like a bug in our plugin. We’ve just pushed out an update to address these issues. Can you update to 2.7.1?
I very much appreciate this type of feedback. Thank you!
Wow, the team will be thrilled to hear this. I very much appreciate your kind review! Thanks for taking the time to share. 🙏🏻
Thank you Andrew! We very much appreciate your review.
Thank you for reaching out about this. I appreciate your viewpoint and concern to help make SureCart more accessible for all users.
While we’ve made headway to ensure our plugin is as accessible as possible for all users, our checkout and product page score 82/100 and 84/100 respectively on the Lighthouse accessibility audit. So we recognize that there is room for improvement on these pages and throughout our plugin as well as improving our manual accessibility testing.
Accessibility is an ongoing commitment for us, and we’re dedicated to making improvements for all our users, especially those with disabilities. The work here for us is never finished – we are continually shipping updates to improve things.