Closed (fixed)
Project:
Domain
Version:
7.x-2.11
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Mar 2011 at 03:14 UTC
Updated:
25 Mar 2011 at 15:51 UTC
Jump to comment: Most recent file
Issue from new Install, not from upgrade.
Condition:
- All Domain modules are enabled.
- A content type of 'page' has been created in 7.x, similar to 'page' in 6.x
Problem: After adding a new page (node), with the following settings selected:
- send to all affiliate
- published to the only affiliate so far created
- source domain is the only affiliate
The following error is generated on the next/confirmation screen (where 'n' is the node #):
Notice: Undefined index: 'n' in domain_get_node_domains() (line 1654 of /var/www/html/sites/all/modules/domain/domain.module).
In my domain.module file, line 1654 is:
return $lookup[$nodes];
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | 1080840.gineta-index.patch | 937 bytes | agentrickard |
| #9 | 1080840.gineta-index.patch | 809 bytes | agentrickard |
| #2 | 1080840.ununpentium.index_.patch | 354 bytes | agentrickard |
Comments
Comment #1
agentrickardWhat "next/confirmation" screen?
Comment #2
agentrickardI replicated this by simply saving the node. The attached should fix the error.
This fixes the notice, but I noticed a nasty problem with the overlay. #1081468: Redirects on save fail with Overlay.
Comment #3
ununpentium commentedConfirmed error fix. Thanks.
Comment #4
agentrickardAwesome.
Comment #5
agentrickardFixed.
Comment #6
agentrickardThis problem does not exist in 6.x.
Comment #7
gineta commentedSorry this path not work for me. Any other ideas?
Notice: Undefined index: 4 in domain_node_load() (line 1461 of /mnt/var/www/vhosts/gigalearn/httpdocs/sites/all/modules/domain/domain.module).
Notice: Undefined index: 4 in domain_node_load() (line 1462 of /mnt/var/www/vhosts/gigalearn/httpdocs/sites/all/modules/domain/domain.module).
Comment #8
agentrickardWhat are you doing when this error occurs? Please explain.
Comment #9
agentrickardThat second error is different, and theoretically should not occur, but we can account for it here.
Please review so we can get a bugfix release out tomorrow.
Comment #10
agentrickardSlight revision. Tests fine. Fixed.