I'm new to umbraco - so i'm sorry if i sound a little inexperienced here - any help is very gratefully received.
i am looking to extend umbraco 4 with a new job section that will allow you to add jobs to a page, or search jobs by category/date etc.
The jobs are in a specific tables that i will be adding to the umbraco database (three tables; job, jobcategory, dobcategoryassociation). I was wondering if you could advise/help me on the best way to add these to the umbraco so that they can be added to a page, or searched on and displayed in a list. I'd like to have it so that 1 page is associated with a job so that the URL re-writing still works nicely.
I know you can add custom data types, but i want to keep the job tables seperate from the umbraco tables, as the client wants to be able to get access to the tables externally.
I'm more a fan of using umbraco tables here. I'd still use the building blocks of umbraco to create a job document type. Categories and associations can be handled in different situations, that depends a bit on how you're structuring that info. Only a single category per job, and such questions...
If the client wants access to the tables, just write up some webservices which exposes the data to the client. I'd advice against direct access to your database.
custom job section
Hello :)
I'm new to umbraco - so i'm sorry if i sound a little inexperienced here - any help is very gratefully received.
i am looking to extend umbraco 4 with a new job section that will allow you to add jobs to a page, or search jobs by category/date etc.
The jobs are in a specific tables that i will be adding to the umbraco database (three tables; job, jobcategory, dobcategoryassociation). I was wondering if you could advise/help me on the best way to add these to the umbraco so that they can be added to a page, or searched on and displayed in a list. I'd like to have it so that 1 page is associated with a job so that the URL re-writing still works nicely.
I know you can add custom data types, but i want to keep the job tables seperate from the umbraco tables, as the client wants to be able to get access to the tables externally.
Does this make sense?:-s
thanks.HP.
Hi,
I'm more a fan of using umbraco tables here. I'd still use the building blocks of umbraco to create a job document type. Categories and associations can be handled in different situations, that depends a bit on how you're structuring that info. Only a single category per job, and such questions...
If the client wants access to the tables, just write up some webservices which exposes the data to the client. I'd advice against direct access to your database.
Does that make sense?
Regards,
/Dirk
Hey there,
If you want to do that just in case then you can look at this:
http://www.simm.dk/umbraco-corner/articles/making-custom-sections-and-trees-inside-umbraco---part-i.aspx
http://www.simm.dk/umbraco-corner/articles/making-custom-sections-and-trees-inside-umbraco---part-ii.aspx
He does a pretty neat job.
However, I agree with Dirk use the umbraco core to the extent that you can and if it is not flexible enough for you then do the other thing.
Thanks
is working on a reply...