Plugin Contributor
lusp
(@lusp)
Hi @mariine,
Could you please provide us with some more information on which URL exactly do you click when the problem occurs?
Do you mean the URL you have generated for your campaign which was used and placed somewhere e.g. in the newsletter or on your site?
Some screenshots illustrating the encountered problem or direct link to the site where it occurs would be really helpful.
Kind regards,
Luke
Plugin Contributor
lusp
(@lusp)
Thank you for the screenshots. Here are some questions which should help in further troubleshooting:
1. Are the products included in the campaign published, on stock and publicly accessible by all customers?
2. Isn’t the access to these products restricted e.g. only for logged-in users?
3. Do you have any rewrite rules added in the .htaccess file, do you use any plugins applying the SSL or the ones which might have an influence on URLs structure?
4. Have you tried to temporarily disable the minification and code optimization plugins in order to exclude they may interfere here?
Kind regards,
Luke
All products are on stock, and accessible by all customers.
I tried disabling all the plugins, keeping only woocommerce and cart link for woocommerce, and it did the same thing
Plugin Contributor
lusp
(@lusp)
Have you tried to resave permalinks structure at WordPress > Settings > Permalinks?
Kind regards,
Luke
I resave, and there is always the 404 error. However, I have custom structure, could this conflict ?
Plugin Contributor
lusp
(@lusp)
Could you please shed some light on how this custom permalinks structure exactly looks like with an example?
Common Settings :
https://www.paima-beaute.com/%category%/%postname%/
Product :
/product/%product_cat%/
It helps ?
Plugin Contributor
lusp
(@lusp)
Yes, thanks a lot – knowing the exact permalinks structure you’ve just provided we were able to reproduce this problem in our test environment and soon we will release an update containing the proper fix.
Kind regards,
Luke
Plugin Contributor
lusp
(@lusp)
@mariine,
The Cart Link 1.1.2 update containing the fix for the problem you’ve reported has been just released and should be available to download by now. Please do the update and let me know if the problem’s solved.
Kind regards,
Luke
It works, thank you very much !
Plugin Contributor
lusp
(@lusp)
It’s great to hear that everything works fine now. Thank you too for bringing this to our attention : )
