?
avatar sonqor
sonqor
8 Apr 2016

Steps to reproduce the issue

While trying to update my Joomla I am brought to the "updating" page where the progress bar shows up and a message that says 'Updating your Joomla files. Please wait ...' but nothing happens. I looked in my server log files but found nothing unusual, however I do get an error in the browser console on the 'updating' page that says:

Uncaught TypeError: window.pingExtract is not a functionscreen shot 2016-04-08 at 02 23 49

Expected result

Actual result

System information (as much as possible)

Additional comments

avatar sonqor sonqor - open - 8 Apr 2016
avatar alexonbalangue
alexonbalangue - comment - 9 Apr 2016

myself server updating on local/vps 's passed, purge your cache & cookie also in your browser, maybe before update as possible u can, trying firefox browser, so it's rule,

avatar sonqor
sonqor - comment - 9 Apr 2016

Hi
I tried use Firefox and also use my Android phone browser but the result is same.
May I update joomla manually? ??


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

avatar alexonbalangue
alexonbalangue - comment - 9 Apr 2016

upload all files by ftp on u server (= same version actual joomla )

purg cache everywhere & then tried updated maybe works, so!! create backup not loose data and beginning new.


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

avatar sonqor
sonqor - comment - 9 Apr 2016

Thanks. But is this problem global.?? Or it only occurred for me?


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

avatar brianteeman
brianteeman - comment - 9 Apr 2016

Based on the lack of anyone else reporting this it does look like its something in your own installation


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

avatar brianteeman
brianteeman - comment - 9 Apr 2016

