I need to get two independently operating tabsets on the same page. The first set is simple: topics A, B, C. The second set needs a selector, so that the topics A, B, C are in a category determined by the user. For example, we might have the categories "Animal," "Vegetable," and "Mineral," and each category would have its own set of topic tabs: Animal -> A, B, C and so forth.
I've been able to use tabs.module to get two sets of tabs onto the same page (by putting views into tabs, and nodes into views).
And I've been able to get the two to sets of tabs operating independently, since tabs.module depends on jstools.
What's defeating me is the selector. I've managed to capture a mouseup event from the selector so that a URL is created that addresses, e.g., Animal-> A (http://www.example.com//tabs?category=animal#topic-A) and my tabs module uses the URL parameters to construct the appropriate combination of views.
This does exactly what I want IFF I use devel->Clear Cache after the new URL appears in the browser bar -- but not unless I do that.
1. It isn't an issue with the browser's cache.
2. I tried forcing a window refresh within the JS driven by the selector, but that doesn't work.
3. I tried forcing my tabs module to do what devel does when the clear cache button is pressed, but that leads to an endless recursion (perhaps because the drupal_go_to?
4. Perhaps I need to add something to the PHP header in addition to creating the URL? If so, how and what?
I have the uneasy feeling that I'm messing with the way Drupal makes URLs in a way that Drupal will never be happy about. But it's frustrating to be so near and yet so far.
Thoughts, anyone? An alternative solution?
