Thanks for coding this, rhertogh!

While we’re transitioning to a new integrated tracker, could you report the issue on our current main tracker at JoomlaCode and cross-reference each with a link to the other? Here’s the process for reporting on the other tracker:
http://docs.joomla.org/Filing_bugs_and_issues

Alternatively, let me know if you’d like me to create it for you and I can go ahead and do that.

Thanks in advance and thanks again for coding this, rhertogh!

Hi Nick,

You're welcome
I created the issue on the Joomla issue tracker, please see: Report on
Joomla Issue tracker:
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=30775

On Tue, Apr 30, 2013 at 6:48 AM, Nick Savov notifications@github.comwrote:

Thanks for coding this, rhertogh!

While we’re transitioning to a new integrated tracker, could you report
the issue on our current main tracker at JoomlaCode and cross-reference
each with a link to the other? Here’s the process for reporting on the
other tracker:
http://docs.joomla.org/Filing_bugs_and_issues

Alternatively, let me know if you’d like me to create it for you and I can
go ahead and do that.

Thanks in advance and thanks again for coding this, rhertogh!

—
Reply to this email directly or view it on GitHub#1075 (comment)
.

Thank you, Rutger! :)

The error must have come from another error the first time during the update, the original code is OK, please see also Elin Waring comment at:
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_id=8103&tracker_item_id=30775

Great! Glad you got things sorted, Rutger!

By the way, we're looking for more JBS members if you'd like to join :)
http://docs.joomla.org/Bug_Squad