Will this work with Pathout for the glossary/term pages

I cannot seem to make it work, will I need to do each manually?

Comments

nancydru’s picture

I would probably have to do some work with the Pathauto maintainer to figure out what to do. #309820: Update API.txt for other modules

tseven’s picture

I would also like to see pathauto implemented.

Thanks for the great module!

mandclu’s picture

Seems to work OK with Pathauto for me.

nancydru’s picture

Status: Active » Postponed (maintainer needs more info)

@surge_martin: Perhaps you could share the path set up you are using?

mandclu’s picture

Sure, the site where I've been using Glossary is a Motocross News site.

Specifically, the section on riders is really a directory of pathauto-generated URLs for taxonomy pages (each rider is a taxonomy term):
http://www.directmotocross.com/category/riders

The tricky bit for me was that each taxonomy page is actually a panel (I needed to have more structure in the page). The solution was to set the path for the panel to be taxonomy/panel/%. As far as I can tell, Drupal is internally able to determine that the path Glossary inserts into the copy should be translated into the pathauto version. You can see an example of the page here (it actually contains a link to itself):
http://www.directmotocross.com/category/riders/colton-facciotti

That self-link is one of the issues I am still trying to resolve, the other is that whenever I edit a node I end up with duplicate icons.

nicholasthompson’s picture

Title: Path auto » Pathauto glossary term page
Version: 6.x-1.6 » 5.x-2.x-dev
Category: support » feature
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new4.06 KB

Sorry to change this back to 5.x-2.x but that's what I've written the patch for. If I get time I will try to port it to 6.x-1.x too...

This patch adds a new configuration fieldset to the Pathauto configuration page which allows you to define your custom path auto paths for "glossary/term/[tid]" pages.

Any thoughts?

bago’s picture

@nicholasThompson: I'm using "per-letter" glossary pages and I currently manually created the aliases from "glossary//lettera" to "glossary//letterz" so to name them "glossario/a" to "glossario/z" that was much better for my structure. Could this patch also handle the pathauto stuff also when using "per-letter" pages instead of term pages?

nicholasthompson’s picture

Possibly - I'll have to take a look.

netentropy’s picture

i really look forward to the 6.x version!

websites-development.com’s picture

so do I

nicholasthompson’s picture

Title: Pathauto glossary term page » Pathauto integration
StatusFileSize
new6.72 KB

I've updated the patch...

Glossary now provides a "glossary-letter" token for taxonomy terms. This is literally the first letter of the term name. It will also generate glossary/[vid]/letter[a-z0-9] aliases too.

This is still Drupal 5 only, but I'll probably try to redo the patch for D6 at a later date (ie, when I need it).

This patch is running on the Glossary install for www.pponline.co.uk (which is still being populated... only 2 entries so far!)

nicholasthompson’s picture

StatusFileSize
new6.75 KB

Ok - fixed a small bug where pathauto's include file needed to be included on hook_taxonomy.

This module is now working perfectly on www.pponline.co.uk (live site). I imported about 200 glossary items with a small script and it does the job fine.

EDIT: See the Glossary here: http://www.pponline.co.uk/glossary

nicholasthompson’s picture

Title: Pathauto integration » Pathauto & Nodewords integration
Priority: Normal » Critical
StatusFileSize
new7.5 KB

Ok last one... Nodewords integration for better SEO... This patch greatly enhances the search engine friendliness of these pages.

nicholasthompson’s picture

Title: Pathauto & Nodewords integration » Pathauto, Nodewords and Page Title integration
StatusFileSize
new8.21 KB

Right.. another one.

This one includes better integration for my Page Title module. All glossary/term/[tid] pages are picked up and will use the glossary vocabulary associated with the term. This means if you have multiple glossary vocabs, then each one can have its own Page Title "pattern"...

For example "Definition for: [page-title]" could be for a glossary vocab for complete phrase words (such as Repetitive Strain Injuries) but you might also have another vocabulary for abbreviations which could have a Page Title pattern of "Abbreviation meaning: [page-title]".

Without the addition of my two Page Title hooks, all Glossary pages would be rendered using the default Page Title pattern (which most people set to just [page-title]). This means the Glossary Page Title would just be the term name (maybe just RSI, using the example above).

I'd love to see this patch get into the 5.x-2.x-dev branch. It hugely improves the SEO of this already fantastic module.

nicholasthompson’s picture

Damn - minor bug in patch...

+function glossary_page_title_pattern_alter(&$pattern, &$types) {

Should actually be...

function glossary_page_title_pattern_alter(&$pattern, &$types = array()) {
netentropy’s picture

can't wait for the D6 version, do you think this will make it into the actually Glossary code?

drupalfan2’s picture

Is glossary_pathauto.patch already implemented in the latest module version for Drupal 6?
How can it be implemented?

netentropy’s picture

yes i am very eager for this as well. i tried to do it myself but royally mucked it up

Brian294’s picture

I just published a 6.x module that marries the best features of page_title and nodewords. Wildcard paths and tokens supported. Great for tough-to-reach page titles in Views, Panels, and other non-node paths!

http://drupal.org/project/nodewords_pagetitle

Let me know if this helps solve your immediate problem for 6.x.

Peace,
Brian

ecoment’s picture

Hi,

is the patch already implemented for 6.x? I'm running version 6.x-6.16 of the glossary modul and have the configuration field in pathauto, but it just doesn't work. It creates alias like "myalias/term.html" => "taxonomy/term/[tid]", but correctly the alias has to point to "glossary/term/[tid]".

Thanks,
Martin

Countzero’s picture

I'd be interested in aliasing glossary pages too. As for now, I think I'll do a blunt search/replace for 'glossary/term' in the source ... It shouldn't be too difficult to abstract the paths' elements in a variable.

What do you think ?

nancydru’s picture

Issue summary: View changes
Status: Needs review » Closed (outdated)