You are here

README.txt in View Alias 6.2

Same filename and directory in other branches
  1. 5 README.txt
  2. 6 README.txt
  3. 7 README.txt
VIEW ALIAS

This module aids in the bulk creation and deletion of SEO friendly view aliases.

In the past I've worked on several sites that utilize a single view which takes in a single taxonomy term id to display a list
of related items.  And on these sites maintaining the url aliases for them was a pain to do by hand, so I wrote this module
to do the repetition for me.


SETUP
1. untar the tarball into your drupal modules directory
2. enable the module
3. visit admin/build/path/pathauto for configuration options.

Generating Aliases
View Alias is integrated with pathauto, (admin/build/path/pathauto).  So expand "View Alias Settings"
settings fieldset to select the views to alias.

Steps to make a view avaialbe to view_alias:
1. View must exist and have a page display.
2. Under Arguments, View must have an arg of "Taxonomy: TERM ID".
3. Under Validator options:
  a. Set Validator to Taxonomy Term, then select your term vocabulary.
  b. Set Argument Type to "Term ID"

In the 6.x version the views with term arguments and page displays are
automatically displayed for you to choose from.  Simply select the views
to alias and check the "Bulk generate aliases ..." box and Save the
configuration to kick off the generation.

/** NOT DONE YET **/
Recurring Aliases
This works of hook_taxonomy to update aliases when terms are updated, created or deleted.
For each view:
1. check "Create/Update/Delete aliases for <view-name> on term creation"
2. select the "Vocabulary to alias" from the select box.
3. Save configuration.


FAQ
WHY NOT JUST USE <view-name>/<term-name>?
I kept running into duplicate terms when not using the full path.  I also found that people were turned off by some of the special characters that showed up in the browser bar.

NO TOKENS?
Yep, no tokens, I didn't really see the need for them.  But if you have a good
reason for them.. let me know and we can figure something out.

Eric Mckenna, Phase2 Technology
emckenna@phase2technology.com

File

README.txt
View source
  1. VIEW ALIAS
  2. This module aids in the bulk creation and deletion of SEO friendly view aliases.
  3. In the past I've worked on several sites that utilize a single view which takes in a single taxonomy term id to display a list
  4. of related items. And on these sites maintaining the url aliases for them was a pain to do by hand, so I wrote this module
  5. to do the repetition for me.
  6. SETUP
  7. 1. untar the tarball into your drupal modules directory
  8. 2. enable the module
  9. 3. visit admin/build/path/pathauto for configuration options.
  10. Generating Aliases
  11. View Alias is integrated with pathauto, (admin/build/path/pathauto). So expand "View Alias Settings"
  12. settings fieldset to select the views to alias.
  13. Steps to make a view avaialbe to view_alias:
  14. 1. View must exist and have a page display.
  15. 2. Under Arguments, View must have an arg of "Taxonomy: TERM ID".
  16. 3. Under Validator options:
  17. a. Set Validator to Taxonomy Term, then select your term vocabulary.
  18. b. Set Argument Type to "Term ID"
  19. In the 6.x version the views with term arguments and page displays are
  20. automatically displayed for you to choose from. Simply select the views
  21. to alias and check the "Bulk generate aliases ..." box and Save the
  22. configuration to kick off the generation.
  23. /** NOT DONE YET **/
  24. Recurring Aliases
  25. This works of hook_taxonomy to update aliases when terms are updated, created or deleted.
  26. For each view:
  27. 1. check "Create/Update/Delete aliases for on term creation"
  28. 2. select the "Vocabulary to alias" from the select box.
  29. 3. Save configuration.
  30. FAQ
  31. WHY NOT JUST USE /?
  32. I kept running into duplicate terms when not using the full path. I also found that people were turned off by some of the special characters that showed up in the browser bar.
  33. NO TOKENS?
  34. Yep, no tokens, I didn't really see the need for them. But if you have a good
  35. reason for them.. let me know and we can figure something out.
  36. Eric Mckenna, Phase2 Technology
  37. emckenna@phase2technology.com