Downlodify is not working, no error message at all - javascript

I have the latest shock wave (11.9.900.117) add-on installed to my Firefox (24).
When i download and run the sample test.html file nothing is happening.But when i run the same demo linked (http://pixelgraphics.us/downloadify/test.html) HTML from Git hub works as expected.
Also i have tried this with my project too, same kind of output, nothing happens but the button hides.There are no error messages shown or can be caught since i cant go through the swfobject.js file.
I am using javascript alone, not jquery etc.
Is there anything that i am missing some basic stuffs?
Also asked in https://github.com/dcneiner/Downloadify/issues/34.
Any simple working examples would be helpfull.!!
Thanks in advance.

I know this question is old, but for anyone who encounters the same problem, here is how I solved it.
If you want to run Downlodify from the local filesystem you need to edit the Flash Player Global Security Settings and add the Downlodify folder as a trusted location.
Currently the settings can be edited here. The location URI looks like this file:///C:/Users/Name/Desktop/Downloadify-master

Related

Local JS files not loading/running on Heroku

I'm running a nodejs application on Heroku. For simplicity's sake, I went through Heroku's example application steps. Once the application was up and running, I created a public/js/test.js file which contained a simple alert( 'testing' ); command.
I then came back to the view/partials/header.ejs file and included the new test.js file appropriately. Obviously, all of this works as intended locally - but when I push it to Heroku I get no alert. When I check source using developer's tools I see that it found the js file, but clicking on it reveals an empty file.
I assume that Heroku must require some sort of build step for this - but I haven't been able to find a specific path to getting it working. Any help would be appreciated!
So, it turns out that the Brave browser was interfering with the javascript file. I've never known Brave to cause a problem like this (and locally Brave did not break it). The issue must have something to do with how Heroku loads some of the static files.
Hopefully posting this answer will help someone else encountering the same issue.

Problems opening javascript github examples

So I want to start using dc.js package to create a few dashboards, and I've found this tutorial:
https://github.com/austinlyons/dcjs-leaflet-untappd
I've downloaded the entire folder and attempted to open the html to see whether it works, but I only get some parts of the page (no data, no graphs, you can see the expected and gotten image attached). I've had the same problem with some other tutorials that I've found, and can't figure out why. I can open the page in the browser when it is a link like:
https://austinlyons.github.io/dcjs-leaflet-untappd/
Any ideas? I am using Chrome btw, but it doesn't work in IE either.
You need to run python -m SimpleHTTPServer in your terminal.
Try it yourself
If you want to play with the code as we go, I recommend downloading
the source code from this GitHub repository, navigating to the
directory where the files are located, and kicking off Python's
SimpleHTTP server so that you can see your visualization in your own
browser at http://localhost:8000 (If this is new for you, see this
link for a bit more information).
If anyone is interested there is a very nice workaround for those not willing to play around with a server. For some reason Firefox allows the opening of such pages, so one can test D3 and similar code in it without having to run a server.

Firefox add-ons: cfx run works great, cfx xpi works but the add-on does nothing

