Using the Insert View module, I am displaying a View inline on a standard page node. The view has one exposed filter corresponding to a CCK text field. For some reason, as soon as the exposed filter is invoked by the user, the URL is changed to something like this:

http://examplesite.com/?field_myview_value_many_to_one=category

I don't want this behavior. Instead, I want users to stay on the same page. I assume this behavior is related to the "unlock operator" option, but that option is not actually checked. Here are my options:

Operator - "Is one of"
Reduced duplicates - unchecked
Unlock operator - unchecked
Optional - unchecked
Force single - checked
Remember - Unchecked
Limit list to selected items - checked

What am I missing here? (Please let me know if I am not providing enough info).

CommentFileSizeAuthor
#14 insert_view.diff614 bytesDave Cohen

Comments

dawehner’s picture

Project: Views (for Drupal 7) » Insert View
Version: 6.x-2.11 » 6.x-1.x-dev

Insert view should set the path. $view->override_path.

silurius’s picture

Title: Exposed filter changes path » Exposed filter changes path of node running Insert View
Project: Insert View » Views (for Drupal 7)
Version: 6.x-1.x-dev » 6.x-2.11

Accidentally posted issue to Insert View issues queue, moving to Views issue queue.

Edit: Oh, I see you moved it, dereine. Thought it was my bad! :)

silurius’s picture

Project: Views (for Drupal 7) » Insert View
Version: 6.x-2.11 » 6.x-2.x-dev

Moving issue back to Insert View since it sounds like that could be where the issue is.

Dereine: Insert view should set the path. $view->override_path.

Dereine, are you referring to an option I should set in the Insert View brackets? I will look into how to do that next.

dawehner’s picture

Oh i'm referring to the views api. Perhaps the insert view module has a bug here.

silurius’s picture

Okay, it sounds like we are on the same page then. The more I test this issue, the more it feels like a bug. Hopefully someone will come along and verify that. Thanks for the input!

silurius’s picture

I came up with a workaround for my problem that doesn't involve the Insert View module, so I probably won't be monitoring this issue closely at this point. I might be willing to test a patch or something, though.

stephen ollman’s picture

I'm having the exact same issue.

I have a view associated with a node via the insert view command [view:xxxxxx] which works as expected, but as this view is exposed the filtering does not set the variable to the current path, instead it move back to the root /.

Not sure if its a Insert Views bug or a Views bug.

Either way it would be nice if an exposed view used in an 'insert view' worked as it should.

I look forward to this being solved.

stephen ollman’s picture

Priority: Normal » Major

One way around this is to turn on 'Use AJAX' in the view itself. This way the page is not recalled.

komlenic’s picture

I am seeing this bug in D7 version as well.

acbramley’s picture

+1 this is happening on D7 version as well, enabling AJAX as a workaround for now

Ankabout’s picture

This is happening with me as well, even with AJAX turned on. It basically reloads the page instead of just the block...

Ankabout’s picture

Version: 6.x-2.x-dev » 7.x-2.0

Oh and since it's happening in D7...

bcobin’s picture

I think I'm running into the same issue - see https://drupal.org/node/2072123

Did anyone find a solution here? Thanks...

UPDATE: This looks like an issue with Views and not Insert Views per se - continuing my inquiry at https://drupal.org/node/1109980

Dave Cohen’s picture

Category: Support request » Bug report
Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new614 bytes

This is solved (I hope) by explicitly setting $view->override_path. See https://www.drupal.org/node/525592#comment-1833824

igor mashevskyi’s picture

Status: Needs review » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Everyone can apply the patch above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.