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

[4.0] Extension update check #17844

Closed
brianteeman opened this issue Sep 3, 2017 · 9 comments
Closed

[4.0] Extension update check #17844

brianteeman opened this issue Sep 3, 2017 · 9 comments

Comments

@brianteeman
Copy link
Contributor

brianteeman commented Sep 3, 2017

Steps to reproduce the issue

With current J4 the extension update check never completes. Looking at the console is the following error

 Uncaught SyntaxError: Unexpected token < in JSON at position 0
    at JSON.parse (<anonymous>)
    at onSuccess (extensionupdatecheck.js?61f0bd7f3a1e51d20f4535590f3e4657:28)
    at XMLHttpRequest.o.onreadystatechange (core.min.js?61f0bd7f3a1e51d20f4535590f3e4657:1) 

@dgt41

@C-Lodder
Copy link
Member

C-Lodder commented Sep 3, 2017

@brianteeman - could you replace the minified code with the uncompressed code and try again, to get the exact line number?

@dgrammatiko
Copy link
Contributor

@C-Lodder its not the javascript, the error comes from php, the returned data is not JSON formatted. Something throws an error and the return data is html formatted

@dgrammatiko
Copy link
Contributor

@brianteeman check #17846

@joomla-cms-bot
Copy link

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/17844

@ghost
Copy link

ghost commented Sep 3, 2017

closed as having Pull Request #17846


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

@dgrammatiko
Copy link
Contributor

@franz-wohlkoenig can you re open this one?
The PR was wrong
The error is coming from:
screen shot 2017-09-03 at 15 05 12

@roland-d roland-d reopened this Sep 3, 2017
@ghost
Copy link

ghost commented Sep 3, 2017

reopened as stated above.


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

@mbabker
Copy link
Contributor

mbabker commented Sep 3, 2017

It is already fixed in staging so either the fix has not yet been merged to 4.0 or it was removed in a merge conflict.

@dgrammatiko
Copy link
Contributor

Actually re installing a fresh copy resolves the issue

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

No branches or pull requests

6 participants