Locale module not handled properly
agentrickard - June 9, 2009 - 14:16
| Project: | Domain Access |
| Version: | 6.x-2.0-rc8 |
| Component: | - Domain Theme |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
| Issue tags: | locale module |
Description
The domain-specific theme settings do not seem to load properly when a site is offline. This warning is produced:
warning: Attempt to assign property of non-object in /Applications/MAMP/htdocs/drupal-6.12/includes/theme.inc on line 1816.
#1
#2
This is actually an issue with the language setting.
$variables['language'] = $GLOBALS['language'];$variables['language']->dir = $GLOBALS['language']->direction ? 'rtl' : 'ltr';
Odd. It went away while I was testing it.
Can anyone reproduce?
#3
This is caused by some bad language value handling, especially when Locale module is disabled.
#4
Better fix, since we have to ensure that local is enabled.
#5
Committed to HEAD.
#6
Actually, this only gets ported if language support does. So closing.
#7
This reopened issue is a catch for a duplicate issue #497464: warning: Attempt to assign property of non-object
Hello!
I have MySQL 5
PHP 5
I have a domain: example.com and several sub domains; subdomain1, subdomain2, subdomain3, ...
1. I configured a separate theme for subdomain1 and the settings came through perfectly.
When the component Domain Theme was enabled and theme custom configured for subdomain1.example.com, I received the following error on every page in example.com and subdomain1.example.com:
warning: Attempt to assign property of non-object in /example.com/public_html/includes/theme.inc on line 1807.
2. With the Domain Theme disabled and uninstalled the warning still remain in subdomain1.example.com but NOT when visiting example.com.
3. With the Locale module enabled AND Domain theme module DISABLED the error disappeared.
4. With the Locale module enabled AND Domain theme module ENABLED the error disappeared.
It looks like I have to have the locale module turned on ;-)
Hope this is enough info?
#8
Yes. Thanks.
#9
Try this patch. Apply from the domain root directory. (It actually patches Domain Conf.)
#10
The following has been committed to HEAD.
#11
Automatically closed -- issue fixed for 2 weeks with no activity.