Is there any work around for that instead of deleting all posts and generate it again?
This is already on the to do list and I’m hoping to at least get updating done in response to template changes. But there are other update triggers required which I don’t think any other plugin has so I’m keen to add them in the next few months.
- Update when template changed
- Update all posts when a new custom field added to a project. Considered the ability to delete a custom field/meta value for all posts on deletion also.
- Update when tag settings changed. Basically re-build all posts tags.
- Updating category descriptions when they are covered after being created.
- If user configures featured image after posts created it will add the featured image to all posts
There will be a switch to trigger any updating but the complex part is not updating an entire post when only a specific element of a post requires changing. Anyone with say 100,000 posts does not really want to run update queries on the wp_posts table if it is a new custom field being added.
So I need to create separate update processes and functions. All of which will be worked into the schedule system so that updating can be systematic as posts are opened.
Looking forward to reaching this state of the plugin and anyone who wants these abilities should comment below. The higher the demand for features the higher they are placed on my massive to do list 🙂
I do mean massive, hundreds of items lol
Thanks again Kai
Ryan
Oh as for a workaround.
Doing a query on your imported data, changing a part of it to force an update on all posts is one way. Could change a date value or none used data with a simple PHP function. Then even reverse the change later if required.
What this comes down to is a button on the plugins interface to force updating even if records have not changed. That is simple enough for me to do so I will keep it in mind over the next couple of weeks. It’s just not the best way to do it for most users. Also need to make sure post revisions are off and I think I can provide a setting for that or at least indicate to users how to disable them by editing a file in WordPress.
Hello Ryan,
just tested your workaround. I changed one field of one record in the db.
Put all update flags in csv2post backend to “on” – but nothing happened.
After that I trigger a “manual update” of the post by it´s id (2337)
Now some strange behaviour:
This post (id 2337) was updated to a new data-set from the db – I check it out – it was the next unused dataset.
The old dataset (with my change) was not used. So now the old dataset has no more correspondening post on my blog 🙁
in the csv2post table the old dataset is still referenced to post 2337, but the content of 2337 is completely false.
Now i generated 5 new posts:
The first new post has the same content as my updated post 2337.
Argl….
Maybe you can fix this 🙂
Best regards,
Kai
