Closed (fixed)
Project:
Domain
Version:
6.x-2.0-rc6
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 May 2008 at 21:35 UTC
Updated:
6 Feb 2011 at 13:54 UTC
Jump to comment: Most recent file
Comments
Comment #1
agentrickardNot sure how to handle the "these terms are shared but these terms are not" issue.
Comment #2
nonsieKen, would you care to elaborate?
One example of this would be if you are using Domain to have different subdomains for locations and taxonomy to specify sections of the site. So for example you might have a vocabulary named sections and terms for sections such as jobs, about us ets. You might have jobs section for subdomain1 but not for other subdomains. There's also the issue of cascading domain access from parent term(or even vocabulary?)
I can see people using Domain Menu if they just want to have different menus for different subdomains but once it gets beyond single level architecture it's quite useless.
Comment #3
agentrickardI think you misunderstood me. I understand your use case. What I don't understand off the top of my head is how to select which terms would be available to all domains and which would not.
Comment #4
nonsieI've been thinking about trying to copy the idea behind i18n taxonomy. I might be completely off here - haven't really started to tackle it yet.
Comment #5
agentrickardAnd, to be clear, table prefixing is not the proper solution here. It is not that you want to share all terms on domains A, B, and D but not on domain C. You want to have some terms that exist on A, B, C, D and others that exist only on D.
I think the solution is a separate table that can be JOINed to the taxonomy tables. Taxonomy queries are affected by db_rewrite_sql(), so you should be able to run additional JOINs if $_domain is a specific value.
Does that make sense?
Comment #6
nonsieIt makes a lot of sense actually. I'll try to find some time over the next few days to get into it.
Comment #7
agentrickardJust remember that $_domain is a global -- so it is available to you at all times. You could also use hook_domainload() to load additional information onto that array.
Comment #8
agentrickardComment #9
summit commentedHi Any progress in this field please?
Is there otherwise a way to disable a term on a domain if all nodes in the term are referred to another subsite?
Will taxonomy access interfere with domain access?
greetings,
Martijn
Comment #10
agentrickardRead the provided documentation regarding multiple node access modules. The answer depends on what you mean by "interfere with."
As to progress, I am not touching any new requests until #298696: * ROADMAP * Please read this first is complete.
Comment #11
summit commentedHi Agentrickard,
I was speaking about drupal 5. And will look into it.
thanks for your answer. I heard you are in Hungary. Enjoy the meeting!!
greetings,
Martijn
Comment #12
agentrickardNo new features are being added to the Drupal 5 branch. It is not possible to maintain different features for multiple branches.
All new features currently go into D6, and get backported if really useful. This is the same method that Drupal itself uses.
Comment #13
chawl commentedHow about the ability to rewrite links for some taxonomy/term/% pages to a particular domain at least, a sort of pseudo-association ?
I am aware that this has to be a term level setting and Path Auto, Taxonomy Menu like modules will cause pain, but take this as a thought experiment.
As an example, an "all sites" menu could be created with Taxo Menu, and menu items could still point to their (pseudo) associated domains. This could also be very useful for free tagging indeed. Even if Path Auto had domain awareness, this combination could be the holy grail of a multisite.
Sorry for mentioning other modules but I'd like to cast a useful scenario.
Tx.
Comment #14
agentrickardYou can try setting 'taxonomy/term/*' or 'taxonomy/term/TID' to a 'special page request' to achieve something like the above.
Comment #15
chawl commentedYes, but all links are rewritten to current domain eventually. You can not send different terms to associated domains by this method, hence single vocabulary can not be used as a united taxonomy.
For example from the same vocabulary, PDA term could point to www.handhelds.net/taxonomy/term/38, LCD could point to www.visualsense.com/taxonomy/term/40. Moreover a menu (or tag cloud, free tags etc.) which could be created from this vocabulary might serve as an annex to navigate users accross member sites.
Sure with careful planning, some can be achieved, but if you have thousands of (hierarchical) terms from several vocabularies which evolve daily with the context of a big member sites network, this may not be a feasable option.
I will try different things with table prefixing, but I am not sure if I can manage something this synergetic.
Thank you.
Comment #16
chawl commentedNo success at all.
Is this feature request postponed indefinitely?
This seems rather crucial when I conceive the benefits (at least for our scenario) by the way.
Comment #17
agentrickardIt is postponed indefinitely unless someone else solves it, because I don't comprehend the issue well enough and have no project driving its completion.
Comment #18
xanderz commentedi`am who create this "Domain Taxonomy" (for D6) module and waiting for administration give me access to create this project. Temporary posting module here for testing by community. Instructions are included in README.txt file.
Comment #19
Skirr commentedAnyone tested it yet? It works pretty well for me.
Comment #20
mindgame commentedHi xanderz! A nice module, thanks!
To make it work with views I had to patch the file "views/modules/taxonomy/views_handler_field_term_node_tid.inc" (see attachment), otherwise the sql rewrite has no effect. (I posted a feature request for Views: http://drupal.org/node/483690)
Comment #21
xanderz commentedDomain Taxonomy project is published
http://drupal.org/project/domain_taxonomy
Comment #22
agentrickardAlright, I will add it to the list.
Comment #24
spicyguy commentedDoes anyone have clear documentation / tutorial on this module?
My scenario is this:
I installed Domain Access module and setup 3 subdomains. What I want is, when user clicks on Taxonomy term under the blog article, it should go to the subdomain what that term name.
Ex:
www.example.com
alpha.example.com
beta.example.com
Taxonomy:
Domains
Alpha
Beta
Theta
Alpha term should point to alpha.example.com, beta term should point to beta.example.com, etc
Comment #25
drasgroup commentedYes, this is what this thread was started about. subdomains -> taxonomy terms.
Comment #26
IckZ commentedanyone who got the "rewrite all terms to a single source" thing to work? At my installation there gets no url rewritten however the term is published to another domain than that one the visitor is viewing...
Is there maybe an other domain taxonomy modul?