view has exposed filter on a node reference which relies on a view to select [#1432282]

When I expose the above mentioned filter is shows a lot of the code that would be used to make the items in the list link to the node the represent. The code is not active just shows in the select list. I attached a screen capture image.

Comment	File	Size	Author
	Capture node reference filter multi select in view has code.JPG	46.84 KB	chris pergantis

Comments

Comment #1

merlinofchaos commented 8 February 2012 at 06:04

Status:

Active

» Closed (won't fix)

I believe the node reference is allowing you to pick from a view, however you have markup in the view that is being used for the filter. You need to set the option in the node reference itself that cleans the HTML from the view. Alternatively you can go into the view it's using and disable all the markup in the field that it's using.

This isn't an exposed filter, it's a widget created by the references.module (I think).

Comment #2

chris pergantis commented 8 February 2012 at 20:42

@merlinofchaos - Just the bump I needed to fix the filter's select list. Thanks. I actually had to go to two different areas to remove the unwanted code. For those of you who might have a similar issue - here is what I did.

In the view that is used for the lookup for the node reference.
The first was the title field. There I removed the check box that added the link code.
The second was the Show inline fields | settings - the settings had a spot to turn off "Provide inline wrappers" that was adding the two span code pieces.

The reason we have to use a view for the node references is that the client is wanting to be able to remove items from the list for selection as the activities age and are replaced with new activities. Rather than have them delete those older activity entries we are just filtering out any unpublished in the view. They would then only have to move the status of an activity node to unpublished and thereby the relationships remain intact.