Identify start date and end date

This support ticket is created 6 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Import and export, Setting up custom fields, Types plugin

This topic contains 1 reply, has 2 voices.

Last updated by Christian Cox 6 years ago.

Assisted by: Christian Cox.

Author

Posts

December 28, 2018 at 4:51 pm #1174293

jannisM

Snap 2018-12-28 at 17.49.57, 316x251.png

I migrated a Drupal site to WordPress and some of the imported custom post types originally had a date field that can either have a simple date or a start date and an end date. What I have now in my import is a date filed that has two entries. Is there a way to ignore the second date if it is identical with the first and/or define the first date as a start date and the second as an end date?

Thanks in advance,

Jannis

December 30, 2018 at 4:55 pm #1174836

Christian Cox

Is there a way to ignore the second date if it is identical with the first and/or define the first date as a start date and the second as an end date?
Hi, unfortunately there's nothing built in to Toolset that will help split repeating field values into other single field values. Are you using a CSV file to import your content? If so, then you can create two new custom date fields in Types - one for start date and another for end date. Then edit the CSV file manually before import. Copy all the old date values to use as the new start date field values. Then find any new start date fields with multiple date values. Cut the second date value and paste it in the new end date field value. During your import process, do not map the old date field to anything in Toolset. Instead, map the new start and end date fields. It's a tedious process, but it could be accomplished without any custom code.

Or if you're comfortable writing code, a custom SQL database script could loop over all the posts that have this date field, and transpose the existing field values into the new start and end date fields. I can show you how to access any custom field in the database, but the SQL code itself is outside the scope of support we provide here.