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

Warnings on update from 3.3.1 to 3.3.3 #4098

Closed
javigomez opened this issue Aug 12, 2014 · 11 comments
Closed

Warnings on update from 3.3.1 to 3.3.3 #4098

javigomez opened this issue Aug 12, 2014 · 11 comments

Comments

@javigomez
Copy link
Contributor

screen shot 2014-08-12 at 05 07 42#### Steps to reproduce the issue

Install a Joomla 3.3.1 and update it to the latest 3.3.3 (with debug mode active)

You will get the following:

  • Warning
    Update: :Extension: Could not open http://update.joomla.org/core/sts/extension_sts.xml
  • Notice: Undefined property: JUpdate::$downloadurl in /var/www/redmember2/administrator/components/com_joomlaupdate/views/default/tmpl/default.php on line 59
  • Notice: Trying to get property of non-object in /var/www/redmember2/administrator/components/com_joomlaupdate/views/default/tmpl/default.php on line 59
  • Notice: Undefined property: JUpdate::$downloadurl in /var/www/redmember2/administrator/components/com_joomlaupdate/views/default/tmpl/default.php on line 60

Expected result

Actual result

System information (as much as possible)

Additional comments

@javigomez
Copy link
Contributor Author

After a second try I was able to update with no issues:

screen shot 2014-08-12 at 05 09 46fter
You may blame the J!Tracker Application for transmitting this comment.

@brianteeman
Copy link
Contributor

I just repeated your steps with debug mode on and error reporting set to maximum. I didnt see any errors in my browser but i do have the following errors in the logs

[12-Aug-2014 12:11:52 Europe/Berlin] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 5926319 bytes) in /Applications/MAMP/htdocs/Joomla_3.3.1-Stable-Full_Package/plugins/system/debug/debug.php on line 276
[12-Aug-2014 12:11:54 Europe/Berlin] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 5782074 bytes) in /Applications/MAMP/htdocs/Joomla_3.3.1-Stable-Full_Package/plugins/system/debug/debug.php on line 276
[12-Aug-2014 12:12:01 Europe/Berlin] PHP Notice: Undefined variable: packageURL in /Applications/MAMP/htdocs/Joomla_3.3.1-Stable-Full_Package/administrator/components/com_joomlaupdate/models/default.php on line 287
[12-Aug-2014 12:12:15 Europe/Berlin] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 525928 bytes) in /Applications/MAMP/htdocs/Joomla_3.3.1-Stable-Full_Package/plugins/system/debug/debug.php on line 1109

You may blame the J!Tracker Application for transmitting this comment.

@javigomez
Copy link
Contributor Author

@javigomez
Copy link
Contributor Author

cc @nikosdion

@nikosdion
Copy link
Contributor

These are two bugs. JUpdate's error handling is atrocious is one of them. The other one is Joomla! running a gazillion things in the update script inside com_admin without the possibility to split them in chunks to avoid memory outage and timeouts.

The first one I can fix by not using JUpdate. The second one I can only partially fix. Both fixes I have already applied in CMS Update. That latter fix I would contribute to Joomla! but it's FOF-based and I understand the PLT decided not to add any further dependencies to FOF. So all I can suggest is use my third party CMS Update component. If the PLT wants to include it in Joomla!, no problem, I can contribute it. Just let me know :)

@infograf768
Copy link
Member

@nikosdion
Please ping me on skype

@brianteeman
Copy link
Contributor

FYI Rerunning without debug mode I only got the one error

[12-Aug-2014 12:37:26 Europe/Berlin] PHP Notice: Undefined variable: packageURL in /Applications/MAMP/htdocs/Joomla_3.3.1-Stable-Full_Package/administrator/components/com_joomlaupdate/models/default.php on line 287
You may blame the J!Tracker Application for transmitting this comment.

@zero-24
Copy link
Member

zero-24 commented Aug 12, 2014

@brianteeman your last error is allready fixed with 23545e4 for 3.3.4

@brianteeman
Copy link
Contributor

Can we close this now?

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

@brianteeman
Copy link
Contributor

Closed after one month without reply from @javigomez


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

@javigomez
Copy link
Contributor Author

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants