Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[jlaunch] Update 3.10 > 3.2.7 #1246

Closed
ghost opened this issue Oct 31, 2018 · 9 comments
Closed

[jlaunch] Update 3.10 > 3.2.7 #1246

ghost opened this issue Oct 31, 2018 · 9 comments
Assignees
Labels

Comments

@ghost
Copy link

ghost commented Oct 31, 2018

Steps to reproduce the issue

Installed a new 3.10-dev.-Site. In Backend got Information that should Update on new Version "3.2.7".
bildschirmfoto 2018-10-31 um 07 08 27

Expected result

No Information about an old Version.

System information

  • 3.10
  • Template: Protostar
  • macOS Sierra, 10.13.6
  • Firefox 63 (64-bit)

CloudAccess.net

  • PHP 7.1.15
  • MySQLi 5.7.18-cll-lve

Additional comments

Looks like 3.2 ist higher than 3.10.

@zero-24
Copy link
Contributor

zero-24 commented Oct 31, 2018

What update server do you use?

@ghost
Copy link
Author

ghost commented Oct 31, 2018

Update Channel "Default".

@zero-24
Copy link
Contributor

zero-24 commented Nov 1, 2018

Please check what happen when you switch it to the correct nightly build server: https://update.joomla.org/core/nightlies/next_minor_list.xml

I guess at some point the regex can't handle it with the default update server as no 3.10 entry exists there as 3.10 is not released yet but they have a match on 3.1 on that.

@ghost
Copy link
Author

ghost commented Nov 1, 2018

Using https://update.joomla.org/core/nightlies/next_minor_list.xml the Update-Message is gone.

@zero-24
Copy link
Contributor

zero-24 commented Nov 1, 2018

Can you only reproduce this on launch or also on an local install?

@ghost
Copy link
Author

ghost commented Nov 1, 2018

i can only test on launch.

@zero-24
Copy link
Contributor

zero-24 commented Nov 1, 2018

hmm added to my todo list to analyse in detail when i get more time than today. Thanks for reporting.

@zero-24
Copy link
Contributor

zero-24 commented Nov 2, 2018

hmm I can not reproduce the issue on a local install nor on a newly created 3.9 site (at cloudaccess) and than upgraded to 3.10 how did you got a direct 3.10-dev install up and running at cloudaccess?

@ghost
Copy link
Author

ghost commented Nov 3, 2018

ther was a 3.10-dev-Installation available at launch, which is not gone. I guess this problem can't come up and close it. Thanks for your Work, @zero-24.

@ghost ghost closed this as completed Nov 3, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants