Andre Gagnon
Forum Replies Created
-
Happy to help! Perhaps you could share what version of the plugin you are running, along with a link to the issue? I would help us see exactly what is happening.
Happy to help!
Thanks! I do see you are running a beta version of SureCart. We don’t recommend running a beta version on live sites as there can be bugs like this. We don’t recommend running beta software on production websites – it should only be used for testing purposes.
I’m pretty certain that you would not have experienced issues if you had stayed on our stable release branch. In the meantime, could you update to the latest stable version? I don’t think you will want to be on the beta version since your site is live.
Thanks for following up. Perhaps you could share a public link to your site to see the issue? I’m just trying to match up a support topic with your account, so it’s possible it’s for a different site. Without seeing the live site it might be hard to diagnose the issue.
Thanks for following up! For sure – additional SEO options are always great to have. If you could provide feedback once you try 3.0, please let me know.
Happy to help explain on the caching. I did see your support emails so I was able to take a look at your site. The headers coming back from the page indicate caching:
https://share.zight.com/d5ujq2nn
X-Litespeed-Cache: hitThis means you are running a Litespeed server, and the cache “hit”, meaning it’s returning a cached version of the page. Depending on your host, you may not even know this caching is enabled (you don’t need a plugin for this). Typically on Litespeed setups, I recommend the LiteSpeed caching plugin – it just lets you control LiteSpeed cache settings on those pages. Let me know if this makes sense.
Hi There,
Thanks for taking the time to leave a review. Just checking through your support tickets to get a better understanding of what’s going on here.
Checkout
- These checkout issues sound like caching. When some users are getting a different experience than other users. So for example, if you set your checkout to test mode, but then cached that page, some users will still see the page in “test mode” depending on your caching setup. Looking at your checkout page, there is a caching “hit” from Litespeed. I recommend you check out this doc: https://surecart.com/docs/caching/
- I’m not sure I completely understand this, but if you have caching on your checkout page, redirecting to a different form would solve things. This is because there is no cached version of the form yet on your new page. I don’t think this is necessary if you have the proper cache turned off on your checkout page.
- This also sounds like caching behavior, especially if you are getting inconsistency. The checkout page is not fragile – it’s extensively tested and processes millions of transactions every month. However, SureCart operates on thousands of unique hosting and caching configurations, so it’s easy to misconfigure this for eCommerce. It sounds like caching had caused some users start their checkouts in test mode. If you are using abandoned checkout, those test mode checkouts will send them back to complete the test checkout. It’s also possible they are still seeing a cached version of the page if you have turned on browser caching (this keeps the page cached in their local browser memory).
It’s totally not your fault – caching can be very difficult to get right, and incorrect configurations can have some serious consequences in these cases. Can you exclude your checkout page from caching? Once the test checkouts get cleared out, then I am confident you should not experience any of these issues.
SEO
I encourage you to check out version 3, which will be releasing in a couple days. In this version SureCart Products sync to custom post types, making them much more compatible with SEO plugins. That being said, we do have native structured product data for rich snippets in google. There is no need for a plugin to do this.
Thanks so much for the review!
Thanks for the feedback! We have just launched our beta version of Bricks product and shop pages, have you checked that out? It’s the first Bricks iteration and we hope to integrate more going forward.
Forum: Plugins
In reply to: [Presto Player] Player doesn’t adapt to resolutionThanks for reaching out Karl. We will get this added. Keep in mind, though that this will only work for non-Safari browsers since Safari runs hls natively. But it should be an easy add for us. Thanks for reporting.
Thanks for the lengthy reply. Apologies, I was not trying to avoid your question.
whether it was possible to avoid allocating the site’s default role
This is not something we do. WordPress itself requires a default role. You can certainly remove the SureCart user role if you want. But that still won’t change default WordPress functionality. I honestly don’t know how to go about doing this, which is why I was suggesting doing things in the way WordPress expects.
The only way I would know how is just to remove all roles, but this would require custom development to ensure only the correct ones are added again.
function remove_default_role($user_id) {
$user = new WP_User($user_id);
$user->set_role(”);
}
add_action(‘user_register’, ‘remove_default_role’);But not the way WordPress was designed, so your milage may very.
Again, my apologies, I am just trying to steer you into a direction that I thought would be best, knowing how these things work under the hood.- This reply was modified 1 year, 9 months ago by Andre Gagnon.
If I select “no” for subscribers but “yes” for sure cart customers or premium members, there will be a conflict if a user was allocated the default subscriber role as well as the sure cart customer role when making a subscription purchase, and the premium member role.
What if you just didn’t select the “no” part? The thing about permissions – all roles should have no permissions to start. You shouldn’t need to explicitly exclude a capability from a role. Basically if it’s not set, it is assumed it’s a “no”.
Doing things this way, where you select “no” for specific roles can make things very complicated too. Rather than just an opt-in system, you need to account for opt-in and opt-out, which makes the logic extremely hard to follow. Which plugin is this?Hi There!
Thanks so much for reaching out. Happy to help with this.
We require all purchases to have WordPress user accounts. Otherwise we cannot assign a user role to that person. By default, it’s the SureCart customer role, which has no capabilities. It’s just used as a record for the purchase.
It is perfectly fine for a user to have multiple roles. I believe you may just need to alter how you are checking for permissions.
Instead of “Can this user role do this”, you should be checking “Can this user do this”. It will take into account the roles and capabilities that the user has.
So for example, say you have a role called “Premium”. This role has the capability toupload_files.
For users with this role,current_user_can('upload_files')will be true.
For users without this rolecurrent_user_can('upload_files')will be false.
https://developer.ww.wp.xz.cn/reference/functions/user_can/
https://developer.ww.wp.xz.cn/reference/functions/current_user_can/
Let me know if this makes sense.Hi There!
You should be able to delete a collection by navigating to the single collection edit screen:
https://share.zight.com/GGueZwr1And yes, you can disable the filter on the shop page, select the product list block and toggle off the “collection” toggle:
https://share.zight.com/xQuJd87JAny questions, let us know.
Hi There!
So sorry, somehow we missed your question. Are you talking about the cart icon? Or the entire menu? The cart icon should match the color of your header menu. If you are having issues with the entire Astra header menu, perhaps you will want to reach out to Astra support about that – they are typically very helpful.Hi There,
Thanks for taking the time to leave a review. I really wish you had reached out to us about this – it sounds like a plugin conflict of some kind. We are happy to help solve these type of issues.
The deprecation warning you are seeing is not actually an error, but a developer notice because your site is in debug mode. It’s specific to php 8.2 – we will have to update that, but keep in mind it will not affect functionality.
Could you provide any other information about where you are seeing the validation error? I’m happy to help get you up and running.