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: Blocks Support
| Status | Resolved |
| Add-on / Version | Publisher Lite 1.6.10 |
| Severity | |
| EE Version | 2.10.1 |
Nick Johnson
Jan 07, 2016We have recently begun to look at using Blocks for our clients to give them more dynamic page options without having to create a gazillion templates. I am wondering if you have any plans to support this with Publisher. More specifically, for the approval workflow - saving a block as draft still saves it for published as it is not supported.
BoldMinded (Brian)
I won’t be adding Blocks support natively. Its simply too much to handle with already supporting Matrix, Playa, Grid, Relationships and Structure. Publisher has an API that Blocks could use to support Publisher, so the support would need to be added into Blocks, not the other way around.
Due to some planned changes for Publisher 2.0 (EE3 only) Blocks should work just fine with Publisher without any need for them to be aware of each other.
BoldMinded (Brian)
FWIW people have used Blocks with Publisher, but you need to set the Blocks fieldtype as ignored in the Publisher settings.
Nick Johnson
Comment has been marked private.
BoldMinded (Brian)
Yes, but depends on if he adds full support. The API basically is just a couple of properties in which developers can access that makes their add-on aware of what language and status Publisher is currently displaying data and what language status it needs to save data. If used correctly yes it will have full approval and language support.
I’d have to think about that, but right now I’m leaning towards no, only because time spent working on adding that support would keep me from working on Publisher for EE3. If this came up 6 months ago I would definitely add support, but as it is right now the lifespan of EE2 is shortening and I need to get to EE3 as soon as possible.
BoldMinded (Brian)
To be honest, it would probably be easier to pay Bryan Burgers to add support directly to the add-on. Its harder for me to support the 3rd party add-ons without being able to pick and choose where a hook might go, otherwise I’m working within the constraints of what the add-on provides, which makes it more difficult. I could provide some guidance to Bryan if you choose to go that route. Ideally he would add hooks to Blocks, then write a new extension that uses those hooks to add the support. That way Blocks doesn’t have Publisher specific code in it.
Nick Johnson
Comment has been marked private.