Question:
Why is dapper.net telling me that its having an internal server error when it appears that no one else is?
Overview:
I can't access yahoo's dapper.net (http://open.dapper.net/dapp-factory.jsp). I can reach the page "http://open.dapper.net", but not the actual program "/dapp-factory.jsp" When I click the link it loads for a long time and eventually says "An internal server error occurred. Please try again later." However, judging by other forums other users are not having this problem- including those on stackoverflow- and yahoo has not put forward any notice.
Things I did/ tried:
Searched on other forums, and posted this question on yahoo's forum (http://forum.dapper.net/viewtopic.php?f=4&t=5946&p=9720&hilit=internal+server+error#p9720) with no luck.
After having some other strange things happen related to chrome, i tried to use dapper.net on firefox and ie, and the same thing continues to happen. I tried to access the site from another computer, and it still happens.
Background that may/may not be relevant:
About a month ago dapper.net, (a popular online software that scrapes web pages to create rss feeds and other types of files from different web data) went down for a while, other users noted it on forums, and then the site went back up. Apparently it was a routine update. After the update, the site was live, and i began to have problems. the site would allow me to get to /dapp-factory.jsp but after trying to select content for scraping, it would eternally load the page with a "there was an error in the creation process of this dapp" in the background.
*this question was previously closed because it was originally too vague, so I have tried to clean it up. Please let me know how I can specify further if this is still the case.
Thank you
Related
We have been using the following library for months:
https://unpkg.com/react#15.3.0/dist/react.min.js
Yes - I know we can just reference 15.3 and get the URL rewrite to the latest, but they released a breaking change. That's another issue for another day. Don't get distracted.
Yesterday this simply stopped working. You'll notice that if you load the URL mentioned, that the file is TRUNCATED. Simply cuts off. This made everything we use react with break. Interestingly, if you go to the following URL (without the .js extension) - things work.
https://unpkg.com/react#15.3.0/dist/react.min
My question is - what the heck happened? Why did the URL we've been using for 8 months suddenly stop working, and who can we get to fix it. In the interim, we had a copy locally that we've started referencing (which we probably should have been doing to begin with, since we don't want the automatic upgrade). When things like this happen, who do you inform?
I'm not sure you'll find the answer as to why this file is no longer working here but based off of the website you could reached out to the creator on twitter: https://twitter.com/mjackson
On the website it says:
SUPPORT
unpkg is a free, best-effort service and cannot provide any uptime or
support guarantees.
i.e. you should probably only use this link if you are messing around with a small project and shouldn't be used for any website where you actually care about the uptime of the site.
My hosted app is showing a floating banner with a notice saying “Installation of this item may not work properly.” on its Google Chrome Web Store product page. The app is undiscoverable by searching the Web Store.
What is causing this problem? I find no additional information in the developer dashboard.
If you get this message, it is probable that there really is an error in the manifest or locale files (For example, in my case it was a trailing comma on the locale files).
The process y follow to solve the problem was:
Try to instal the app version you have just submited to the chrome store. When you try to install the app you will probably get a error message thats points you on the track of the problem of your manifest file.
Solved the problem on the app and upload it again. You may get the same error on the developers panel. Two thinghs can be appening:
A) If you've already corrected all errors in the manifest files remenber to publish the changes and what is more important remenber that the publication process may take a few minutes to become effective. The message will disappear after a while if everything is okay. (This explains why is you look on the internet for that problem you find people saying that the message will disappear after a while)
B) If error persist event after the publishing process have been complete finished. You may have not solved all error on the manifest file go back to Step 1
cheers
I had this exact problem. When I tried installing, I got an error message about a missing file.
When I removed my locales directory, everything worked fine.
In the past I had successfully created several Google Earth tours complete with audio and animation. As best I can remember, I looked at one of my tours 2weeks ago? and things were working fine.
But I look at the tours now on both my local machine and my host web server and the google earth tours have disappeared. When I look in firebug at where the code should be, I see the following error:
Failed to process gadget http://code.google.com/apis/kml/embed/tourgadget.xml. Reason: Unable to retrieve spec for... code.google.com/apis/kml/embed/tourgadget.xml. HTTP error 404
I have not changed anything within my code, so am completely at a loss.
Can anyone share what might have happened or what I need to do to get my GEs going again?
My web site is www.kavelookout.com...See www.kavelookout.com/fingers.html for where a tour should be.
UPDATE:
I believe this is the GE tour gadget code I need...
http://www.gmodules.com/ig/creator?synd=open&url=http://code.google.com/apis/kml/embed/tourgadget.xml
but as you can see, clicking on the 'More info...' link takes me to... google.com/ig/directory?synd=open&url=http://…
Does anyone know why GE Gadgets is not working at this time? Or what link I should be using to embed GE Tours? Can anyone confirm that GE Tours are having a problem, or is it me?
Much Thanks,
k
You should notice that the pages you're trying to process are no longer available, so, that's the nature of the error.
Check the link, it sais that the page is not being found, that's why you're getting a 404 error.
So I figured it out.
The embed code that was generated in the past was...
script src="http:// www.gmodules.com/ig/ifr?url=http://code.google.com/apis/kml/embed/tourgadget.xml
I'm not sure why or when it changed, but I found that the GE Tour gadget at this URL...
http://www.gmodules.com/ig/creator?synd=open&url=http://dl.google.com/developers/maps/tourgadget.xml
...now generates this new embed code...notice the differences...
script src="//www.gmodules.com/ig/ifr?url=http://dl.google.com/developers/maps/tourgadget.xml
Again, I'd love to know why things changed, but am happy to know there is an answer.
I have applications which are displayed as tabs in Facebook pages which have been working fine. They suddenly started displaying this output in the tab:
/1336720089,176820405/
if (window.CavalryLogger) { CavalryLogger.start_js(["EgxV3"]); }
__d("UFIUpdate",
Any ideas what is going on???
Here is a link to one of them: http://www.facebook.com/TweakShoes/app_132692060112327
A temporary solution is to add https:// to facebook itself. This doesn't solve the problem, but it'll allow you to see your page on a per client basis.
The best fix in the longer term until facebook fixes this issue is to go to your account settings > Security > Enable secure browsing. This will enforce HTTPS wherever it can and should resolve the issue for a lot of pages you're trying to access.
Good Luck!
After encountering this issue yesterday, I tracked it down to an apparent conflict with the JS log wrapper included as part of HTML5 Boilerplate's script.js file. In particular, the "make it safe to use console.log always" snippet. After commenting it out, the FB lib error went away and my app displayed properly.
I didn't dig into what the conflict was, but here is the snippet. If you use something similar on your page, then it may be worth investigating.
/* make it safe to use console.log always */
(function(b){function c(){}for(var d="assert,count,debug,dir,dirxml,error,exception,group,groupCollapsed,groupEnd,info,log,timeStamp,profile,profileEnd,time,timeEnd,trace,warn".split(","),a;a=d.pop();){b[a]=b[a]||c}})((function(){try
{console.log();return window.console;}catch(err){return window.console={};}})());
It's probably not a coincidence that FB's own logger bugs out with this.
Facebook has opened a bug for this issue and recently triaged it to medium priority - no word on when it will be addressed.
Nothing has changed on my end (at least I don't think anything has), but all of a sudden I'm unable to launch my app (and users reportedly are unable to install/launch) which uses the legacy require_login() function from an old version of the PHP SDK.
When I go to apps.facebook.com/myapp, I'm brought into a redirect loop between that URL and http://mysite.com/myAppsCanvasURL.
I've Googled and found some old posts where people report similar behavior but it doesn't seem like there was any resolution, and I still have no idea what could have caused this to happen out of the blue.
Any help would be greatly appreciated.
Thanks!
dshap
Figured out the answer to my own question.
My app requires access to both the user's uploaded photos as well as the user's photo tags.
To do this, I was requesting the (previously) necessary permissions by calling:
require_login('user_photos, user_photo_video_tags');
According to this developer blog post, the "user_photo_video_tags" permission is not supposed to be deprecated until November 22nd, however if I use it right now it breaks my app - if I simply remove it, there are no issues and the app works as expected.
The weird thing is I'm not seeing any exceptions thrown, but then again I'm not seeing any exceptions thrown even if I do something like:
require_login('user_photos, fake_permission');
So maybe this has something to do with the out-dated version of the PHP SDK that I'm using.
Hopefully that helps if someone else out there is having the same problem.