A goal of CSV 2 POST is to help users protect their live blog. What I mean by this is that we want to reduce risk when making changes to a project that has already created hundreds of posts. Our Test Posts meta box feature allows us to enter one or more post ID when editing a Content Template. On clicking “Update” our template changes are applied to those test post. Other update procedures make changes to the whole post, essentially re-building it. This feature focuses on the “post_content” value stored in the database and that is the value users see. We can then inspect them and decide if we want to allow the plugin to apply the changes to all posts. As always you should read this feature guide to fully understand how this operates.
Original Premium Feature: No other CSV importer on WordPress provides this functionality and so it is provided in our premium plugin only. Our aim is to provide surgical tools to help manage live blogs without taking them offline and we will continue to show innovation in this area.
The Test Posts tool is provided to help during the process of editing and updating existing posts. So the first step is to create posts using CSV 2 POST.
Open C2P Content in the menu and click Edit on the template you wish to change then apply to posts using that template.
Enter one or more post ID separated by comma. The posts must be using the template you plan to edit. They may have used the template originally or you have changed to that template. Either way CSV 2 POST will still only apply the template linked to the posts through the standard project settings or the custom field named “csv2post_template”. The Test Posts tool simply tells CSV 2 POST which posts we want updated right now, despite any other settings.
Ensure your posts are private or draft, unless you are working on a test blog then it does not matter. The idea is to hide changes. Confident users may enter post ID for public posts, that is fine. We’re still reducing any potential damage if our template changes are not correct or turn out different from what we expected.
Click Update and check your posts. Continue the process if required.
Custom Field: the string of post ID will be stored in a custom field named _csv2post_testposts. The underscore at the beginning of this custom field key hides it on the interface though.