CSS and Button issue occurs only in IE7 and Windows Server 2008 - css

I have a CSS issue that appears to only be reproducable when viewing the webpage in IE7 on a Windows 2008 web server. The issue does not occur when viewing the page on my dev version of the website (which is a widnows 7 environment). Note: the windows 2008 server and dev code (and database data) are the same.
The problem is when a popup is displayed, one of the buttons poistion is not updated (actually, the image for the button is not updated, the button itself has moved but is not displayed as such). This kind of problem is usually straight forward to fix because you can inspect the elements in IE9, but in this case you can't see the HTML that is output and you cannot select the elements in the popup. I cannot reproduce this on my dev machnine and cannot inspect the button element in the browser as you usually would be able to.
Are there any known issues that can be caused simply by websites being hosted on certain versions of windows server? (I can't think of anything else that's different beteween dev environment and the server)
I have researched on the internet but there seems to be very little regarding this specific issue. The best guess I have is that it may be caused by something being used by the site called PIE.htc and it may be one of the issues listed here: [http://css3pie.com/documentation/known-issues/][1]
[1]: http://css3pie.com/documentation/known-issues/ but this is a long shot and I have no way of verifying whether this is the case because the code must first be deployed to the 2008 server (I cannot reproduce it in dev environment and cannot inspect elements)
I cannot think what else could be causing this issue so any any suggestions will be very much appreciated.

Related

VS2010 opens website in notepad? bad hotfix?

I am using VS2010 on Windows XP pro (sp3, x86), and I just installed the hotfix kb2106584. This fix was reported by some people, example here, as having a fix for an issue I had with Asp.Net Development Server not getting opened properly from VS, which I was having previously. My issue was being caused by ESET NOD32 messing with the http traffic from devenv.exe and causing all the ports in my computer to get used up, however.
Anyway, as soon as that was finished, I opened my website back up, and clicked debug. Asp.Net Dev server pops up, which was what the hotfix was supposed to make happen, and then notepad++ opens with the tabs I had last time I used it, and IE never shows up. "Wait, what?" try it again. and again. Always notepad++, never IE, always with no new documents opened, just some completely unrelated stuff.
I've seen one other post on SO about this happening, here, but his issue was corrupted files/filesystem. My project is in source control, so I tried a delete&revert to yesterday's revision. Still opens notepad++, so that's not my issue.
I've also tried rebuilding, which did nothing, and deleting my local Solution files, which also did nothing. I restarted the program and then the computer, both to no avail.
I start to believe that this is the hotfix screwing things up, so I try to do a system restore to a couple days ago. Once again, no dice; it's still pulling up notepad++ instead of IE.
So, the questions become:
Is there a setting or two I can try changing to make it open the proper program again?
Or was this a bad/improper hotfix, and if so, how do I uninstall it? It doesn't show up in the Add/Remove Programs dialog, and I don't see an option to uninstall it in VS, or in the installer.
Thanks in advance.
[edit] Also note: Notepad++ is not actually opening the website file, it's just getting opened with whatever I left in it last time. I dunno if this helps at all, but I felt like details would be appreciated. [/edit]
Fixed:
Uninstalling n++, deleting EVERY registry entry & folder containing 'notepad++' (except one, from whose string I removed ";notepad++.exe"), then reinstalling n++ made VS stop opening notepad++.
Now it opens the default web-browser again.
[edit]
Note for anyone else out there who ends up with this specific and bizarre problem:
It would be worth a shot to try changing the "Browse With..." setting in VS, by r-clicking on Default.aspx to "Internet Explorer". My list included Notepad++ as an available internet browser.
This might be a better solution than the previous, if it does in fact work.
I didn't know this setting would allow Notepad++ as an option until I had to set it back to IE again after all this, and that may have been the problem all along. Apparently, VS just changes this setting sometimes. How or why N++ got put in as an internet browser is completely beyond me, but I did myself the favor of 'Remove'ing NotePad++ from the list, and you may wish to do the same.
Again, I'll never truly know whether or not I nuked everything when I could have changed a single setting that got mysteriously reset, but may this [lesson?] at least be recorded for posterity.
[/edit]
It took all of that to figure out that it [was?] a bogus registry entry somewhere that [may have been?] modified by the hotfix; a registry entry that neither notepad++ nor visual studio 2010 ultimate would clean up on uninstall or replace on reinstall
Which was it? I have no idea. Like I said, I didn't even use n++ this week until VS started opening it for me, and the only change I made was to install that hotfix.

After publishing, my Umbraco admin panel did not show in IE9. But it appear in FF and Chrome browsers

After publishing, my Umbraco admin panel did not show in IE9. But it appear in FF and Chrome browsers.
Note: Before publishing website, I run it from Visual Studio 2012 and I observed that everything was Okay.
Can anyone help me?
A disappearing tree is often related to an error in the Treedataservice.ashx call.
If you use F12 developer tools in IE9 you should be able to get the URL for this web service call from the Network tab, it will look something like this:
http://your-domain.local/umbraco/webservices/TreeDataService.ashx?rnd=d4859dc821714624be368bdafb1dd1d9&id=-1&treeType=content&contextMenu=true&isDialog=false&rnd2=89.4
Then when you call the web-service url from the browser direct you should be able to see the error that is returned and therefore ascertain the exact issue.
I've tested 4.11.1 with IE9 and the tree works correctly, therefore it suggests the issue is with your instance.
If the above web service is functioning correctly (it should return JSON), then it may be worth checking the other webservice calls, such as TreeClientService.asmx for errors.
In most cases checking these webservices will reveal the actual issue which is causing the tree to not render.

CSS Works In IE8 With Linux/Apache2.0/PHP4 But Not With Windows/IIS7/PHP5

I just changed from a linux/apache2.0/php4 web server to a windows/iis7/php5 web server (I only post php versions since that was a significant change).
My css is working just fine on the linux one (http://66.119.8.165/flcunderconstruction.php) but it isn't working on the windows one (http://66.119.8.236/flcunderconstruction.php).
Now, the issue only seems to be applicable to internet explorer 8 (maybe older, but I'm not testing those). Firefox and internet explorer 9 work just fine.
I think I've ruled out php issues as I created a non-php version (http://66.119.8.236/flcunderconstruction.html) and the issue persists.
I'm assuming the problem is in the css (which is quite large and throws up a lot of validation errors). But since it only occurs on the windows server and with ie8, I'm hesitant to start whacking away at the code.
Any ideas?
JJ
The broken version stops loading when it hits /include/html5.js. You only see this on IE8 because later versions handle the HTML5 stuff just fine without the polyfill.
Missing: http://66.119.8.236/include/html5.js
Present: http://66.119.8.165/include/html5.js
To test this, press F12 to open up the Developer Tools. Switch your Browser Mode to IE8. Jump over to your Network tab and press "Start Capturing". Perform a hard refresh (CTRL+F5), and watch as the files begin loading in. You'll note the 404 when it gets to the HTML5 polyfill. (Image below)
Using Fiddler2, I set up and Auto Responder to automatically add the HTML5 file from my local machine in the place of your missing file. Refreshing the request resulted in the entire site loading as expected in IE8. Put your polyfill on the other server, and you should be set.

watir-webdriver black screenshots

I'm using watir-webdriver to navigate around my website and grab screenshots in different browsers.
Sometimes the screenshots taken in IE turn out the right size, but colored entirely black. The firefox tests that get run at the same time look fine.
browser.driver.save_screenshot(screenshot_dir)
Once I remote desktop to the computer running the tests the IE screenshots look okay again. A little bit after leaving remote desktop the IE screenshots go black again.
I'm running these tests on a instance of Windows Server running on ec2.
Based on your comment that remotely accessing the machine resolves the problem for a little while... disable the screensaver on that box. I'm not sure how (if at all) the screenshot functions on IE and FF differ, but it's worth the time it would take to test the change.
Edit: I still feel like it's windows/power setting related as you logging into the box appears to have an effect, but I don't know what else specifically that could be. I tried a programmatic approach below vvv.
From what you are saying, it sounds like the Windows system is automatically locking, like it should. This would explain why screenshots work fine when you remote in, and then go to black several minutes later when the screensaver kicks in and locks your system.
If the Windows system is locked, screenshots are blacked out. This is a Windows security feature.
I would be curious to know if FF really does do screen captures on a locked system.
Here's the code I'm using to capture screenshots (Watir-Webdriver, Cucumber). I use remote Windows XP VMs for my test boxes, and have not encountered the issue using Firefox or Internet Explorer.
We did find that when you view the log with the embedded screenshot, it does not seem to work in IE - so you have to use Firefox for viewing. It's base64, so there doesn't seem to be a logical reason for this.
After do |scenario|
if scenario.failed?
encoded_img = #browser.driver.screenshot_as(:base64)
embed("data:image/png;base64,#{encoded_img}", 'image/png')
end #
end

Flex application doesn't work properly after uploading to a server

I'm a C++ programmer, but I'm a newbie in Flex. I'm developing a Flex 3 application for a social network using the FlashDevelop. For debugging I'm using the stand-alone FlashPlayer (10.3 debug) downloaded from Adobe. The application is a simple audio player which shows artist/album images.
The application worked properly on both local computer and remote server until I made some layout changes in Main.mxml. I added some HBoxes and changed Image placement. After that the application still works on my local computer, but it doesn't work properly after I upload it to a server.
Application buttons are not highlighted on over/out/click events, images loaded from the Internet are not displayed, text changed dynamically is not displayed, but when I click buttons a sound file is loaded from the internet and starts playing. It looks like some events which are responsible for components displaying are not dispatched, because some part of functionality not related to displaying still works.
To make sure that this is not a server problem, I rolled back to the previous revision. All works fine.
I suppose that this is a known issue, but I have no idea what is the reason.
Could anyone please help me to resolve the issue?
Thanks.
UDP: I observed the issue in IE and FF, I didn't test Opera and Chrome.
Are you tying to access the pixel data of the images in the new version? If so, that might be the problem, as pixel data for loaded images is not (always) accessible so that might throw a security error, which in turns breaks the rest of the interface.
Also, did you try running the remote version in the debugger? If so, is there any exception being thrown?
And no, it's not a known issue, it's the kind of annoying and hard to debug error that you sometime get when using the Flex SDK.

Resources