Wrong date format in profile plugin
From Joomla! Documentation
(Difference between revisions)
(Created page with "If you see % (ampersand) in your date field, which is part of the profile plugin, you can fix it easily with editing the file ''plugins/user/profile/profile.php''. The line curre...") |
m (→See also: heading reduction as for FAQ inclusion DPL test) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | If you see % (ampersand) in your date field, which is part of the profile plugin, you can fix it easily with editing the file ''plugins/user/profile/profile.php''. | + | If you see % (ampersand) in your date field, which is part of the profile plugin (date of birth field), you can fix it easily with editing the file ''plugins/user/profile/profile.php''. |
| + | |||
| + | Line #227 currently (Joomla! 2.5.1) is: | ||
<pre> | <pre> | ||
$data['profile']['dob'] = $date->format('%Y-%m-%d'); | $data['profile']['dob'] = $date->format('%Y-%m-%d'); | ||
| Line 8: | Line 10: | ||
</pre> | </pre> | ||
| − | == See also == | + | === See also === |
* [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27918 issue in the tracker] (bug tracker #27918) | * [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27918 issue in the tracker] (bug tracker #27918) | ||
| − | [[Category:Version 2.5 FAQ]] | + | <noinclude>[[Category:Version 2.5 FAQ]] |
[[Category:Version 2.5.1 FAQ]] | [[Category:Version 2.5.1 FAQ]] | ||
| + | [[Category:Version 2.5.2 FAQ]] | ||
| + | [[Category:Version 2.5.3 FAQ]]</noinclude> | ||
Latest revision as of 23:21, 1 September 2012
If you see % (ampersand) in your date field, which is part of the profile plugin (date of birth field), you can fix it easily with editing the file plugins/user/profile/profile.php.
Line #227 currently (Joomla! 2.5.1) is:
$data['profile']['dob'] = $date->format('%Y-%m-%d');
and should be changed to:
$data['profile']['dob'] = $date->format('Y-m-d');
[edit] See also
- issue in the tracker (bug tracker #27918)
