Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use custom URL for Sprig action requests
See original GitHub issueIs your feature request related to a problem? Please describe.
We’re currently facing the situation in which our site is running with one URL (e.g. https://www.domain.com), but the Sprig actions requests must be served with a different URL (e.g. https://content.domain.com/index.php/actions/...). Thus, I’m wondering if it’s possible to use a custom URL for Sprig action requests.
Describe the solution you would like
A possible solution would be to set a custom URL for Sprig action requests in the sprig.php config file, which ultimately gets passed down to the _getSprigActionUrl function.
Describe alternatives you have considered
Currently, I’m replacing the “wrong” URL with the “right” URL directly in the _getSprigActionUrl function, which is by no means a clean solution.
Issue Analytics
- State:
- Created a year ago
- Comments:24
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@bencroker yeah, you’re right, this is the difference. thanks for finding this out!
@martinhellwagner this might be interesting for you: https://github.com/putyourlightson/craft-sprig/issues/257#issuecomment-1239469060
Of course, an
elsecondition – so obvious! I think that’ll work great – thanks for the help! 🙂