Active
Project:
Subsites
Version:
6.x-1.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Oct 2010 at 20:58 UTC
Updated:
24 Nov 2010 at 12:27 UTC
Jump to comment: Most recent file
When I create a node, and select a subsite, I get the following error:
Fatal error: Call to undefined function context_set_by_condition() in /var/www/vhost/test/sites/all/modules/subsites/subsites.module on line 148
This is a fresh install, with Context 3.0.
From what I understand, context_set_by_condition() has been removed for Context 3.0.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | context-2-3-support-935164-1.patch | 590 bytes | joneldesouza |
| #1 | context-2-3-support-935164-1.patch | 589 bytes | tobby |
Comments
Comment #1
tobby commentedI have created a patch that will support Context 2 and 3, depending on what you have installed on your site. This seems to be working fine for me -- I'm seeing my context set when I create a new node (as evident by a different theme).
Comment #2
jschrab commentedThis is a step in the right direction. But there are still some problems with Subsites and Context v3 interaction. Context v3 does not list "Subsite" as a "Condition" option as v2 use to. Pre-existing v2 contexts that used Subsites do not appear after upgrading to Context v3 and this causes me loads of problems for one site.
I've drilled down through the code and I have to wonder if the "hook" to register Subsites within Context v3 is working properly but I don't quite understand it clear enough to be certain.
Is this something I should share for the Context project or does this sound like a problem strictly contained within Subsites?
Comment #3
joneldesouza commentedHello,
Stowage with this problem, I used the patch that tobby published. Except that she is a key "}" to close more.
Attached the same patch but without this switch. Well that worked just fine!
Thanks