Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Stash and Publisher
| Status | Resolved |
| Add-on / Version | Publisher 1.6.8 |
| Severity | |
| EE Version | 2.9.2 |
Edoardo Biasini
Mar 03, 2016Is Stash supported?
I get a whold bunch of errors on my Stash enabled pages when I install Publisher
BoldMinded (Brian)
Yes it is. There should be no conflicts, they are doing two very different things.
i can’t help though unless you share he error message.
Edoardo Biasini
It’s not really an error… I get a whole bunch of unparsed {stash:name}{name}{/stash:name} code on the front-end. I even tried to look at template debugging but the overall system is stuck. It won’t even allow me to scroll down the actual template debugging. I tried to increase available memory with no success.
This seems to occur as soon as I add another language. Where can I check for insights? Do you want access?
Edoardo
Edoardo Biasini
Comment has been marked private.
BoldMinded (Brian)
I’m pretty sure this is not a Publisher issue. Publisher does not change or alter the parsing, if it did other plugins or native EE tags would be effected too. I’ve had many customers use Publisher and Stash together fine. Did you try simplifying your template by removing everything but the stash tags to see if it works? What have you done so far to debug the issue?
BoldMinded (Brian)
Can you post the entire page template code in which those stash tags are present?
BoldMinded (Brian)
Edoardo, please respond to the tickets on the site, not direct replies via email. Thanks.
“Unfortunately is a bit complex. The template calls for snippets which are enclosed in Playa fields… it’s a bit complicated. You can have a look yourself in the design section. Thanks for your suggestions.”
That is kind of my point, it needs to be simplified in order to debug it. The last 2 times similar issues have come up, I spent over an hour debugging customers templates only to discover that it was an issue with their template code, not my add-ons. For this reason I can’t spend time debugging your issue or logging into your site until you spend time simplifying your template and provide more evidence that it is in fact a conflict with Publisher. Even if I were to login to your site right now I don’t know what template or snippets to look at because you haven’t told me what they are.
Did you read https://boldminded.com/support-terms-conditions and https://boldminded.com/support/how-to-submit?