Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Jules 252 posts 543 karma points
    3 days ago
    Jules
    0

    uSync Exporter - potential issue with Date Picker

    Hi Kevin

    Umbraco: 8.18.4 uSync: 8.11.12-build.20230125.2

    Seeing some strange behaviour when importing a node that includes a date picker to one of our environments

    We have a Date Picker where the Date Format is set to DD-MM-YYYY (don't ask!).

    When importing that node to one of our environments using Exporter it seems to reverse the format to MM-DD-YYYY and therefore we end up with invalid dates.

    I only noticed this because I reimported the same package again and the 2022 node was still showing differences after uploading the package.

    No obvious differences between environments and database collation is the same in each environment.

    Any thoughts on whether this could be a uSync issue?

    If you need any more info please let me know.

    Kind regards

    Jules

  • Kevin Jump 2228 posts 14220 karma points MVP 6x c-trib
    3 days ago
    Kevin Jump
    0

    Hi,

    I will take a look - we do format the dates in the export into a "standard" format - mainly to ensure its a date we can parse at both ends.

    I think the date is then parsed and loaded as a Date object on import (so the format in the usync files shouldn't affect what happens in Umbraco) but i am not 100% sure so it will have a play around and see what i can see.

    Kevin

  • Jules 252 posts 543 karma points
    3 days ago
    Jules
    0

    Thanks Kevin

  • Jules 252 posts 543 karma points
    7 hours ago
    Jules
    0

    Hi Kevin Still experiencing this issue after recreating node from scratch in dev environment and trying import to our preprod environment again. It swaps date format around.

    Source code is same between environments. I can't think of anything that might affect date formats - sql server collation is same in the different databases. Globalization setting in web.config is the same.

    I'm totally stumped!

  • Kevin Jump 2228 posts 14220 karma points MVP 6x c-trib
    7 hours ago
    Kevin Jump
    0

    Hi,

    yes it turns out we do have a fix for this, ( https://github.com/KevinJump/uSync/commit/37a6e03145c2b3457bfc33a88ec844955aaeaf46 )

    we just haven't released it yet 😞 - but that is what i am working on today. so we should have a new v8 release out and it fixes this (i have tested it based on your format above and it seems to work).

  • Kevin Jump 2228 posts 14220 karma points MVP 6x c-trib
    7 hours ago
    Kevin Jump
    0

    Hi,

    I notied your using a nightly so if you do want to check while we do our final package version testing this is the version that going to become the release.

    https://dev.azure.com/jumoo/Public/_artifacts/feed/nightly/NuGet/uSync.ContentEdition/overview/8.11.4-build.20230320.3

    or from the package console:

    update-package uSync.ContentEdition -version 8.11.4-build.20230320.3 -FileConflictAction IgnoreAll
    

    If you can confirm that works it would be great - but no worries if now - we are likely going to release this as the final release later today/tomorrow once we've double checked everything.

    (there are only a few small changes, but we just want to run through them all - we hardly ever release v8 anymore - so just want to make sure)

  • Jules 252 posts 543 karma points
    5 hours ago
    Jules
    0

    Hi Kevin

    Unfortunately, we won't get the opportunity today to deploy to the problem environment to test.

    It's locked down at the moment pending a release.

    Sorry about that

    Jules

  • Kevin Jump 2228 posts 14220 karma points MVP 6x c-trib
    4 hours ago
    Kevin Jump
    0

    No worries

    I was able to replicate and then fix your issue by upgrading locally. so fingers crossed the full release will solve your problem when its out.

    Kevin.

Please Sign in or register to post replies

Write your reply to:

Draft