Please help me autogenerate content directly into c5 backend (initial creation and regular updates)
Permalink
I am planning to initially create 250 pages of content, and then have the ability to update it once every week automatically
I have created a list of SQL for inserting into the concrete5 system, which is at yet untested it took me a long time to follow it through using mysql diff tool, (and I am sure it will take even longer to actually get it working). I much prefer using the concrete5 models.
Can anyone tell me the model methods I should call in order to correctly add new content which is indexable in c5? And also how to update content?
I have not been able to find a recipe for doing this and I am very new to C5 (2 days).
I was helpfully advised by
Jordan Lev yesterday that if I wanted to update a content block that's on a page, I need to create a new collection version (which I believe implicitly carries all existing blocks forward), then copy the block in question block (I think there's a "copy" or "clone" method in the block model for this purpose), then update that block's content, then un-assign the old block from the new collection version, then assign the new block to the new collection version, then approve/publish the new collection version.
THIS IS starting to make sense, but I look forward to help in formulating a precise checklist of the the actions necessary to add content and periodically update content.
Many thanks in advance.
I have created a list of SQL for inserting into the concrete5 system, which is at yet untested it took me a long time to follow it through using mysql diff tool, (and I am sure it will take even longer to actually get it working). I much prefer using the concrete5 models.
Can anyone tell me the model methods I should call in order to correctly add new content which is indexable in c5? And also how to update content?
I have not been able to find a recipe for doing this and I am very new to C5 (2 days).
I was helpfully advised by
Jordan Lev yesterday that if I wanted to update a content block that's on a page, I need to create a new collection version (which I believe implicitly carries all existing blocks forward), then copy the block in question block (I think there's a "copy" or "clone" method in the block model for this purpose), then update that block's content, then un-assign the old block from the new collection version, then assign the new block to the new collection version, then approve/publish the new collection version.
THIS IS starting to make sense, but I look forward to help in formulating a precise checklist of the the actions necessary to add content and periodically update content.
Many thanks in advance.
