Skip to main content

Timeline for Re: Relation Module

Current License: CC BY-SA 3.0

4 events
when toggle format what by license comment
Oct 3, 2012 at 19:08 vote accept Paul B
Aug 15, 2012 at 20:58 comment added Paul B ..maintaining or 'taking over' might not be worth it and probably better I find a way and share it my results here with others for future use. It's possible that some of the Recruit module was for me 'too heavy' and I merely need to incorporate an "Apply Now" on each job node and then have that linked via Relation to the content posters (and applications) dashboard. I know others have done some great work with the "Recruiter"/Drop_jobs but IMO they lack certain aspects which I'd like to build upon from a commercial/ organisational aspect. I'll keep people posted on how I overcome my issues.
Aug 15, 2012 at 20:55 comment added Paul B Again Thank you for your reply and in response, refer to my boombatower reply above. Further to yours, I'm glad of the confirmation to my initial thoughts re; the old recruit module. I agree with you that duplicating effort is not what I want, but as said above whilst I've been an IT user for 25 years, I'm not currently too confident to 'hack' a module until my programming ability has increased over then next few weeks. I'm glad to read that 'provides integration with Relation already' so at least I'm on the right track. cont..
Aug 15, 2012 at 20:14 history answered Letharion CC BY-SA 3.0