Hello!

So something strange has happened to me. I had a project where I was using beans and boxes side by side. Don't ask why! I never insallted entity_boxes, however, somehow the core boxes module thinks that bean is entity boxes?

Thus my situation is that I've created an entire site with 6 different block types, that all for some reason are boxes block types despite not having this particular module installed. They show up in the boxes permission list even.

This fluke wouldn't be so much of a problem if it werent for the fact that the boxes per-bundle permissions don't work, thus, no matter what I do, unauthenticated users cannot see these block types. I'm guessing its because the per-bundle permissions are applying to beans and not boxes, thus the access callbacks are misfiring.

Also, I can't uninstall either module, because both think that the fields attached to the block types are theirs!

I am probably just going to do a quick rebuild using bean, but just giving you a heads up! I'd be glad to supply some more info if folks want to replicate this issue. I know you are considering or are merging with the bean folks, so it might be nice to figure this out if it comes up again!

Also, I'd be glad to move this issue to the entity module itself, just thought that this would make it to folks who are working on entity_boxes who might be close to everything thats happening here!

Comments

rerooting’s picture

Ok looking at the commitlog this is definately happening in boxes core. Moving the discussion over!

rerooting’s picture

Er in the main boxes module. Need to stop using the word core so losely! But who knows, maybe all this magic will end up in D8 ;)

rerooting’s picture

Status: Active » Closed (works as designed)

ok moved this over to #1626576 sorry to bother!