This is expected behavior since 3.5.0 please update via com_joomlaupdate or upload and install in com_joomlaupdate

You cannot upload patches with the extensions manager anymore - this is by design - and that has been widely announced

Closed as this is expected behaviour as stated above

Does it make sense to offer patches for installation which don't work?

The patches provided DO WORK when they are USED AS INTENDED - what you are doing is refusing to accept that things have changed, and refusing to learn the new way to use the patches.

They are not "patches for installation with the Joomla extension manager"

They are patches for "uploading to the NEW AND IMPROVED com_joomlaupdate"

The process has recently changed. I cannot find a link to the documentation at the moment, but it was widely announced.

see:

This is as good a link as any https://www.joomla.org/download.html

Updating Joomla to version 3.5.0 and higher cannot be done by the extension manager.
You have to update via the Joomla! Update component or via the steps explained in our documentation:

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11469.}

The process has recently changed. I cannot find a link to the documentation at the moment, but it was widely announced.

For those who missed or forgot that announcement, a second line below 'Upload & Install Joomla Extension' in the Extension manager 'Upload Package File' tab saying something like "For Joomla updates use 'Components' > 'Joomla! Update' instead" might keep users from old habits.
:-)

As it is in a massive box on the page you downloaded the update from and
you still missed it i doubt very much you would have seen it on that page
either. Plus we obviously can not add that message on to an existing site
so it wouldnt have helped you if we added it now.

On 5 August 2016 at 12:56, Gitjk notifications@github.com wrote:

The process has recently changed. I cannot find a link to the
documentation at the moment, but it was widely announced.

For those who missed or forgot that announcement, a second line below
'Upload & Install Joomla Extension' in the Extension manager 'Upload
Package File' tab saying something like "For Joomla updates use
'Components' > 'Joomla! Update' instead" might keep users from old habits.

:-)

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/11469
https://issues.joomla.org/tracker/joomla-cms/11469.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#11469 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8YeJk5eYThzYEh52uKubqA6nCV_gks5qcyTtgaJpZM4Jdh1z
.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

As it is in a massive box on the page you downloaded the update from and you still missed it...

I missed it because I downloaded the update patch directly from https://github.com/joomla/joomla-cms/releases
:-)

Ok. There was a note on the 3.6.0 release on that page. I will add it to
the 3.6.2 release

There was also a check added specifically for Joomla packages to the extension manager as of 3.6.0. If that didn't trigger, then the patch package is missing an important file.

@mbabker wont that check only be triggered if you are updating from a
version with that check? It wont help someone on 3.3

@gitjk I have added the notice on the github release page

On 5 August 2016 at 13:46, Michael Babker notifications@github.com wrote:

There was also a check added
a5443c2
specifically for Joomla packages to the extension manager as of 3.6.0. If
that didn't trigger, then the patch package is missing an important file.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#11469 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8UnOg-FQeXzHPoF7HDTSNBCwjZG4ks5qczCkgaJpZM4Jdh1z
.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

It wont help someone on 3.3

Right, but given the file name referenced here, I made the (potentially incorrect) assumption that the user was updating 3.6.1 to 3.6.2.

I made the (potentially incorrect) assumption that the user was updating 3.6.1 to 3.6.2.

Your assumption was correct. :-)