First, love the module. Thanks for all your hard work!

I first installed DA about a year ago, and successfully set up 3 domain records with alternate frontpages. All was well.

I have tried recently to create new records, but the alternate frontpage settings (admin/build/domain/conf/*) are not followed. Here is the behavior:

Set frontpage to a view for domain x. View has path of /foo-bar.
In separate browser, view domain x.
Domain x shows default frontpage for base domain.
Navigate to x/foo-bar.
Frontpage of base domain is displayed.

I have tried the following:
- Upgrading to 2.10 from 2.7
- Deleted and re-created test domains several times.
- Manually set the domain_conf blob in the DB to a copy of the blob for a domain that works.
- Disabled and uninstalled Mobile Tools.
- Searched and read similar issues on this project (which led me to kill Mobile Tools).

The original domains continue to work properly. I have checked my settings.php, and the DA include is the _very_ last item.

Thanks for any insight. :)

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Postponed (maintainer needs more info)

I wonder if this is because the path is a View page.

Does it work with non-View front pages?

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Working fine with a View on my tests.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

It could be, of course, that the site thinks you're on the primary domain.

nick johnson’s picture

nick johnson commented
Status: Postponed (maintainer needs more info) » Active

Same behavior with non-view front pages.

Yeah, I kind of figure this is not a bug. My guess is that DA has gotten into a wonky state through a few upgrades somehow. Likely my fault.

The two domains that still work (created a year ago) both use a view as their front page. This is why I thought using the domain_conf.settings blob from one of these might fix it, but no dice.

How can I check to see what domain DA thinks I am on?

I am toying with the idea of bringing the site into maintenance mode, uninstalling DA, and reinstalling from scratch.

Thoughts?

Thanks so much for your help.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

The best way is the domain alias block (if you are using that module). Or the domain list page, which puts the active domain in bold.

You can also just print the $GLOBALS['_domain'] variable using the debugging method of your choice.

If you uninstall, you will lose node access data, so that might mean starting over.

nick johnson’s picture

nick johnson commented
Status: Active » Closed (works as designed)

Update:

PEBKAC.

I forgot that a year ago I created a special theme for domains because my default theme has special handling for front pages and therefore did not show the front pages set in DA. Using the special theme, voila! All domains have properly set front pages.

Sorry for wasting your time, agentrickard.

Thanks.