Closed (fixed)
Project:
Default Content (Deprecated)
Version:
7.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Mar 2011 at 20:13 UTC
Updated:
10 May 2011 at 01:21 UTC
Thanks for the useful module.
It wasn't working with the Features UI - but the attached code change made the difference.
| Comment | File | Size | Author |
|---|---|---|---|
| defaultcontent-fix-feature-integration.patch | 458 bytes | jamsilver |
Comments
Comment #1
infojunkieWorked for me. Thanks!
Comment #2
e2thex commentedThanks for the patch it is commited
commit 5461f3c54726850390a2a54b95118430ffb235be
Date: Tue Mar 22 09:23:46 2011 -0400
Issue #1091300 by jamsilver: Small bug prevented Features UI working on export
Comment #4
aschiwi commentedHow about a new release? There was no new release made after this commit and unless people find this issue they won't be able to get the module to work.
I have to say I still haven't found out how it works. Using this patch I get a file called myfeature.features.content.inc which contains the node content, but the content does not get created when I turn on the Feature. I tried and copied the openpublic_demo_content Feature from OpenPublic but still no content when I activate that. Is there anything else I need to do that I missed?
Comment #5
emorency commentedI have the same problem. The features seems to export content correctly but no content is created when I activate the Feature...
I'm using the dev version.
Thank you !