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: One global structure template
| Status | Resolved |
| Add-on / Version | Publisher 3.3.1 |
| Severity | |
| EE Version | 5.4.0 |
Studioweb
Jul 28, 2021Hi,
Somehow Publisher let’s me assign a structure template for each language but I just want to use 1 main template without going trough all versions to update a template. I’ve added Structure as ignored field-type but this doesn’t solve the issue. Any tips and do I’ve to add this field as ignored field-type or not?
BoldMinded (Brian)
The Structure Template field isn’t an ignorable option because it’s a field from a 3rd party add-on. It would take a decent amount of work to add logic to support that, and I’m not sure it’s something I want to add. If the entry is created in the default language, all other languages will inherit the value of the template field from the default language when you save it, so in essence it is ignored if you don’t change it when editing entries in non-default languages. If you need to update a bunch of existing entries, then you’ll probably need to manually make the updates, or figure out the SQL query to make the update. Even then the exp_sites and exp_publisher_sites table has the template associated to the page, so those serialized arrays and json objects would need to be updated.