-
Notifications
You must be signed in to change notification settings - Fork 63
Fix the link since the page migration #171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Touxten
commented
Jul 24, 2025
| Questions | Answers |
|---|---|
| Description? | Fix the link from the page migration? |
| Type? | bug fix |
| BC breaks? | no |
| Deprecations? | no |
| Fixed ticket? | PrestaShop/PrestaShop#39185 |
| Sponsor company | @friends-of-presta |
| How to test? | See issue |
SiraDIOP
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Qa by Dev
|
@SiraDIOP You can test it just fine yourself, really. Just verify that all buttons in module settings work fine. |
|
Ping @PrestaShop/qa-functional @PrestaShop/committers for QA, this is required for this module to work on 9.0.x branch on NGINX. |
jolelievre
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be fixed on the core level not on all modules, I struggled to ake this backwatd compatible and it works in most cases I guess from the issue that nginx is a special case but it also needs to be handled
If there is no other solution we'll fix it on the module level, but first we need to try and handle this on the core level
|
@jolelievre Double index.php in the URL is a wrongly constructed URL.
Yes, the core CAN handle it, but the module should link to a proper URL. It's the modules "fault" that it routed to fragile relative URL for years. |
|
@Hlavtox the thing is that but, to be honest, I think this PR doesn't need to be blocked @jolelievre |
|
Ok i can change and use the third parameters. However, why not merge all PRs and afterthen use the third parameter? Since the release of 9.0.0, these modules have been unusable, and the PRs date back to July. PrestaShop/PrestaShop#39185 (comment)
|
|
I get a 404 error when I add tracking id in module configuration, I think it is linked to this issue. |
|
@jolelievre It's ready Jo, check it out. The params need to be provided properly, so I did it. :-) |
|
@SiraDIOP I beleve you're now able to do the QA review? |
|
Hello @Touxten, Thanks for your PR, I tested the module on nginx server and it's good for me Thanks |
|
PR merged, well done! Message to @PrestaShop/committers: do not forget to milestone it before the merge. |

