With Views I created several pages and defined their paths like:

section1/agenda
section1/users

This works well, but when I enable Subpath Alias, I can't access these views anymore. Instead they direct me to section1

Disabling Subpath Alias makes it work again.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

RobNL’s picture

I experience the same problem as oBirdman describes. Disabling Subpath makes it work again, but I found an other solution.

I renamed the views in:

section1-agenda
section2-agenda

and then I added the URL aliases:

section1-agenda --> section1/agenda
section1-users --> section1/users

Then the views work with the Subpath Alias enabled. It is a bit curious, but for some dynamic theming reasons I need the 'section1/' in my URL's.

tim.plunkett’s picture

Title: Subpath Alias breaks Views » Subpath Alias breaks Views and Devel

Also breaks Devel's dev load and dev render tabs.
The error given is "too many redirects".

akhodakovskiy’s picture

Ajaxed pager in Views doesn't work as well.
I think module should make Views hook it's method to obtain proper system path.

nagiek’s picture

subscribe

ManyNancy’s picture

I also had a problem with ajax pager. I didn't realize it was this module.

Also the same problem as topic starter.

Please fix! This is a great module. Thanks!

ManyNancy’s picture

Priority: Normal » Critical
ManyNancy’s picture

Version: 6.x-1.0 » 6.x-1.1
kaianine’s picture

i have this problem as well, with the subpath.

in my instance, using subpath w/ ubercart products, the edit link for the product also does not work, returning a browser-based looping redirect error. (as mentioned by another user above, my node's Devel links are also broken when subpath is enabled)

disabling subpath returns the link to it's original path (node/##/edit) allowing the edit link to function as intended.

smk-ka’s picture

@kaianine: do you have the Global Redirect module installed? If so you'll find the solution here: #346911: Redirect Loop and custom_url_rewrite ignored.

iva2k’s picture

subscribe

iole’s picture

Same issue here. I would love to use this module, but it stops the Calendar module's calendar view from displaying anything but the default view, as it seems to stop the view from seeing any arguments.

thijslemmens’s picture

subscribe

flips’s picture

Same issue here.

Jerome F’s picture

Subscribing

If this module breaks views and panels arguments I can't use it.

blueblade’s picture

subscribe

Mars2012’s picture

Anyone has a solution for this?

I have see drupal webpages which work just fine with the subdomain.

Mars2012’s picture

SOLVED!

Unistall the module Sub-path URL Aliases and maybe you don't need the URL alter either.
Install the module Extended path aliases.

Follow the Readme.txt to install this module.

It's very easy to configure.

Configuration = NONE ;-)

Enjoy

blueblade’s picture

Hi, you mean version 6.x-1.1?

Mars2012’s picture

Hi again,
Version 6.x-1.1 and 6.x-1.0. These module have bugs.
The two modules Sub-path URL Aliases and URL alter (needed by Sub-path URL Aliases) don't work together.

The module Extended path aliases work 100%.

Regards

crea’s picture

Subscribing

YK85’s picture

subscribing

Cyberwolf’s picture

Subscribing.

jleinenbach’s picture

Dave Reid’s picture

Status: Active » Closed (duplicate)

Sounds like this has been confirmed multiple times that the problem lies in Global redirect.

Stilgar’s picture

Status: Closed (duplicate) » Active

I confirm Views' page malfunction without Global redirect installed. Do you need reproduction on vanilla Drupal?

ajdonnison’s picture

I can confirm the problem exists, and is related to the custom url rewrite functions. If you install the facebook integration module it installs its own custom url rewrite functions, so url_alter cannot implement its own, and the problem goes away. Investigating further.

*update* - definitely a problem in subpath_alias_url_inbound_alter function. Looks like it doesn't know that the path already is in use by a view.

*further update* - The problem is that the view will register the path with the menu router, however the path aliasing occurs before the menu system starts up, and modifies the path that is looked for. Ideally the subpath_alter_url_inbound_alter function should check if the module views exists and if the path is already in the menu router. Unfortunately the alter function runs before full initialisation, so we can't query if views exists nor can we check the menu system, as it isn't loaded.

ajdonnison’s picture

The following patch addresses the issue, although I'm not happy that we have to do a database lookup to get this.

jasom’s picture

#27 not working for me, because if was causing by broken quicktabs js. So this comment is irrelevant.

DanielWashbrook’s picture

Thanks ajdonnison! #27 worked for me for views that had 'sub-directory' structures in their paths.

TommyK’s picture

Status: Active » Needs review

The patch in #27 works for me as well. Views paths are now working.

Hopefully this patch can be reviewed further by those more familiar with the code in this module.

wizonesolutions’s picture

Status: Needs review » Reviewed & tested by the community

Oh, snap! #27 worked for me too! Can't believe it!

I am going to be bold and RTBC this. DB lookup may suck, but the issue sucks more.

TommyK’s picture

Status: Reviewed & tested by the community » Needs work
FileSize
5.38 KB

Something about this patch stopped working for me. I cannot figure out what it is.

In trying to figure it out, I set up a barebones D6 install with just CCK, Date, Views 3, Sub-path URL Aliases (with patch in #27), and URL alter, (and Devel generate).

  • I created a bunch of path-aliased Page and Story nodes.
  • The Page nodes have a date field on them.
  • I created a View with an argument to show me Pages based on the Year.
  • In the argument I used Provide default argument > Raw value from URL > Path component: 2.
  • The Page display has a path of example/%/pages.
  • Works fine in the preview with "2012" as an argument.
  • Works fine at example/2012/pages.
  • I edit the path of a node (Story node) to be example/2012.
  • The view at example/2012/pages no longer works and I see only the node content from the example/2012 node.

I do not know why I reported the patch worked back in March. It must have seemed that way for some reason. It doesn't work for me any more and I'm quite sure I'm using the exact same versions of all the modules involved as I was back then. I attached the View if anyone cares to try to reproduce what I'm trying.