I am trying to use [vocab]/[title] or [cat]/[title] for node paths and they work fine root/vocab/title when bulk generate pathauto run is done... yet upon initial node creation I get only the root/title.

A fix for this would be much appreciated!!

CommentFileSizeAuthor
#12 pathauto_screen.gif10.4 KBvatavale
#10 pathauto_47_free.patch4.67 KBgreggles

Comments

nathanraft’s picture

nathanraft commented

Let me expand on this a bit....

Because I want blocks to show based on what vocab or vocab/cat the node it on I need the node paths to carry the proper url so i can set the blocks to show accordingly for example cars/* would show a block of most popular cars on each car node.

Yet this does not happen unless I bulk update each a node is created.

When I create a node I see (with verbose on) that my alias has been created. This prints on top of the screen:

* Created new alias thistestnode for node/11
* Your Page was created.

Yet the alias is not according to the structure I gave it in pathauto. The node created is http://mysite.com/thistestnode
it should have been http://mysite.com/vocab/cat/thistestnode

As bulk update works fine it appears that the node is created with the information it has at the time i.e. no vocab/cat yet. This maybe completely wrong but is this the problem? So after the node is created and you go to bulk update the vocab/cat are known and thus it works fine. So would pathauto need to run directly after the node creation instead of before as the logs would suggest?

Anyway this is way over my head but I figured I would try and help whom ever would take the time to work on this... Are there others out there that are having this problem.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Closed (duplicate)

There are several other issues in the queue related to this problem so I'm marking it as a duplicate.

It would be great if you could clarify what kind of vocabulary you are using when you observe this behavior (my guess is freetagging).

nathanraft’s picture

nathanraft commented

Greggles,

I just tested this more based on your comment.
Yes, indeed this is happening only when freetagging is around. That is, even on a page with both a drop down and freetag for setting the category I have this problem. Even if I don't enter anything it to the freetag field. If I only have a dropdown it works just fine.

Thanks for any help you can provide.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

NathanRaft - Thanks forgettng back. If you look in the issue queue you'll see a couple others for freetagging. As you noted in the other issue it's just a patch for 5.x and we also need a fix for 4.7. The necessary code for 4.7 is inside of that same patch, but it will be slightly different. I'm making a bunch of fixes for 5.x right now and will get back to the 4.7 branch shortly (though the time I have to spend on pathauto is limited...).

In the meantime, if you want to take a stab at the patch, by all means please do!

nathanraft’s picture

nathanraft commented
Priority: Normal » Critical
Status: Closed (duplicate) » Postponed (maintainer needs more info)

I am marking this as critical so that people read this.

Many thanks for the response Greggles

I have looked at the code for the 5.X patch and it is just over my head. I completely understand the time constraints and am quite impressed with the efforts you put forth.

As this one of the most important modules in drupal (as I see it) from both a usibility standpoint for making blocks show in the proper places as well as getting search engines to index the site in a meaningful way, I am willing to kick in some $ for your greatly appreciated efforts and the 4.7 patch.

I will start the donation out at $100. Please send me details on how to submit a donation or an address to send a check.

I hope that this motivates others who are taking advantage of the talent behind drupal to do the same! Come on people where would we be without pathauto???

FiReaNGeL’s picture

FiReaNGeL commented
Status: Postponed (maintainer needs more info) » Active

active (need more info) isnt selected by default in the issue list and wont show up for the vast majority of people looking at this list. As you want to draw attention to it, switched to active.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Node paths only working on Bulk update » 4.7: Node paths involving categories only working on Bulk update

Just changing the title to help track this better. Now that we've got a solution for 5 this will be easier to do.

ahneill’s picture

ahneill commented

I wanted to verify that this is still a problem with 4.7 and freetagging. Definitely a critical issue! Would be happy to contribute something towards fixing this in 4.7 if someone sends me a paypal address...

thanks

art

nathanraft’s picture

nathanraft commented

Yes still an issue. Anyone still out there willing to help sponsor the fix?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Needs review
StatusFileSize
new pathauto_47_free.patch4.67 KB

Ok- try out this patch.

I've done some initial testing and it seemed to work alright, but I didn't do thorough testing.

Thanks.

nathanraft’s picture

nathanraft commented

First of all. Thanks!

This already solves the [vocab]/[Title] problem!

This is what I have found.

Creating [vocab]/[catpath]/[Title] and other node specific aliases works correctly for established categories. Yet, when creating a new node and a new category (using freetagging) at the same time the node alias is created as [Title] only.

From the drupal_set_message output it appears that the node alias is being creating first and then the category alias. Thus, when the node alias is being created there is not yet a category path to include in the node path.

Maybe making the category alias first will fix this...

I have a bunch more testing scenerios to go through and will get back on those as well if I find anything.

vatavale’s picture

vatavale commented
Title: 4.7: Node paths involving categories only working on Bulk update » 4.7-5.x: Node paths involving categories only working on Bulk update
Version: 4.7.x-1.x-dev » 5.x-1.1
StatusFileSize
new pathauto_screen.gif10.4 KB

I have the same problem, but i don't using freetaging. I use Category module and use [vocab]/[nid] pattern for Pages.
Bulk update create fine aliases, but then i update any Page, the alias changed (only get [nid] argument).

I notice that this bug not extend on category or container nodes. I have [categorypath]/[nid] pattern for category and container nodes, and url looks fine then i update category or container nodes.

Drupal 5, Pathauto 5

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Version: 5.x-1.1 » 4.7.x-1.x-dev
Status: Needs review » Needs work

@vatavale - please don't hijack the issue. this issue is for the 4.7 version (which kinda works, but frankly I'm not planning to spend any more time on this issue - though I welcome patches or bounties to get other folks interested in it).

@vatavale - if you haven't already, please submit an issue for your specific case. Frankly, though, I will want proof that this is a problem in pathauto and not just a problem with the way that category module works. Category is a total departure from drupal's core style of handling taxonomy so it's up to category to make itself work with pathauto, in my opinion.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Needs work » Fixed

I believe that the only work this needed was to work with freetagging terms that were created during node submission. That's been fixed in 5.x using the weight system.

@NathanRAFT - thanks for your help on this issue.

I just applied this to 4.7.

nathanraft’s picture

nathanraft commented
Status: Fixed » Closed (fixed)

Glad to hear it... My pleasure helping out.. .