First timer.
I am working on a web application with Google-app-engine.
The code is mainly servlets and jsp.
When I run the local server and try to browse the site with IE9 it looks great.
But, when trying to do so with firefox10,11 or with GC, all I get are blank pages.
I deployed one page to the server and the problem reaccures.
If needed, I will add source-code or link to the page, but currently I've got nothing. Any ideas? Thanks!!
Thanks for the comment. Still learning my ways around here, after being a loyal reader for a few years.
Anyway, I found it. It took me about 2 months, but I did. It is as simple as that:
Seems like while IE is a bit more flexible, FF and GC can't parse a path with '/'s instead of '\'s.
I got it when I installed Firebug for firefox and it ran over the code and implied that the URL for the images is invalid. A short look for that error message got me to that conclusion.
Thanks a lot!
Related
I know it may sound crazy but yeah, I thought making angular work on old IEs was crazy enough. The reason why is that our app are running fine on most browsers (laptop and fone). Now it is not working with prerenderio (which depends on phantomjs).
Note: not the whole app having the problem but just a few routes. I tried to comment our the code of that route but it still giving $rootScope/infdig.
I have been debuging it for 2 days before asking. I really need some hint what to do
Thanks in advanced for looking at my post! I developed this Commerce Kickstart site locally using Aquia Dev Desktop and everything looked and functioned great. When I post it to the server, I get the WSOD, and an error in the error_log:
PHP Fatal error: Call to undefined function delta_get_current() in /xxx/xxx/xxx/profiles/commerce_kickstart/themes/omega/alpha/includes/alpha.inc on line 222
This is a site that had been working fine remotely also, except for an issue with the checkout. (the original reason for taking it down.) I had to refer to a backup copy of the site, make some changes to get it to be more recent and then post it. That's when I received the WSOD and Php Fatal Errors.
If you have any advice on how to fix or where to proceed, please let me know. Also, let me know if you need any more info.
Thanks again.
Jason
You need to make sure that you're working with the right module and theme versions. See what you can do to update Delta to fix it, also update Omega.
I'm trying to understand why I have so many errors on the remote server but on local server everything's fine.
Any idea why I'm getting all of these error?
Thank you in advance!
looks like there's a mess with the cache files. Try disabling the cache in your remote app.
Do this in /app/Config/core.php
Look for the following:
//Configure::write('Cache.disable', true);
and remove the // to make it works.
Best,
Ok guys, I have no idea what generated these issues but after changing to a new hosting the issues disappeared. Always check online for hosting reviews to make sure it's a good one or you'll end up with some odd things happening on your website. Thanks y'all for your help and time.
While exporting a Solution from CRM, I dont get the prompt to save the exported solution.
I cleared Cookies and tried,
Upgraded to IE 9 also and tried,
I made sure that the Popup is not blocked, but these things didn't help.
This is the case with few other colleagues of mine also.\
Thanks
I usually get a popup right at the bottom of the window. Its not instant however, Crm has to generate the solution file, so if its particulary large it can take a minute or two. I would suggest clicking export, finish the dialog and then waiting 5 minutes to see if anything happens (it needs a loading icon really).
If that doesnt work, try the same again with a small solution (one entity).
I know it is too late but I am adding the solution here if someone faces the issue again.
The issue was due to URLScan. It was solved by removing URLScan from ISAPI filters for CRM web site.
I have an ASP.NET app in which I've used Vertigo's SlideShow 2 silverlight image gallery component. All was working well and the app went through testing and suddenly, after a recent deployment I get an alert box that says:
IMPORTANT: Remove this line from json2.js before deployment.
This pops up after the Silverlight component loads but then the SlideShow2 xap file seems to work fine after that.
Anyone have any ideas on why this would just start happening? I've done some research and can't come up with much and it's pretty mysterious that it just started happening. I've not directly used json2.js in this application nor have I customized the Slideshow 2 component in any way.
It also happens both in my dev and production environments.
-Kevin
Something like this?
From http://tech.groups.yahoo.com/group/json/message/1413:
Thu Dec 10, 2009 5:23 am
The server at JSON.org is getting
hammered. It turns out that there are
some sites that are linking directly
to json2.js instead of dispensing it
from their own servers. By far the
heaviest impact is from
onlinebootycall.com. My intention was
to provide the world with a free
implementation, but the world can buy
its own bandwidth.
So I have added this line as the first
line in the json2.js file:
alert('IMPORTANT: Remove this line
from json2.js before deployment.');
It will not break anything, but it
should help get a message to the
onlinebootycalls that you should not
load code from strange third party
servers. It is not safe.
- "Douglas Crockford" <douglas#...>
Don't link to json.js OR json2.js directly from json.org. It is bad etiquette, it uses their bandwidth for your site.
Copy the file to your own server, remove the line, and redeploy.
p.s. what are you using silverlight for at onlinebootycall.com? Curious... ;)
In doing more research (and taking a step back to evaluate my environment), the implementation of SlideShow2 I am using is a modified one from an opensource CodePlex project. This particular version supports streaming images and albums from Picasa's web albums. The version I'm using is located here: http://slideshow2picasa.codeplex.com/. In checking out their online dmeos they exhibit the same behavior so obviously this implementation is linking to the json2.js file on your servers as a means to interact with Picasa web.
Today I'll take at their code and see if I can rely on a local copy fo json2.js.
Thanks for helping me out.