[#11442] - Can not upgrade to J3.6.1 if "Backup on Update" plugin is active
- Closed
- 4 Aug 2016
- Medium
- Build: master
- # 11442
Steps to reproduce the issue
Just as instruction says,
- I upgrade the Upgrade component;
- try to upgrade Joomla.
Expected result
Seeing silly clowns around.
Actual result
I get the error message "The last request was denied because it contained faulty security token . Please refresh the page and try again." (Try again what?)
The Database says it's OK, but Joomla reports still being 3.6.0
System information (as much as possible)
Akeeba "Backup on Update" plugin is active.
PHP 5.6
Additional comments
Disabling Akeeba "Backup on Update" plugin helps.
Votes
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-08-04 12:37:51 |
| Closed_By | ⇒ | brianteeman |
@brianteeman, yes, it is this instruction that I followed.
It causes the bug.
Why did you close it?
Akeeba "Backup on Update" is not part of the core of joomla.
Akeeba "Backup on Update" is the de facto standard of the joomla backuping, unless there is a similar functionality in Joomla core.
So it's incorrect to not update instruction that causes bugs just because you consider it "not core" bugs.
The link is a wiki where you can submit edits yourself
I know, thanks.
So your function here is closing bugs without correcting them, and letting others to correct them themselves?
Then maybe you shouldn't close them until others correct them.
Don't you think?
It's correct procedure. The Joomla project cannot be responsible for
debugging and resolving issues in third party code, even if it is "de facto
standard". This tracker is ONLY for issues related to the core CMS that
you download from joomla.org, nothing more.
On Thursday, August 4, 2016, Chang Zhao notifications@github.com wrote:
Them maybe you shouldn't close them until others correct them.
Don't you think?—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#11442 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWfoVfCSS_VFY2hobz2HvokaDW9jlGuks5qcfdAgaJpZM4JcpdL
.
no - this is the issue tracker for the joomla core. not for anything else
On 4 August 2016 at 15:29, Chang Zhao notifications@github.com wrote:
Them maybe you shouldn't close them until others correct them.
Don't you think?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11442 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8d56K7cTzOQi7iIzW9RNotBKy3xEks5qcfdCgaJpZM4JcpdL
.
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
@brianteeman
@mbabker
Closing bugs without correcting them and without explanation why did you close them is not a correct procedure.
Please review your practices, guys.
@brianteeman Thank you!
Good luck in all the useful actions!
https://docs.joomla.org/J3.x:Update_fails_with_an_error_message