According to merlinofchaos, the %views_arg menu loader is only necessary if the argument needs to be validated. Attached patch adds logic to avoid using the menu loader if the related argument doesn't require any validation.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

brianV’s picture

Doh. Text editor inserted the changed code where I thought I told it to overwrite.

Revised patch attached.

longwave’s picture

Revised version of the above patch attached. This correctly handles displays with inherited arguments, and also checks the correct "no validation" type, which is "none" instead of "default".

dawehner’s picture

Status: Needs review » Reviewed & tested by the community

* Both in views2 and views3 the validate_type is "none".
* Manual testing of the feature worked fine. (checking the menu router item)
* Code looks fine

merlinofchaos’s picture

Status: Reviewed & tested by the community » Needs review
$key = $name . ':' . $display_id . ':' . $value . ':' . $index;

Then use $key in all the places the calculation is used.

The only place that : is a valid value is $value so you shouldn't get any weird combinations that can masquerade as other combinations.

merlinofchaos’s picture

Status: Needs review » Reviewed & tested by the community

Disregard #4, wrong issue.

merlinofchaos’s picture

Status: Reviewed & tested by the community » Fixed

Patches like this remind me that the project has gotten so big that easy, obvious fixes don't happen just because they're so small I never get to them in the giant pile of things I can do. I know this should happen but when I sit down to work, it never ends up on my plate.

I'm glad someone else did this, because the patch is dirt simple and a good improvement. Applied to all branches.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.