Drupal 7.16 installation. When the Domain Configuration submodule is enabled I cannot change aspects of my Content Types: unable to change available menus or change fields (the content type saves, but changes do not show). When I disable Domain Configuration my changes are there, but when I enable again, my changes are gone and cannot be used when creating nodes of the content type. It's like Domain Configuration uses it's own outdated snapshot of what the content type configurations were when it was installed. I've cleared the site cache many times, so it probably isn't caching.

CommentFileSizeAuthor
#5 Screen Shot 2012-12-12 at 5.48.24 PM.png45.39 KBagentrickard
#3 1863436-node-types.patch1.05 KBagentrickard
#2 1863436-node-types.patch436 bytesagentrickard

Comments

agentrickard’s picture

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

Where are you trying to make the changes? The Domain Configuration module does _not_ make the Content Type editing form domain sensitive. That form will always save changes to the primary domain.

I don't understand what the error is in the report. Please list the steps you take. The domains you have, and when URL (and domain) you are performing actions from.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Category: support » task
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new 1863436-node-types.patch436 bytes

This minor patch may help explain things.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
StatusFileSize
new 1863436-node-types.patch1.05 KB

Slightly better patch.

axxint’s picture

axxint commented
Version: 7.x-3.5 » 7.x-3.6

Thank you for the patch! I updated Domain Access to 7.x-3.6 and applied the patch to that version. I'm not seeing any differences in my ability to change any content types and I found an issue with maintenance mode.

I have 3 domains; I'll call them main.com, site2.com and site3.com.

With Domain Configuration Active

  • I go to main.com/admin/structure/types/manage/page to edit the basic page template (or any content type, but I'll use the page as an example here).
    • Domain access settings is set to "all domains" and "author's currently active domain."
    • Click on the "Menu Settings" section and make changes to available menus, click "Save content type".
    • Or Click on “Manage Fields” and make changes to fields; click “Save content type”
    • The content type saves.
  • I go back to main.com/admin/structure/types/manage/page and my changes aren't there.
  • I go to main.com/node/add/page and my changes don't show as options.
  • I go to Maintanance Mode at main.com/admin/config/development/maintenance and try to put the site in maintanance mode - it saves.
  • When the page refreshes, my setting is not there.
  • When I go to main.com from another browser, the siet is not in Maintanance Mode.

When I Disable Domain Configuration

  • I go to main.com/admin/modules and disable Domain Configuration, save.
  • I go back to main.com/admin/structure/types/manage/page to the available menus or manage fields and my changes are there.
  • I go to main.com/node/add/page and my changes show as options and can be used.
  • I go to main.com/admin/config/development/maintenance and Maintance Mode is on.
  • I go to main.com from another browser and the site is in Mantanance mode.

When I Re-Enable Domain Configuration

  • I go back to main.com/admin/modules and enable Domain Configuration, save.
  • I go back to main.com/admin/structure/types/manage/page and my changes are gone again.
  • I go to main.com/node/add/page and my changes are not options.
  • I go to main.com/admin/config/development/maintenance and it is not set to maintanance mode.
agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
StatusFileSize
new Screen Shot 2012-12-12 at 5.48.24 PM.png45.39 KB

I cannot replicate any of that behavior.

After applying the patch, you don't see a message at the top of the Content Type page? It should look similar to the attached.

If you don't see that message, something else is wrong.

agentrickard’s picture

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

Also make sure you didn't enable Domain Settings by accident. It radically changes the behavior. It also, however, gives you very large warnings on the page.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Needs review » Fixed

Committed.

   891b5f8..6b29f8c  7.x-3.x -> 7.x-3.x

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Wolfgang Reszel’s picture

Wolfgang Reszel commented
Version: 7.x-3.6 » 7.x-3.x-dev
Category: task » bug
Status: Closed (fixed) » Needs review

This bug still exists in the latest Dev (7.x-3.7+2-dev). I can't change the defaults in admin/structure/types/manage/XXX.

Maybe it's not a bug, but then the Message "This form submits changes to your default configuration." should also link to admin/structure/domain/batch/menu_options_XXX. I haven't realized, that these Options are also domain specific.

agentrickard’s picture

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

I cannot reproduce the bug.

Steps to reproduce, please. Error messages, log entries.

agentrickard’s picture

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

And what do you means by "can't change the defaults". Please give me a proper report.

Wolfgang Reszel’s picture

Wolfgang Reszel commented

I mean by "changing defaults" the normal page to edit content types at admin/structure/types/manage/XXX. Changing the settings there have no effect when Domain Config is enabled.

agentrickard’s picture

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

I cannot replicate that. I just changed the "Description" field of a node type with no problem.

I need exact steps to replicate. What fields? What values?

Wolfgang Reszel’s picture

Wolfgang Reszel commented

It only happens at the available menus (look at first post).

agentrickard’s picture

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

I can change available menus just fine. Granted I am user 1.

Now, you may be running into an issue with the Parent Item, because those could be access restricted. But that has nothing to do with Domain Conf, but rather Node Access.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Category: bug » support

What is more likely happening is that Domain Conf is overriding those settings on a per-domain basis, which is how the module works.

E.g. If you have saved settings for domain A, they have to be updated through the Domain Conf UI.

I suspect this is all "by design". The Available Menu settings can be set per domain. I suspect that you may have Domain Conf settings for your primary domain. If so, delete them using the Batch Updates tool.

But seriously, the OP and the title of this issue are entirely misleading if that is the actual issue.

axxint’s picture

axxint commented

Update: Everything is working. Part of the issue I had was misunderstanding, and the other part was a mysterious issue that just cleared up on it's own.

The available menus issue was working as designed. You cannot choose available menus at admin/structure/types/manage/content-type - you have to select them at /admin/structure/domain/view/#/config. Once I figured this out, I got everything working.

The other issue was that fields I created/changed on various content types were not showing up/not changed when I created content with the Domain Configuration module enabled. This issue just went away and I was not able to correlate its disappearance to any changes I made.

agentrickard’s picture

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

Odd. Sorry for your frustration.

Wolfgang Reszel’s picture

Wolfgang Reszel commented

Maybe the Form at admin/structure/types/manage/content-type could be altered by Domain Config so that the fields are disabled there for UX reason.

jweirather’s picture

jweirather commented
Issue summary: View changes
Related issues: +#2452013: Create Content Type "default configuration" warning message.

Created a related thread here: https://www.drupal.org/node/2452013

maxplus’s picture

maxplus commented

Thanks,
also found out that you need to use admin/structure/domain/view/#/config to change the default menu for a content type... (and not admin/structure/types/manage/#)