package name prefix not using correct date

  • Resolved Sabina

    (@pessimisticoptimist)


    7 years, 10 months ago

    Hello!

    I just noticed recently that the archive package names no longer properly generate the date that the package was created as the prefix for me. It seems to be stuck using an old date for every new package, which is going to make keeping track of versions tricky.

    I’ve got screenshots from 2 sites as an example of what’s going on:
    https://gradycreative.com/development/duplicator-fwa.jpg
    https://gradycreative.com/development/duplicator-yra.jpg
    FYI, the screenshot jpegs are on same site, but the package lists in the screenshots are from 2 different sites with different domains on different web hosts.

    At first I thought it might be due to the size of the package as one of the screenshots shows the date lock up just after it goes over 100MB, but I just did a test on a 23MB site and got the same result of duplicate prefix.

    Is there something I’m doing wrong? Some setting I’m missing somewhere? Any help is much appreciated.

    Thanks,
    Sabina

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hey @pessimisticoptimist,

    When you create a package you have the option to give it whatever name you want. By default it will use the last value you set. By the Name is a blue arrow that you can click and it will generate a new date-name prefix. Some users don’t even want a date in the name so the value should be update with each build if you want.

    Hope that helps~

    Thread Starter Sabina

    (@pessimisticoptimist)

    Ohhhh, duh, I had no idea! That blue arrow didn’t used to be a thing, it used to auto-generate, didn’t it? Or maybe I’m just losing my mind. ??

    Thanks so much!

    You are correct! At one point it did, however we had several users who didn’t like that format and wanted it to remember the last item saved without the date, so we basically just put in the last option you saved as the value and then added the refresh item to account for users who wanted a dynamic date…

    Cheers~

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘package name prefix not using correct date’ is closed to new replies.