I've been working on a Firefox extension (basically just a "content script" or "page mod", whichever term works for you) that works exactly as expected when I use "cfx run" but when I do "cfx xpi" and install it, nothing happens. In cfx run, my content script works perfectly, with no errors from the command prompt. If this is any help, I do see an error when I exit the test run:
###!!! [Child][DispatchAsyncMessage] Error: (msgtype=0xAA0001,name=PTexture::Msg
___delete__) Route error: message sent to unknown actor ID
But this looks different from JavaScript errors (and really looks more "internal" to me, something buggy about the SDK maybe?). Anyway, when I do cfx xpi (with or without the "--no
-strip-xpi" option) everything seems to work fine. No errors from the console, the installation seems to work), but when I go to the page I'm writing the script for, nothing happens. The page loads as it usually does, but the content script doesn't do anything; no changes to the page, no errors, really just no hint whatsoever of what the function is going on.
So of course I spent a bit of time on Google and also this site. I found a couple questions that were slightly similar but either unrelated or unanswered. Here are a few of these:
creating xpi does not work (this one was a mac vs. Windows issue)
Create XPI package with the Add-on SDK? (this one was kinda close but I didn't use contentScript in my main.js and did use the PageMod object like the guy suggested)
Firefox SDK Sample Add On Exported XPI Action Button Doesn't Show Up (My console didn't show any errors, so this one didn't help either).
And of course, I tried all the obvious stuff (restart Firefox, reboot the computer, change the content of the scripts, etc.) and the result is still the same: fine in cfx run, compiles and installs fine but does nothing after cfx xpi.
Also, in case it would be helpful to you guys, here's my main.js:
var data = require("sdk/self").data;
var pageMod = require("sdk/page-mod");
pageMod.PageMod({
include: "*.somepage.com",
// NOTE TO SELF: include all object files here.
contentScriptFile: [data.url("Data.js"), data.url("Layout.js"), data.url("HTML.js"), data.url("Restyler.js"), data.url("Shortcut.js"), data.url("ARIA.js"), data.url("Apricot.js")]
});
This follows closely with everything I've read in the documentation and tutorials, but still for whatever/no-good reason it only works in cfx run. So unfortunately, all I can really tell you for sure is that something somewhere is somehow blocking, overriding, or otherwise preventing the XPI from doing its thing (mysterious? Sure. Frustrating? You have no idea...). :))))
I'm sorry I'm not sure what else to say, lol. I know JavaScript (and a bunch of other languages) but this is my first attempt at using the SDK (which seems to be more trouble than it's worth). Gosh I wish they would update the GreaseMonkey compiler, or at least bring back the Add-On Builder... oh crap did I say that out loud? :)
All joking aside though, any potential solutions, workaround or other insights would be greatly appreciated. Thanks.
Are you using private browsing in your Firefox setup?
If so then you need to add
"permissions": {"private-browsing": true}
to the package.json file.
More information:
https://developer.mozilla.org/en-US/Add-ons/SDK/High-Level_APIs/private-browsing#Opting_into_private_browsing

Visual Studio 2010-intellisense and highlighting in javascript doesn't work

In one of my solutions in javascripts files the intellisense suddenly stopped working.
All of the features are disabled - ctrl+space doesn't bring the list - like this
I took the print screen from another solution
and also the file looks like it was plain text -keywords has no colors.
I tried to open new solution and move the files there - still the same.
Files has intellisense only when I am debugging.
It feels like VS2010 see that those files are text files instead of js files.
It has something to do with tfs because it first happened to another member of the team and as soon as I took latest version of the solution - it happened to me.
When I create new js file - it looks fine , BUT after saving
the file , closing and reopen - again it is not colored
I found out that the problem is in one specific project - if I add js files to another project in the same solution it seems to be ok.
After some research and tests. This problem could be a couple of things:
Your file's extension is not .JS.
You are using an express edition.
You have not installed the Web Developer component on your installation (or removed it).
Let me know if this help you, If not I will look forward something else.
The complete reference about the JScript Intellisense on msdn:
http://msdn.microsoft.com/en-us/library/vstudio/bb385682(v=vs.100).aspx
As you can see in the image below, I just created a single javascript file in my Visual Studio 2010 with Web developers components and it is working:
So I solved this problem ....
I wanted to watch some value with QuickWatch (Shift+F9)
I got the message "Unable to evaluate the expression. The object invoked has disconnected from its clients." I pressed the green icon to refresh the values. After I closed the QuickWatch window I realized that I got the intellisense and highlighting back.
After a checkin to TFS, my colleague pulled the solution and got the intellisense and highlighting back as well.
Probably some weird bug in VS2010.

Viewing the updated HTML in ie6

I am working with ie6 (unfortunately) and i am having a javascript error. Its wondrous error message gives me a line in the html source, but unfortunately the javascript that does run changes the code for the page(dramatically). So the error that its pointing me to is a closing div tag, not actual code.
Is there a way to view the updated code for the page so I can at least know where my code is breaking?
I should also point out what im developing in.
I am developing a sharepoint 2007 solution for an winxp and ie6 user base. I am working via remote desktop on a sandbox winserver 2008 r2 and can access the site from my terminal. Now, unfortunately in my sandbox server i have ie 8 in which my code works. So im stuck on ideas. If anyone knows how to view the updated source on the page, i would be very grateful.
Thanks.
Edit. I should also mention i dont have admin access on my terminal. So i cant install visual studio. It would take a couple weeks for an issue ticket for temp admin access to install it, and this is sort of important.
If you can't install anything and the error console information isn't meaningful, then about all you can do is start modifying your code until you can find which section is causing the error. The kinds of modifications you can do are as follows:
Comment out a chunk of code in a way that won't cause more errors. If the error goes away, then you know it's in that block of code or something that code calls. Put that block back in and then comment out a piece of it and so on until you narrow down where the problem is.
Start inserting alert("1"), alert("2") prompts into your code with the goal of identifying which alert the error comes before and after until you've eventually tracked down where it is. When you rule out an area, remove the alerts to make it feasible to still run the app.
On a more modern computer (e.g. Vista/Win7) go to Microsoft's site and download both Microsoft Virtual PC and the Windows image for XP with IE6. You can then actually install things into the VM and do real IE6 debugging or at least see what the actual error is.
Find a computer with XP/IE6 on it that you can install real debugging tools on.
Build your own dummy little debug window using a textarea and a couple functions that append text to it. Put that into your browser page and start sprinkling mydebug("Entering function foo") statements throughout your code so you can narrow down which statements occur before and after the error and eventually find the error. This is how I've done some IE6 debugging when it was't worth the trouble of setting up a full-blown debug environment for IE6. This works much better than alerts for some types of problems because it doesn't interrupt the flow of the app or require lots of user intervention and you can scroll back through the history.
If you are using visual studio you can use it to debug js errors in ie.
Go to the Advanced Internet settings in ie and make sure that the two
Disable script debugging settings are turned off (so that script debugging is enabled)
and that the setting
display a notification on every script error is enabled.
If you don't have visual studio installed you can download and install microsofts script debugger (it's free just google it) and use that, tho it is not as easy to work with and won't give you as much useful information

Categories