? ? Pending

User tests: Successful: Unsuccessful:

avatar zero-24
zero-24
6 Aug 2016

Pull Request for Issue #11440

Notice

Don't do that never on your Live Site please install a dev / test install!

Summary of Changes

This PR add the functionality that if a update for the update component is in place it should show the user to first update the com_joomlaupdate component.

With the new code in place we check exiplit on every call to the com_joomlaupdate default view for an update of the update component.
If there is a update we don't allow Live Update but the Upload & Install still works as before!
If we have the last update installed -> everything works as before

Testing Instructions

Ok this comes a bit complicated ? (please follow exactly the steps)

  • Install 3.6.0 https://github.com/joomla/joomla-cms/releases/3.6.0
  • ignore all messages to update etc.
  • go to the Backend -> Extensions -> Manage -> Update Sites
  • disable the update site for com_joomlaupdate (Joomla! Update Component Update Site)
  • install the patched com_joomlaupdate e.g. via install from URL (it cointains this PR and also a new update server!)
  • double check there is a new Update server for com_joomlaupdate (!)
  • go to com_joomlaupdate
  • see the mesage that you can't use the Live Update
  • follow the link (Click here to update the component.)
  • install the update (it just move the version from 3.6.1 to 3.6.2 to pass the update check)
  • install the Joomla Core Update
  • confirm all works!

Why and how

Disable the official Update Site

If we not disable that it offers us the current com_joomlaupdate package which not include my changes.

Why a own Update server

Else i can't ship my changes to test this pull requrest as Update of the original com_joomlaupdate ;)

Documentation Changes Required

The Core Update Component now inlcues a function to call for a Self Update

Additional Infos

Please give feedback:

  • On language strings
  • Do we need both the error message and the changed Live Update View? Or should we remove the error message
  • On code! It works but maybe it can be improved?! -> Feedback please!
  • On everything else you notice we can improve!

Question

What do we with users that are unable to access com_installer but are allowed to update joomla? => Handel that with a language string? Please suggest one!

Great, you have read all and this this line too your are awesome ? Thanks!

avatar joomla-cms-bot joomla-cms-bot - change - 6 Aug 2016
Category Administration Components Language & Strings
avatar zero-24 zero-24 - open - 6 Aug 2016
avatar zero-24 zero-24 - change - 6 Aug 2016
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 6 Aug 2016
Labels Added: ? ?
avatar zero-24 zero-24 - change - 6 Aug 2016
The description was changed
avatar zero-24 zero-24 - change - 6 Aug 2016
The description was changed
avatar brianteeman
brianteeman - comment - 7 Aug 2016

You are disabling live update but not upload and update - is that correct
screen shot 2016-08-07 at 06 00 19

screen shot 2016-08-07 at 06 00 46


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11493.

avatar zero-24
zero-24 - comment - 7 Aug 2016

Yes in case we broken com_installer and com_joomlaupdate with one update :)

avatar n9iels
n9iels - comment - 8 Aug 2016

Thanks for the feature! :) I think it is very useful in the future because we can change the update component without the Joomla! updates fails.

When I tested the PR I was not able to update Joomla! to 3.6.2 (I got the message "Download of update package fail"), but I believe that is a problem on my local machine. So it tested the feature successful.

About the feedback you asked, I think it is better to just remove the red error message and just use the message below the "Live update is no available".
A lot of messages can make people without experience in updating Joomla! scary and nervous. Also now I see the error First and not the link to the update.

The simple message that we have to update the Joomla! component first before we can update Joomla is enough :)

avatar zero-24
zero-24 - comment - 8 Aug 2016

Thanks @n9iels

When I tested the PR I was not able to update Joomla! to 3.6.2 (I got the message "Download of update package fail"), but I believe that is a problem on my local machine. So it tested the feature successful.

To be sure. Can you please double check that you are able to update using a not modified version of 3.6.0 -> Update for com_joomlaupdate and than 3.6.2?

I think it is better to just remove the red error message and just use the message below the "Live update is no available".
A lot of messages can make people without experience in updating Joomla! scary and nervous. Also now I see the error First and not the link to the update.
The simple message that we have to update the Joomla! component first before we can update Joomla is enough :)

Agree. Lets hear some more opinions on this. Thanks!

avatar n9iels
n9iels - comment - 8 Aug 2016

@zero-24 I'm able to update to Joomla! 3.6.2 using the modified and not modified update component now. Seems like I didn't had the php-curl library installed. So this PR works perfect ?

avatar zero-24
zero-24 - comment - 8 Aug 2016

Thanks for double checking that. ?

avatar zero-24
zero-24 - comment - 17 Aug 2016

Please explain me what you want to be added there? For this PR there is no need to extend that file.

But yes it is meant to first check that file for an update bevor it allows to update the core if that is what you mean.

avatar andrepereiradasilva
andrepereiradasilva - comment - 17 Aug 2016

Please explain me what you want to be added there? For this PR there is no need to extend that file.

You're updating com_joomlaupdate here, so my question is: after this PR gets merged a new release of com_joomlaupdate will be made right?

avatar mbabker
mbabker - comment - 17 Aug 2016

after this PR gets merged a new release of com_joomlaupdate will be made right?

Generally that only happens if there's a critical need. There isn't anything happening here that is a critical need.

avatar andrepereiradasilva
andrepereiradasilva - comment - 17 Aug 2016

Generally that only happens if there's a critical need. There isn't anything happening here that is a critical need.

isn't critical to prevent people from update from 3.6.0 to 3.6.2 without com_joomlaupdate updated?

Update: ok sorry of course, people will only have this AFTER updating com_joomlaupdate right dah :)

avatar mbabker
mbabker - comment - 17 Aug 2016

This isn't adding anything to make that update process easier. All it's doing is adding a self check to tell the component it can't update core without updating the component first, which you won't even see if you're updating the component before updating core on one of the older releases. A separate package isn't going to do anything useful here.

avatar brianteeman brianteeman - test_item - 26 Aug 2016 - Tested successfully
avatar brianteeman
brianteeman - comment - 26 Aug 2016

I have tested this item successfully on 13c8e74


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11493.

avatar zero-24
zero-24 - comment - 28 Aug 2016

I would be happy on any tests or feedback ?

avatar sonalitailored sonalitailored - test_item - 5 Sep 2016 - Tested successfully
avatar sonalitailored
sonalitailored - comment - 5 Sep 2016

I have tested this item successfully on a817850


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11493.

avatar brianteeman brianteeman - change - 5 Sep 2016
Status Pending Ready to Commit
Labels
avatar brianteeman
brianteeman - comment - 5 Sep 2016

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11493.

avatar joomla-cms-bot joomla-cms-bot - change - 5 Sep 2016
Labels Added: ?
avatar rdeutz rdeutz - change - 5 Sep 2016
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2016-09-05 19:15:41
Closed_By rdeutz
avatar zero-24
zero-24 - comment - 5 Sep 2016

Thanks ?

avatar joomla-cms-bot joomla-cms-bot - change - 5 Sep 2016
Labels Removed: ?

Add a Comment

Login with GitHub to post a comment