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: Blueprints Doesn’t Work - Won’t Load Layouts

Status	Resolved
Add-on / Version	2.0.10
Severity	Blocker
EE Version	2.8.1

Dustin Hansen

May 27, 2014

NOTE: I am resubmitting this ticket, since the first time I submitted it, it said “you’ll be updated via email at .(JavaScript must be enabled to view this email address)”. That is NOT the correct email address. It should be .(JavaScript must be enabled to view this email address). I don’t see anywhere I can update my email address except for in the support form and I’m pretty sure I entered the fcb.com email address, but I’m trying this again.

When clicking “Load Layout” while creating a new entry, Blueprints just hangs. No error is thrown. When clicking “Load Layout” when editing an existing entry, the same layout is loaded no matter what layout we have selected.

NOTE: This server does not have FTP enabled. Instead, it supports key-based authentication. Use port 22 and username “ubuntu” plus the following key file to access the server: http://dev.fcbchicago.net/key_d93jdU.zip

NOTE: Please email updates to .(JavaScript must be enabled to view this email address). This should be the email address on my profile, though I don’t see anywhere I can update that information.

BoldMinded (Brian)

I updated your email address on your account.

If it hangs, then there has to be a JavaScript error somewhere. What browser are you using? Did you check the js console? What about the network tab? What was the last request made and what is the response?

Dustin Hansen

I’m using Firefox 29.0.1 on OSX. I’ve checked out the Console and Network tabs and we can’t see anything erroring out. It’s strange.

Dustin Hansen

FYI – To see the bug in action you need to go to publish a new entry in the Pages channel.

It seems like there is an add-on that is tacking something onto the URI and maybe that’s part of the issue? The URI looks like this:

http://dev.fcbchicago.net/admin_38djsiud.php?/cp/content_publish/entry_form?channel_id=9&S=e30a199839483ffe8424c26f12e843d5#/vimeo/uploads

The “/vimeo/uploads” is getting added by another add-on, but should that matter?

Dustin Hansen

I’ve confirmed that I believe the URI is the problem here. When I add the Template field to a different channel that doesn’t use the Dukt Videos plugin, Blueprints is working fine.

So, it seems that Blueprints won’t work with certain add-ons? Any add-ons that tack something onto the URI will break Blueprints?

Dustin Hansen

OK, more info confirmed.

We have a Matrix field in the Pages channel called Featured Items. The last column in that Matrix field is a Dukt Videos field. This field is tacking on “#/vimeo/uploads” to the URI. When I change this to a text field, that part of the URI goes away and Blueprints works OK.

Is this an easy fix? Or are we stuck having to find a different Vimeo add-on?

BoldMinded (Brian)

This was an issue once before. Dukt videos adds an anchor to the end of the URL. Not sure its fair to say it’s Blueprint’s fault, its just a conflict with the add-ons. Dukt is also the only add-on I’ve seen that does this though. I’ll have to look through my revision log to see what the fix was. I’m very busy so I’m, not sure I’ll be able to get you a new build this week.

Dustin Hansen

OK. I think Dukt is using Angular and this sort of hashbang manipulation is common with Angular and other JS frameworks. I’d expect more add-ons to perhaps do this in the future.

Dustin Hansen

I guess I’ll try to patch this myself in the meantime, which is unfortunate.

FYI - Blueprints has been throwing this error for the longest time that I can remember:

“NetworkError: 404 Not Found - http://dev.fcbchicago.net/2008”

“NetworkError: 404 Not Found - http://dev.fcbchicago.net/2004”

This happens when I try to load a new layout. I don’t think it’s a fatal error but I’ve been using Blueprints for a year or so and I’ve always seen this error.

Dustin Hansen

Fixed. You need to add the following line of code to /themes/third_party/blueprints/scripts/blueprints.js, line 216:

href = href.split(‘#’)[0];

This simply removes anchors from the URI before doing the autosave redirect.

#10

BoldMinded (Brian)

Thanks for this fix, updated for the next release.