do views work with domain access in drupal 6.17 ? (i had to choose a 7.x vs. for "version"!)

please help - I am at the end of a production project ! I am using drupal 6.17 and the latest production versions of all my required modules. these include domain access (incl domain views). When i import views from sites that used to reside in their own drupal installation - I am experiencing a fatal behaviour and may have to abandon the amalgamation of many sites using domain access.

basically, the views page-display's and menu entries disappear periodically. I can add 1 domain with views, but as soon as I add a 2nd, the views from the first disappear. I can make them re-appear by editing and saving one of the missing views.

I am using the default table prefixes - which create views tables with domain prefix for each domain.

any help greatly appreciated !

Comments

agentrickard’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

There is no Domain Prefix for Drupal 7.

elliottbrown’s picture

thanks for your reply agentrickard. I am not sure I understand it. I am using Drupal 6.19. When I posted this bug - 6.19 was not an option. Not sure why. Should I be able to get views working in multiple sites running on Domain Access ?

agentrickard’s picture

Project: Domain Views » Domain
Version: 7.x-1.0 » 6.x-2.7
Component: Code » - Domain Views

In Drupal 6, Domain Views is part of the main module. That's why. 6.19 is the Drupal release version. 6.x.2.7 is the module release version.

Updating meta-data.

You say you used table-prefixing on Views. Which tables did you prefix? Are you exporting Views to code?

Normally, Views are used across all domains. There is a provided Views access plugin that restricts View access per domain per view.

elliottbrown’s picture

thanks rickard- i appreciate your help.

all in my Views Section at admin/build/domain/prefix is set to "create".

\Views
- cache_views
- cache_views_data
- views_display
- views_object_cache
- views_view

I did import my views using Views export/import module. I pasted from the clipboard rather than exported a file.

However - i also get the same behavior with brand new views created in the sites already in a domain_access configuration. I could start afresh and document a walk through to reproduce this if that would be helpful.

Ideally, I would really like to have views separated by domain. I understand that there are filters for active domain and that they can be viewed across domains - but I have e.g. a view in one site of casino promotions and in another site a view of recent poker strategy articles. the node types they contain, and the nodes themselves are isolated by site.

Is it possible using DA 6.x.2.7 with its included DOMAIN_VIEWS to have views also separated by domain ? Could the disappearing be a caching problem?

any insights greatly appreciated.

agentrickard’s picture

With that setup, the View should be stored in the database for the active domain _from which the View form is entered_. Make sure that you actually have created tables for each domain. (Just setting the defaults is not enough if the domains were already created.)

Normally, I would just use the access filter, shown here --> http://skitch.com/agentrickard/d6f3p/domain-views-access

elliottbrown’s picture

i have domain-prefixed tables related to views.

e.g. i have added e.g. domain_34_views_view (3 records) and domain_46_views_view (2 different records)

also have domain_34_views_display and domain_34_views_object_cache - for each of my domains in my MDS (my acronym for DA-based multi-domain server).

The views work - but only in 1 domain at a time. editing in a domain causes the views in the other domains to fail. they do not disappear from the domain_XX prefixed DB tables - but their page-displays return 404. until you edit them. then they re-appear but views in another domain disappear.

I am grateful for your help. how can I provide more useful information ? shall I document a walk-through from a fresh 6.19 installation ? would you like to see the problem on my server ? I am new to Drupal and so don't know procedures well yet.

Thanks !

agentrickard’s picture

That sounds like a menu caching issue. Are these Views being added to the menu through the Views interface?

elliottbrown’s picture

yes. for each view I have a page display. these pages have an associated URL and primary navigation menu entry. BOTH the menu entry and the page disappear. By this i mean I can normally go to e.g. domain.com/view_name and see my view's page display. sometimes this will return 404 - page not found, although the view is still in the DB and can be seen in the list of views. It can be "revived" by simply editing and re-saving the view - but then the views from another domain disappear - as though there can only be one set active at a time.

This is the last stumbling block preventing me from amalgamating approx 50 sites into 1 MDS. (e.g. http://theflop.net and http://gimmecasinobonus.com). The time savings in having to administer modules, configurations, users and privileges in 1 MDS vs. 50 separate Drupal installs is HUGE.

thanks again, rickard, for your ongoing help and interest.

agentrickard’s picture

Status: Postponed (maintainer needs more info) » Active

I suspect you are having an issue with {cache_menu}. You might have to prefix that per domain as well.

agentrickard’s picture

Status: Active » Closed (works as designed)