Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Handling of extrafield type "date" not correct #10278

Closed
glu000 opened this issue Dec 29, 2018 · 0 comments
Closed

BUG: Handling of extrafield type "date" not correct #10278

glu000 opened this issue Dec 29, 2018 · 0 comments

Comments

@glu000
Copy link
Contributor

glu000 commented Dec 29, 2018

Instructions

This is a template to help you report good issues. You may use Github Markdown syntax to format your issue report.
Please:

  • only keep the "Bug" or "Feature Request" section
  • replace the bracket enclosed texts with meaningful informations
  • remove any unused sub-section

Bug

handling of extrafield date is not correct in function insertExtraFields.

Environment

  • Version: 9.0
  • OS: n/a
  • Web server: n/a
  • PHP: n/a
  • Database: n/a
  • URL(s): n/a

Expected and actual behavior

Wrong data is stored, when a date is entered in any form into an extrafield-type "date"

Steps to reproduce the behavior

  1. Create an extrafield with type "date" (e.g. in proposal)
  2. Enter a date in a new proposal into this extrafield -> wrong data is stored

Suggested implementation

File: core/class/commonobject.class.php
Function: insertExtraFields, line 5027
-> handle extrafield date in the same way than extrafield datetime

if (! is_int($this->array_options[$key])) {
	$this->array_options[$key] = strtotime($this->array_options[$key]);
}
@glu000 glu000 mentioned this issue Jan 21, 2019
eldy added a commit that referenced this issue Feb 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant