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: Can’t Save Layouts - Gets All Buggy
Status | Resolved |
Add-on / Version | 2.0.7 |
Severity | Blocker |
EE Version | 2.7.1 |
Dustin Hansen
Oct 02, 2013Steps to reproduce issue:
1.) Start a new entry.
2.) Open the toolbar.
3.) Delete the “Options” tab.
4.) Save the Publish Layout for all Member Groups and Blueprint Templates.
5.) Refresh.
What you’ll see is that certain fields can no longer be used in the Publish layout at all (in my screenshot example, you’ll see the broken fields are “URL Title”, “Headline” (a custom field) and “Additional Content” (a custom field) and “Body Content” (a custom field).
Thoughts? If this cannot be resolved relatively quickly, what’s the return policy on the software? We love the concept of Blueprints but it’s simply not working as advertised right now, just a few hours in.
BoldMinded (Brian)
Its a 30 day return policy, but I have a feeling you’re running into a new bug in 2.7.1.
https://support.ellislab.com/bugs/detail/19745
BoldMinded (Brian)
And there is this: https://twitter.com/ejaedesign/status/385529223625981953
It seems like there are issues with the Publish Layouts in 2.7.1 all around.
Dustin Hansen
Thanks. You were right in that this is an EE bug.
BUT, now we have a new bug. When I try to load a different template via Blueprints, it stalls and the following error shows up in the Console:
uncaught exception: Internal Server Error,<div solid #990000;padding-left:20px;margin:0 0 10px 0;”> <h4>A PHP Error was encountered</h4> Severity: Notice Message: Array to string conversion Filename: database/DB_active_rec.php Line Number: 442 </div>{”error”:”Error Number: 1054<\/p>\n\nUnknown column ‘Array’ in ‘where clause’<\/p>\n\nSELECT
cf
.field_id
,cf
.field_required
\nFROM (exp_channel_fields
AS cf)\nJOINexp_channels
AS c ONcf
.group_id
=c
.field_group
\nWHEREcf
.site_id
= ‘1’\nANDgroup_id
= Array<\/p>\n\nFilename: third_party\/blueprints\/models\/blueprints_model.php<\/p>\n\nLine Number: 497<\/p>”}Dustin Hansen
Never mind… I think this is an issue because of entries created while the EE Publish Layout bug was present. Creating a new entry works fine.
If we have more issues, I’ll start a new ticket. Thanks for your help.