# Mautic 3.0.0. datefields don't have a popup calendar anymore

**URL:** <https://forum.mautic.org/t/mautic-3-0-0-datefields-dont-have-a-popup-calendar-anymore/14910>\
**Category:** Mautic 3 - Install/Upgrade Support\
**Created:** [June 22, 2020, 7:20pm UTC](https://forum.mautic.org/t/mautic-3-0-0-datefields-dont-have-a-popup-calendar-anymore/14910 "2020-06-22T19:20:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![maurice](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/maurice/32/406_2.png) [@maurice](https://forum.mautic.org/u/maurice)\
**Post date:** [June 22, 2020, 7:20pm UTC](https://forum.mautic.org/t/mautic-3-0-0-datefields-dont-have-a-popup-calendar-anymore/14910/1 "2020-06-22T19:20:27Z")

</div>

**Your software**  
_My PHP version is_ : 7.3

**Your problem**  
_My problem is_ : when editing a contacts custom datefield value, I do not get a date popup anymore. It acts as a text field.

So I need to enter a date manually as a string and I’m not sure if the format is correct.

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [June 26, 2020, 7:59pm UTC](https://forum.mautic.org/t/mautic-3-0-0-datefields-dont-have-a-popup-calendar-anymore/14910/2 "2020-06-26T19:59:10Z")

</div>

Confirmed - looking into it now. Thanks for raising it!

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [June 26, 2020, 8:05pm UTC](https://forum.mautic.org/t/mautic-3-0-0-datefields-dont-have-a-popup-calendar-anymore/14910/3 "2020-06-26T20:05:11Z")

</div>

> <https://github.com/mautic/mautic/issues/8958>
>
> Bug Description
> Flagged in the forums here and I think I came across it in #8835 without realising!
> when editing a contacts custom...

Issue raised - I had run across it in beta testing but thought it was a different problem (that the field did not tell me the data was invalid)!