I have trying doing some research on this topic and couldn't find an answer to my question, so I thought you guys might be able to help.
I am loading a page in codeigniter and its giving me an internal 500 error on firebug console log, but the weird thing is the page is showing perfectly fine.
Any ideas on why that may be happening??
Nevermind guys. I just found out that it seems to be an error with the javascript code that's causing the error message.
Related
I can't access Parse.com dashboard for at least a few minutes now.
I try refreshing and from different browsers and keep getting the same errors - 500 There’s been an error, but it’s not your fault.
If you keep seeing this, check the help page for more info.
I also tried going for the help page but it is written that Parse is healthy.
I have a little problem with codeigniter.
when I make a mistake while writing code, system display the error, for example 404 Not found, and it also appears a few minutes after correction.
Does anyone advise me how to cancel?
here's my problem, I currently have a issue with a form, when the submit button is pressed, the information are not sent to the server. A programmer friend of mine checked and told me it is a security update in browser that caused the issue.
Screencap:
https://www.dropbox.com/s/3en22ryjr6idv6w/error.png
FYI, Im not a programmer, but I hope to understand more about this issue, so at least I have an idea of what is going on now. Can anyone show some resolving methods or links to tutorials to resolve it? Any help is much appreciated! Thanks in advance.
Its not a browser security update. Its the basic same-origin-policy implemented by all the browser.
Javascript loaded from a particular can't make AJAX request to other domain until same-origin-policy is relaxed. Please read more about it
understanding-the-web-same-origin-policy
What could I do to try and troubleshoot a re-captcha that had previous been working but now returns a 404 when trying to access the javascript file.
I don't think it's a coding issue because they were up this afternoon.
For what it's worth both my sites using re-captcha have the same issue.
Thoughts?
I believe the reCaptcha service may be experiencing issues. I have multiple websites that are all receiving 404 errors. I know for sure at least 2 of them were working a couple of hours ago.
This is the error I am seeing:
Failed to load resource: the server responded with a status of 404 (Not Found) http://www.google.com/recaptcha/api/js/recapcha_1-XXXXXXXX.js
I've also just found a few other posts with people experiencing the same issue.
It appears to be a global problem at the moment. Twitter feed for reCaptcha has many, many tweets.
For a quick fix, using Chrome's console I went to the "Sources" tab and edited the URL. Just change recapcha_1-XXXXXXXX.js to recapcha_ajax.js and save the change.
Please, make sure that you have version 2 in web config recaptcha api.
Version one doesn't run properly
add key="recaptchaApiVersion" value="2"
I'm having a strange issue in the ACP where the manage categories page looks like this: http://screencast.com/t/IcNbpP87 I'd really appreciate any insight you guys may be able to provide.
I've looked around for a couple days and am pulling my hair out.
Chrome
Displays a “New Root Category” form but you are unable to click a category to modify it.
Firefox & Safari:
Seems to return the proper data via ajax from the server, though it displays the information without parsing(?)
Looking at the source in firebug, it looks like data that isn’t being parsed correctly within the otherwise correct <div id="category-edit-container" class="category-content">
Source reference: http://pastebin.com/Zz7pKajj
I’d appreciate any suggestion on how to potentially move forward and get this fixed up. Thanks!
After going two day crazy with this issue in our case the solution was on the most unexpected location: It was the index.php that was corrupted the culprit. After removing some spurious code that seemed that was injected or by some way modified all is working as expected.
If there is content before the doctype header you will get this error. Check for that.