Ability to change the publish / created date in a CMS item manually

Ability to change the publish / created date in a CMS item manually  - would be useful when migrating posts and content from old sites.

  • Diarmuid Sexton
  • Feb 8 2018
  • David commented
    27 Jul 03:14pm

    Just posted a request for pre-populated date fields which would be a nice-ish solution to this – https://wishlist.webflow.com/ideas/WEBFLOW-I-3160

  • David commented
    27 Jul 03:02pm

    This is a real big one, as someone else said – this falls apart when importing a bunch of old entries. Manually having to add the date on every post is... not nice. I'm guessing this is a technical limitation somehow, but being able to manually select the published date would also negate the need to have the schedule feature.

    At the very least we need a feature to pre-fill a date field with todays date.

  • Matt Schweitz commented
    8 Jun 08:40am

    Not sure why the benefits of this feature are such a mystery. When I import posts into Webflow, sure I can manually set the dates for a new custom field (ie, "Original Publish Date"), but THEN for all new future posts, my authors have to manually set this field as well. This shouldn't be required in any modern CMS system. Please fix.

  • Kylee James commented
    8 Jun 07:29am

    error code 43 disney plus can occur due to many reasons, few of the factors can be its settings, network connectivity or at times it can be an overloaded server. It has gained tremendous popularity in a short time still there are some issues people encounter like.

  • Michael Auer commented
    5 May 01:35pm

    This ist SUPER important, and a BASIC Feature of a CMS… i Never saw a cms who doesn't support edit publish date until webflow. why?

  • Tye Newton commented
    16 Mar 05:15am

    This is important! Great points have already been in this thread as to why a custom Date field is not a sufficient workaround, incuding that it causes a ton of extra ongoing work, when the ability to edit the Publish Date would only take some work one time. We also shouldn't have to take up one of a limited number of CMS fields just to correct an issue caused by importing CMS items in a way that doesn't honor the original Publish Date.

  • Yasmina Lembachar commented
    4 Dec, 2019 11:45am

    Yes! This post also provides more feedback as to why a custom date field wouldn't be practical: https://forum.webflow.com/t/editing-publish-date-for-imported-cms-items/100385 (namely: the need to then manually update the field for every new post added to the collection)

  • Keira Buckley commented
    7 Oct, 2019 04:48am

    An enormous advantage to a CMS like Joomla is the network of prepared designers it has taking a shot at augmentations and security fixes for it.

    uk accident claim
  • Ashwin Kumar commented
    11 Jul, 2019 10:23am

    You know the control panel is a section of Microsoft Windows that enables a user to change various computer hardware and software features restore control panel in windows 10 follow this online tutorial to learn more usages.

  • Gustav Kjellin commented
    17 May, 2019 10:24am

    I think I can provide a fairly valid use case, unless I'm missing something obvious:

    I'm building a site for a company that has an existing database of Press Releases. Each new Press Release after the new site will automatically get a "Created Date" when Zapier fetches it from an existing RSS-feed. This "Created Date" can then be used to sort and filter Press Releases.


    However, the existing database of Press Releases will all have the same "Created Date". Being able to change them to the original publish date would fix this.

  • Diarmuid Sexton commented
    9 Feb, 2018 05:56pm

    Yes, a custom date field will work in all those cases. You're right - it's not really necessary!

  • Anna Kelian commented
    9 Feb, 2018 11:06am

    These dates are metadata created with your posts to let you know when the post was created/imported, published, modified in Webflow.

    Wouldn't creating new Date fields and binding those imported dates to the new/custom fields work for you?

    Can you provide an example of a use case where you believe you need to change the metadata and using a custom Date field would not work?

  • and 33 more