Low Search AID tag issues on production environment (possible Stash embed conflict?)
Hi,
I'm having a strange issue with the Low Search tag on my production environment that I'm not having locally.
I have a Low Search tag within a snippet in a Stash embed, as part of a global header. The {AID:Low_search:catch_search} doesn't process once the template is cached (or after the first page load?). This doesn't happen at all on my local environment, but happens every time on production.
I suspect this might be a parse order issue with Stash, but I also remember having issues with the {AID} tag on another module connected to some changes with EE core, but either way I'm hoping you have a clue or some advise on the next direction to look in.
For now I've hard coded an ACT field with the AID number within the Low Search tag, and it appears to be working, but I'd prefer to fix the issue and have it run clean.
Thanks for your help,
Steve
Replies
Low 25 Feb 2014 07:17
Yeah, this will definitely have something to do with another add-on, could be Stash.
The {AID...} variables are put in place by EE and replaced by EE. That's not something an add-on like LS does itself. If you take Stash out of the equation, you'll see it'll be rendered just fine.
Therefore, I'd look into that first, and ask Mark Croxton (Stash's developer).