No Code Attached Yet bug
avatar je1977
je1977
18 Jan 2026

Steps to reproduce the issue

  • create a custom field type calendar for all categories
  • create an article
  • enter a wrong formated date like 01.01.20261 in the custom field
  • save

Expected result

i expect a joomla warning that the article can`t be saved with a wrong formated date field

Actual result

PHP Error Message
Call to a member function format() on false

System information (as much as possible)

  • Joomla! 6.0.2 Stable
  • PHP Version: 8.4.16-nmm1
  • Database: 10.6.22-MariaDB
  • Server OS: 22.04.1-Ubuntu
  • Webserver: Apache

Additional comments

Screenrecord

Image

avatar je1977 je1977 - open - 18 Jan 2026
avatar joomla-cms-bot joomla-cms-bot - change - 18 Jan 2026
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 18 Jan 2026
avatar Fedik
Fedik - comment - 18 Jan 2026

For reference. This is related to (but not the same):

avatar Fedik Fedik - change - 18 Jan 2026
Labels Added: bug
avatar Fedik Fedik - labeled - 18 Jan 2026
avatar Dev10-sys
Dev10-sys - comment - 23 Jan 2026

I can work on this issue and provide a fix.

avatar exlemor
exlemor - comment - 2 Feb 2026

I can't replicate your findings sadly, I do NOT get the:

PHP Error Message
Call to a member function format() on false

It saves and on the Frontend I see the information I put in Testing Field: 01.01.20261
It perhaps 'should' have a warning message but that might be outside of this Issue's scope.

avatar Fedik
Fedik - comment - 2 Feb 2026

Actually 01.01.20261 is not "wrong format", it is much depend from your language.

Wrong for everyone would be something like 78.35.123 or foobar 12 2006 or any random text.

avatar exlemor
exlemor - comment - 2 Feb 2026

FYI, I tried changing the 01.01.20261 to 78.35.123 and was able to save successfully... same thing with foobar 12 2006.

avatar krishnaGandhi11
krishnaGandhi11 - comment - 3 Feb 2026

FYI, I tried changing the 01.01.20261 to 78.35.123 and was able to save successfully... same thing with foobar 12 2006.

Adding to what Emmanuel says:

Recording.2026-02-03.112018.mp4

It fetches the current date.

avatar je1977
je1977 - comment - 3 Feb 2026

FYI, I tried changing the 01.01.20261 to 78.35.123 and was able to save successfully... same thing with foobar 12 2006.

Adding to what Emmanuel says:

Recording.2026-02-03.112018.mp4
It fetches the current date.

yes, but if i try to type the Date manully and makes an mistake like 20263-01-01 the error appears, okay i`m currently under 5.4.2 but in 6.0.x it`s the same

cf-bug-2.mp4
avatar krishnaGandhi11
krishnaGandhi11 - comment - 3 Feb 2026

FYI, I tried changing the 01.01.20261 to 78.35.123 and was able to save successfully... same thing with foobar 12 2006.

Adding to what Emmanuel says:
Recording.2026-02-03.112018.mp4
It fetches the current date.

yes, but if i try to type the Date manully and makes an mistake like 20263-01-01 the error appears, okay im currently under 5.4.2 but in 6.0.x its the same

cf-bug-2.mp4

Image

Thanks, issue confirmed.

Add a Comment

Login with GitHub to post a comment