View Issue Details

IDProjectCategoryView StatusLast Update
0022726mantisbtbugtrackerpublic2017-04-23 10:55
Reportervstokesjr Assigned Toatrol  
PrioritynormalSeverityblockReproducibilityalways
Status closedResolutionduplicate 
PlatformLinuxOSUbuntuOS Version14.04
Product Version2.3.0 
Summary0022726: APPLICATION ERROR 0001303; Custom date field
Description

We upgraded from 1.3 to 2.3 and we are now getting the following error for our custom date field:

APPLICATION ERROR 0001303
Invalid value for field "Target Date".
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.

However, the custom date field is NOT required. See screen shot.

Steps To Reproduce

Create custom date field, do not make it mandatory for new bug.

Additional Information

I think this was a previous bug in 1.x branch and it was fixed. This custom field worked correctly in our stock version of 1.3. Appears this may be a regression. I tracked down the code and it appears to me that it could be fixed in "gpc_api.php" in function "gpc_get_custom_field()":

switch ( $p_custom_field_type )
{
....

    case CUSTOM_FIELD_TYPE_DATE:
        $t_date = gpc_get_string( $p_var_name . '_date', $p_default );
        if ( !$t_date )
        {
            return $p_default;
        }

        return strtotime( $t_date );

....
}

TagsNo tags attached.
Attached Files

Relationships

duplicate of 0022663 closedsyncguru APPLICATION ERROR 1303 Non-mandatory date custom fields blocking issue creation 

Activities

vstokesjr

vstokesjr

2017-04-13 08:10

reporter   ~0056525

Opps, forgot to include:

PHP 5.5.9-1ubuntu4.21 (cli) (built: Feb 9 2017 20:54:58)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies

atrol

atrol

2017-04-13 08:23

developer   ~0056526

@vstokesjr I recommend to use version 2.2.3 until there will be a fix in 2.3.1.