I was testing this module on a local development version of a site I was working on and it works wonderfully. Then, I pushed the changes to my development server. I found that since all links are forced to absolute, I was being redirected to my local dev version by all express checkout generated product links. This kind of makes it hard to use this module in a multi-stage deployment workflow.
I started working on a patch for the module to add a radio button for relative vs. absolute links, but it doesn't seems to be working. I've assured that the salt values on each environment are the same. Is there some other mechanism at play that I'm missing?
I've attached my patch for review.
| Comment | File | Size | Author |
|---|---|---|---|
| relative.patch | 4.74 KB | frogdog_tech |
Comments
Comment #1
frogdog_tech commentedComment #2
frogdog_tech commentedHmm... disregard my previous, it seems to be working now. I don't know if a random clear cache fixed it or what. But the relative/absolute selector seems to be working for me now. You are welcome to test/add the patch to dev version.
Comment #3
bc commentedIs there a reason to generate absolute links in the first place? I vote for relative only, or passing off responsibility to the template system.