And the only references i can find on google are your own posts :( Closing as it is an issue on your installation and not a core bug


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

avatar brianteeman brianteeman - change - 9 Apr 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-04-09 20:14:05
Closed_By brianteeman
avatar brianteeman brianteeman - close - 9 Apr 2016
avatar brianteeman brianteeman - close - 9 Apr 2016
avatar eightdog
eightdog - comment - 11 Apr 2016

For the record, I have arrived here as I have the same issue going from 3.5.0 to 3.5.1.


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

avatar brianteeman
brianteeman - comment - 11 Apr 2016

The same issue being the progress bar not moving or the same issue being the message Uncaught TypeError: window.pingExtract is not a function


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

avatar eightdog
eightdog - comment - 11 Apr 2016

The same issue with the progress bar not moving. I have not investigated
any further. I am wondering if it might be to do with my SEO or CSS
compression extension.

On 11 April 2016 at 12:14, Brian Teeman notifications@github.com wrote:

The same issue being the progress bar not moving or the same issue being

the message Uncaught TypeError: window.pingExtract is not a function

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


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#9802 (comment)

avatar brianteeman
brianteeman - comment - 11 Apr 2016

I would say its not the same issue then

On 11 April 2016 at 12:17, eightdog notifications@github.com wrote:

The same issue with the progress bar not moving. I have not investigated
any further. I am wondering if it might be to do with my SEO or CSS
compression extension.

On 11 April 2016 at 12:14, Brian Teeman notifications@github.com wrote:

The same issue being the progress bar not moving or the same issue being

the message Uncaught TypeError: window.pingExtract is not a function

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


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
<#9802 (comment)


You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#9802 (comment)

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

avatar sonqor
sonqor - comment - 11 Apr 2016

That's mockery to close the topic. This is a BUG and you should responsible for this. Just say: MOCKERY.

avatar brianteeman
brianteeman - comment - 11 Apr 2016

Please check that media/com_joomlaupdate/update.js exists

avatar sonqor
sonqor - comment - 12 Apr 2016

Yes it's exists

avatar supermirel
supermirel - comment - 24 Apr 2016

Same issue here


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

avatar eightdog
eightdog - comment - 24 Apr 2016

Follow the manual install method instead. Works a treat.
On 24 Apr 2016 12:41 pm, "supermirel" notifications@github.com wrote:

Same issue here

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


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#9802 (comment)

avatar supermirel
supermirel - comment - 24 Apr 2016

Uncaught TypeError: window.pingExtract is not a function; and also the status bar is not moving. Exactly the same issue as sonqor


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

avatar brianteeman brianteeman - reopen - 24 Apr 2016
avatar brianteeman brianteeman - change - 24 Apr 2016
Status Closed Confirmed
Closed_Date 2016-04-09 20:14:05
Closed_By brianteeman
avatar brianteeman
brianteeman - comment - 24 Apr 2016

Re-opened


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

avatar brianteeman brianteeman - reopen - 24 Apr 2016
avatar brianteeman
brianteeman - comment - 24 Apr 2016

@supermirel Which browser and operating system


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

avatar supermirel
supermirel - comment - 24 Apr 2016

Primary browser Chrome Version 50.0.2661.87 m (64-bit), but in any other browser happens that too


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

avatar alexonbalangue
alexonbalangue - comment - 24 Apr 2016

trying updated your browser maybe work and doing all process Patch.
Or mozilla firefox 45.0.2 (latest version)...

avatar brianteeman
brianteeman - comment - 24 Apr 2016

And the operating system?

On 24 April 2016 at 12:55, supermirel notifications@github.com wrote:

Primary browser Chrome Version 50.0.2661.87 m (64-bit), but in any other

browser happens that too

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


You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#9802 (comment)

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

avatar supermirel
supermirel - comment - 24 Apr 2016

Windows 10 x64 PRO


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

avatar supermirel
supermirel - comment - 24 Apr 2016

The browser is already up to date.


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

avatar alexonbalangue
alexonbalangue - comment - 24 Apr 2016

its bizarre! clear cache everywhere and unlock on control panel Joomla (your website)

you did https://docs.joomla.org/J3.x:Upgrading_from_Joomla_3.4.x_to_3.5?

Do this https://www.youtube.com/watch?v=VLt-WQCOCpw same version actual you use version your website and trying again update.

avatar supermirel
supermirel - comment - 24 Apr 2016

After many failed attempts using Joomla built in Updater, I finally succeeded to upgrade using Method B form the link on the top. But that does not mean I found the problem that caused the issue or that I found a legit solution to it.


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

avatar expntly
expntly - comment - 29 Apr 2016

Same issue here while trying to update from 3.5.0 to 3.5.1. Tried both direct and FTP, no success. Cleared all caches. Exact same symptoms as @sonqor.

index.php shows a text/javascript fragment, that's where it fails, this function just does not exist on window. Where does it come from?

jQuery(document).ready(function(){
window.pingExtract();
});

avatar wilsonge
wilsonge - comment - 8 May 2016

I just tried doing a 3.5.0 to 3.5.1 update in a variety of browsers on my Windows 10 laptop and am unable to replicate this bug.

Looking around on the web it seems to stem from the javascript directory not being created when doing the 3.5.0 update for Joomla Update. Without any more information I can't really debug this any further give you a valid solution :(

avatar expntly
expntly - comment - 11 May 2016

@wilsonge Is there a way I can create that javascript directory manually? What's the path?

avatar Markkojak
Markkojak - comment - 23 May 2016

I have exactly the same problem on one site.

I'm not sure what to do to overcome the difficulty.

avatar expntly
expntly - comment - 9 Jun 2016

Any updates? Would it help to upgrade directly to a "post 3.5.1" version?

On Mon, May 23, 2016 at 3:03 PM, Markkojak notifications@github.com wrote:

I have exactly the same problem on one site.

I'm not sure what to do to overcome the difficulty.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#9802 (comment)

avatar quentin-oyopi
quentin-oyopi - comment - 29 Jun 2016

Hello,

You can check that you have this Joomla folder : /media/com_joomlaupdate/js
If you don't have a js folder, create one and move all the js files from /media/com_joomlaupdate/ to /media/com_joomlaupdate/js/
(you can add an empty index.html file in this new folder for security reasons).

You must have these files here :
/media/com_joomlaupdate/js/default.js
/media/com_joomlaupdate/js/encryption.js
/media/com_joomlaupdate/js/json2.js
/media/com_joomlaupdate/js/update.js

For me, this problem occurred after an error trying to update to 3.5.1 (from 3.4.8) because of a corrupted Joomla_3.5.x_to_3.5.1-Stable-Patch_Package.zip update file.


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

avatar euoceo
euoceo - comment - 30 Jul 2016

Interesting, I had the same problem too. The thread above, helped solve it. The directory com_joomlupdate was missing! Copied it from another Joomla website and all worked. Thx for the tip quentin-oyopi. There was an error at the end, didn't copy it down, something about "a manifest error". I suspect due to the com_ directory I used was from a 3.6 website. Cleared cache, site looks fine.

avatar andrepereiradasilva
andrepereiradasilva - comment - 21 Aug 2016

this seems to be related to broken installations with missing files.

You must have these files here :
/media/com_joomlaupdate/js/default.js
/media/com_joomlaupdate/js/encryption.js
/media/com_joomlaupdate/js/json2.js
/media/com_joomlaupdate/js/update.js

can this be closed?

avatar wilsonge wilsonge - change - 21 Aug 2016
Status Confirmed Closed
Closed_Date 0000-00-00 00:00:00 2016-08-21 22:33:16
Closed_By wilsonge
avatar wilsonge wilsonge - close - 21 Aug 2016
avatar supergosho
supergosho - comment - 28 Jan 2017

I fix this after change .htacces redirects (made by myself) 301, rewrite conditions etc. Suggest to take clear .htaccess file from new installation.

Add a Comment

Login with GitHub to post a comment