Relation Select stopped working for me, and I am getting the following errors everywhere that the widget is shown:

Notice: Undefined index: #name in relation_select_exposed_form_after_build() (line 951 of relation_select.module)
Notice: Undefined index: #pre_render in relation_select_exposed_form_after_build() (line 953 of relation_select.module)
Notice: Undefined index: #name in relation_select_exposed_form_after_build() (line 974 of relation_select.module)
Notice: Undefined index: #pre_render in relation_select_exposed_form_after_build() (line 976 of relation_select.module)

Clicking the 'Search' button to search for compatible items to relate brings up an error box indicating:

Notice: Undefined index: entity_type in accept_exposed_input() (line 547 views/handlers/views_handler_filter.inc)

I know the fix for the #subform_name issue was to assign it to null if it didn't exist... but will that work if applied to the #name and #pre_render indexes as well? What reason would there be for those indexes not to exist in the subform element?

Thanks!

CommentFileSizeAuthor
#3 relation_select-1572534-3.patch8.28 KBshadybar

Comments

replicaobscura’s picture

replicaobscura
she/her
Primary language English
Location West Virginia
commented

I found the source of these issues--somehow the relation_select view broke.

relation_select_node still works fine, but relation_select does not.

When I look at the Views page, relation_select shows "Type: Broken" where relation_select_node shows "Type: EntityFieldQuery: Node"

Many other internal parameters of the relation_select view seem to be broken as well.

Fields:
Broken/missing handler
Broken/missing handler (Broken handler efq_multiple.label)

Filter criteria:
Broken/missing handler (= node)
Broken/missing handler (= )

If there is some reference I can use as to how those are supposed to be configured maybe I can fix it by editing the view? I've no idea how it got broken in the first place... other than that efq_views is under heavy development.

ben_scott’s picture

ben_scott commented

Hi -

Hmm, I did make some changes to relation select last week, although I wouldn't have thought it would affect the views. Are you using the latest dev release (released 11/5/12)?

If not, then yep, it sounds like something has changed in EFQ views. I'll upgrade to their latest release and investigate...

Cheers,

Ben

shadybar’s picture

shadybar commented
StatusFileSize
new relation_select-1572534-3.patch8.28 KB

To suppress the notices, here is a patch which added isset() around the indexes.

mrangryfish’s picture

mrangryfish commented

This is caused by EFQ Views removing support for Multiple as an entity query type:
http://drupal.org/node/1564740

Until EFQ Views supports multiple again (if ever? see http://drupal4hu.com/node/324) 'relation_select' (which needs eqf_multiple) view should probably be removed from this module.

steveoliver’s picture

steveoliver commented
Status: Active » Closed (fixed)

While Relation Select does support EFQ Views, it no longer depends on efq_views.module (as of Tue, 19 Jun 2012), and now ships with default standard views. Marking closed (fixed).