Closed (duplicate)
Project:
Drop Jobs
Version:
7.x-1.x-dev
Component:
Demo Feature
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
8 May 2012 at 09:39 UTC
Updated:
20 Jan 2013 at 06:57 UTC
Jump to comment: Most recent
Comments
Comment #1
alexweber commentedThe alpha version is a work in progress! Work is being made in all sub-modules, I'll reply here again when this is ready for testing!
Thanks for the feedback!
Comment #2
alexweber commentedComment #3
Anonymous (not verified) commentedUsing MAMP/Localhost. It would not install with the demo radio button ticked. When I did install I got the White Screen of Death.
Comment #4
alexweber commentedStrange, I use MAMP too and it works fine.
What PHP version are you using?
Would you mind running this again with error_reporting on to see what the error causing the WSOD was?
Comment #5
Anonymous (not verified) commentedHi Alex, sure thing. Not sure how to do the error_reporting but will search for it on drupal.org.
I think you may be able to build a highly desirable product to many Drupal aware recruiters. Have you though of hosting a webinar to brainstorm development directions. I would like to participate. As an end user it would be great to input into the projects direction.
Thanks
Comment #6
alexweber commented@CD, in your php.ini set "error_reporting" to "E_ALL & ~E_STRICT" and also set "display_errors" to "On"
Regarding the webinar, I think it's a great idea! For now I've basically abstracted work done for a client of ours at Webdrop and ported it to Drupal 7 using Entities and new best practices and cool modules.
The idea, in the long run, is to create an 80%-use case robust base and make it extensible by leveraging Apps in order to fulfill more specific needs.
To be honest I don't think there's enough momentum at the moment to do a webinar but I'd love to hear your thoughts, feel free to reach out via my contact form! :)
Comment #7
alexweber commentedOnce we stabilize entity types and fields we should be able to start creating demo content.
Comment #8
alexweber commentedOnce we stabilize entity types and fields we should be able to start creating demo content.
Comment #9
kaizerking commentedfor your info There is problem with features which i have noticed, in other instances
If you create a feature and include data, then the terms or the conetent is not properly imported,
for ex:if you have a term reference field data in that field then data will be stored in in deferrence field in the database, I Advice against it using the data in Feature .instead you can use devel to create data for experimenattion seperately
Comment #10
alexweber commented@kaizerking thanks, I've noticed this too. I will find another way to create the demo content. :)
Comment #11
alexweber commentedPostponing this until we have a stable beta release. No point creating demo content now when the data structure can still change.
Comment #12
kaizerking commentedyou can use default content module for demo content
Comment #13
alexweber commentedThe defaultcontent module is terrible. Not only does it not work consistently but it doesn't preserve relationships between different kinds of related entities. This is being done with the Migrate module here: #1893376: Implement migrations for demo content