go to: https://issues.joomla.org/tracker/joomla-cms/11879
edit the issue
save the issue
the bot does what we tell him
This is the place it throws the error so anyhow the issue number did not get passed to that method.
https://github.com/joomla/jissues/blob/master/src/App/Tracker/Controller/Issue/Save.php#L57
And it looks like there is a special issue with that on as i can edit other issue fine.
0 UnexpectedValueException
No issue number received.
exception: exception 'UnexpectedValueException' with message 'No issue number received.' in ROOT/src/App/Tracker/Controller/Issue/Save.php:57
Stack trace:
#0 ROOT/src/JTracker/Application.php(174): App\Tracker\Controller\Issue\Save->execute()
#1 ROOT/vendor/joomla/application/src/AbstractWebApplication.php(134): JTracker\Application->doExecute()
#2 ROOT/www/index.php(104): Joomla\Application\AbstractWebApplication->execute()
#3 {main}
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-09-02 08:52:31 |
Closed_By | ⇒ | zero-24 |
Status | Closed | ⇒ | Confirmed |
Closed_Date | 2016-09-02 08:52:30 | ⇒ | |
Closed_By | zero-24 | ⇒ |
Set to "open" on behalf of @brianteeman by The JTracker Application at issues.joomla.org/jtracker/874
Re-opened as the same is happening with 11899
Re-opened as the same is happening with 11899
Wouldn't it be better to call this a duplicate? Currently we have three issues for:
No issue number received.
As long at it gets fixed ;)
On 5 September 2016 at 13:40, Nikolai Plath notifications@github.com
wrote:
Re-opened as the same is happening with 11899
Wouldn't it be better to call this a duplicate? Currently we have three
issues for:
UnexpectedValueException No issue number received.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#874 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABPH8XwYaluKNYKxg7o0ptYOKV-AwWDTks5qnA3NgaJpZM4JzcAn
.
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
I'll see if Rochen can dig anything up because it's most assuredly not our
code that's messing this up.
On Monday, September 5, 2016, Nikolai Plath notifications@github.com
wrote:
Unfortunately only @mbabker https://github.com/mbabker is able to deal
with server related issues :(—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#874 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAWfoeQc0VJ6ePzNX0iRKNZmhx6PIKOQks5qnBCPgaJpZM4JzcAn
.
Status | Confirmed | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-09-05 14:25:27 |
Closed_By | ⇒ | mbabker |
Workarround by manual edit by Brian and merge.