Category Archives: Notifications

Plugin Notification

No category settings have been saved for your current project. You must save some category settings to make categories as the plugin does not know what columns your category data is in or the order of categories

Explanation

You have not visited and submitted forms for category settings. CSV 2 POST does not assume or detect category data.

Solution

• Go to the Your Projects page
• Click on the Categories tab
• Configure one or more of the forms and submit

Plugin Notification

Job Progress:

Explanation

This counter is the total of all CSV file rows processed, dealt with and decided made for them. If it be that they were Dropped, made Void or imported normally.

Plugin Notification

Rows Processed: #

Explanation

This is the total number of CSV file rows processed by the plugin during the last event, whatever the outcome i.e. dropped, imported and so on. When seeing this notification you will have started a data import event manually and possibly requested a specific number of records. The “Rows Processed” does not include all rows processed for the job. Only those done during the event i.e. you may only have imported 500 out of 1000 rows so the Rows Processed would be 500.

Job Progress is the total of all events.

Plugin Notification

Dropped Rows: #

Explanation

• The dropped rows counter is not indicating a fault.
• Every row dropped is done so for a reason.
• In version 6.7.1 the plugin will drop a duplicate row. This is not a row where every column value is equal to a record already in the database but simply the selected ID/Key column value matches one already in the database i.e. 2 rows in a CSV file sharing the same product ID will cause 1 row to be dropped. This is expected to change and such rows will be indicated as a duplicate with a Duplicates counter being made clearer.

Dropped rows are those that the plugin cannot import. It is possible to setup rules that cause a row to be dropped but we recommend using the void approach to do that. Void indicates that a record should not be used, but it is still imported which is important for later. If you want to update your data, you may want to keep the void status. More importantly importing a record and applying void helps to maintain full stats i.e. imported records equal CSV file rows rather than a miscount because records have been dropped.

Dropped records are not stored anywhere. The plugin detects a problem with the data and avoids doing anything further with the record other than possibly dumping it into the error log at your request.

Solution

• Ensure your CSV file profile is correct: separator, comma and number of fields/columns
• Open your file in Microsoft Excel and determine if it looks alright. Ensure there are not columns of data without a header/title at the end of all your columns as this is common in an incorrectly formatted CSV file.
• Check the plugins error logs and see if there are MySQL failures
• If the plugin drops rows and your really not sure what is going on please report it. Please send your entire CSV file if possible or just a sample. However a sample may not include the problematic records so please run a test on your sample file first.

Technical Information

• This feature exists to help ensure the plugin is doing its job and the users data is valid. We can customize it to any extent i.e. apply strict rules and speed up importing by avoiding further processing on invalid records as soon as possible within scripts.
• This notification can be found in function csv2post_form_importdata()

Plugin Notification

Void Records: #

Explanation

It is important not to confuse void with dropped. We named records dropped when the plugin (using php and mysql) cannot import a row from the CSV file at all and so nothing is imported too the database. Void is totally different and the void status is applied too a record after a row has been imported from the CSV file. So the import is a success, but the record is still not to be used for whatever reason.

Void records are not decided by CSV 2 POST without some guidance from the user. A record will only be made void during data import when the user creates rules to cause the void status to be applied. The rules can vary and we can add more types of rules on request. It is basically the idea of checking each CSV file row for quality and confirming that each row is fit for purpose. The purpose being determined by the user and project.

If you have no idea what data rules I’m talking about. Then your void counter should always show zero. If it does not, please investigate.

Solution

• If you would like to apply void status too some of your records in an easy way. Use the Data Rules features on the Your Data page. These rules may only apply too the full edition or at least their full ability will.
• If you have records being void but do not want this to happen. Reset all forms related too data import rules on the Your Data page.

Technical Information

• This notification can be found in function csv2post_form_importdata()
• Void status is stored in the “csv2post_inuse” column as boolean, false indicates the record is not to be used. Null, empty, blank or true indicates no void status has been applied and the record can be used.