Warning: Illegal string offset 'colspan' in PanelizerEntityNode->hook_page_alter()

Well, panelizer is not a part of backoffice ;)

Hmm. Something else there is modifying the node types list at admin/structure/types and Panelizer seems to be conflicting with some other change. I've no way of knowing what that change is, however.

Ah, that's us.
We are overriding the page callback completely.
Any advice on how I should proceed here?

My code is trying to add a column to the table.

I could add more verification that the table actually exists, or I could try to figure out what you're doing differently so I can handle both?

Take a look at the function that's dying? It's not terribly complex, it is just trying to make life easier on users so that panelizer info is available at admin/structure/types.

In the worst case we can add validation that the table actually exists and disable that code. In the best case we can make our paths close together so they can cooperate.

The problem is that commerce backorder is adding product display column as the second column in content types listing. Panelizer is setting the colspan of the second column because it's relying that it's the operations column. Here's a patch that changes panelizer to increase the colspan of the last column which should be the operations column.

This worked just fine in my testing. Thanks kimee!