Problems With Glimpse #21

Closed
epaulk opened this Issue Apr 20, 2011 · 19 comments

Projects

None yet

5 participants

@epaulk
epaulk commented Apr 20, 2011

Hi Guys,

I installed and configured the app.

When I run my APP, I can see the eye Icon. However, nothing happens when I click it.

I test it in almost every major browser
.
Only In FireFox 4 when I refresh the page or click on a link, I get an EMPTY Popup every time. This popup goes away when uninstall Glimpse.

Some specs:
• Visual Studio 2010
• ASP.net framework 4.0
• MVC 3.0
• Windows 7
• IIS 7.5

Thanks!

Edgar

@avanderhoorn
Member

@epaulk do you get any javascript error? Also do you see a blob of JSON included at the bottom of your page? Also are you doing anything out of the ordinary, i.e. using a different view engine, or custom dependency resolver, etc?

@epaulk
epaulk commented Apr 20, 2011

When you say JS errors, do you mean like an error message?

I not notice any JS errors message or JSON info.

However, I just notice when Glimpse is ON, my JS functions stop working, so probably is a JS issue...

I use razor as view engine.

For dependency I use Ninject. Another libraries I use: Telerik ASP MVC, JQuery 1.5.2,latest Jquery UI, couple of other minor jquery plugins.

@avanderhoorn
Member

@epaulk anyway you could provide us with a basic solution that replicates the issue so that we can debug it and come up with a solution?

@epaulk
epaulk commented Apr 20, 2011

To be honest this week is very busy for me, but i will try to do it by the weekend.

Thanks!

Edgar

@avanderhoorn
Member

@epaulk not a problem and I completely understand. We you get a chance let me know how you get on and I will IM you an address to send it on through to.

@ctaswell

I have a similar system environment, and am also experiencing problems. Glimpse package installed; web.config modified automatically by installation; but am unable to see any eye in lower right hand corner of browser; am unable to browse to mysite/glimpse/config; unable to use glimpse.

It would be extremely helpful to start compiling a systematic list of system environment requirements, compatible browser versions, detailed listing for required elements in web.config, or any other configurations that need to be set anywhere else such as in global.asax app startup... etc

@avanderhoorn
Member

@ctaswell agreed by having the list of requirements, etc will start looking at this after next release which we think will fix a lot more of the immediate problems people have been having.

@ctaswell

the purpose of compiling lists of requirements, compatible browser versions, etc, is to begin solving the immediate problems of where/when glimpse should or should not work; and I'm wondering what could be a more immediate/important problem than trying to understand why an installation of glimpse does NOT run at all or where it's not even possible to see the "eye in the lower right corner of the browser"....

@mikecomstock

Hi, I'm having this problem as well. I click the 'Turn ON' button and the cookie gets set, but I never see anything on my site. No extra .js files getting downloaded, just nothing. I'm running MVC 3 in IIS Express.

@aslezak
aslezak commented Apr 30, 2011

Hi, I am having the same problem.
After installing Glimpse app runs normally, but after turning on Glimpse on config page, nothing changes. The eye icon is not there in lower right corner. I am running VS2010, app is ASP.NET 4, MVC3.

@ctaswell
ctaswell commented May 2, 2011

Discrepancy in documentation may have been cause of problem in my case. The Glimpse readme file refers to configuration via the URL: [http://yoursite.com]/Glimpse/Config/ but the trailing slash may cause problems depending on the configuration of the MVC routes in the RouteTable set in the global.asax startup file. If you have a separate route debugger that may help debugging routes. In my case, I was able to access the /Glimpse/Config page by removing the trailing slash. After solving that problem, I was then able to set a name for the Glimpse session and confirm that the glimpseState=On by clicking on the "Turn Glimpse On" button. Only then was I able to finally see the infamous "eye icon in the lower right hand corner of the browser". So in my case, the problem appears to have been one of being misled by the Glimpse documentation that had an incorrect trailing slash in the URL for /Glimpse/Config/ vs /Glimpse/Config !!! These problems could be prevented by clear documentation about any requirements necessary for MVC3 Routes with any do's and do-not's on the routes vis-a-vis the Glimpse "protocol" and "config".

@ctaswell
ctaswell commented May 3, 2011

As additional follow-up after using Glimpse, I've encountered additional problems wherein Glimpse appears to interfere with AJAX post requests preventing them from executing... which led me to want to turn off Glimpse... but the /Glimpse/Config interface only has ability to turn Glimpse on but NOT turn Glimpse off. So I turned it off in the web.config file and that did successfully turn off Glimpse and restore proper execution of the AJAX post requests.

@aslezak
aslezak commented May 3, 2011

Is the session name something that should be set to some specific value or just any value.
I am still having no luck in getting the EYE icon to show up.
Tnx

@avanderhoorn
Member

@aslezak What browser are you using, does the page include jQuery, what version of MVC are you using and have you turned Glimpse on via the /Glimpse/Config page

@avanderhoorn
Member

@ctaswell Do you know any more about how it was preventing you Ajax calls to work? It should be a seamless experience, so if you are having issues we would love to hear about it. I know someone reported issues with sync calls but that seemed like a real edge case and I haven't had a chance to address it yet. Also in the next release we are going to allow you to black list plugins, meaning if the Ajax plugin is giving you problems, you will be able to turn it off and have it not affect you using the rest of Glimpse of affect the running of your page.

In terms of turn glimpse off... on the glimpse tool strip you will see 3 icons, one of the icons is a circle with a line. This is a terminate button which removes the cookies and switches Glimpse off. Because this button is built into the UI thats why the Config page doesn't have an "off" button.

And yes the system has a problem between [http://yoursite.com]/Glimpse/Config/ vs [http://yoursite.com]/Glimpse/Config. This is really unfortunate and we plan to update the readme to reference the later and to allow the former.

Thanks for your hard work and support!

@aslezak
aslezak commented May 3, 2011

@avanderhorn Thank You, now i feel like an idiot. I have updated the jQuery file, but not the reference to it.
it all works now...thank you.

@ctaswell
ctaswell commented May 3, 2011

@avanderhorn Well, hhhhhmmmm...., I suggest you make things as easy as possible for developers in order to prevent confusion and/or problems that then require you to explain why something is not as expected. So what do I expect? The obvious: if there's an ON switch, then there should also be an OFF switch right there next to the ON switch on the same configuration page.

Now, of course, if you would like to design your user interface to provide additional OFF switches in other places, then that's certainly fine with me. But in my opinion, that would NOT justify violating a fundamental user interface design standard of providing a configuration page that enables both ON and OFF switches consistent with usual expectations. And the easier you make it for developers to use Glimpse, the easier you make it for yourself to support Glimpse.

As far as the blocked AJAX post calls, if I discover the interfering script library or other source of problem, then I'll report it here when I do.

@avanderhoorn
Member

@ctaswell feedback taken on board... I'll see that a OFF switch is added to config as well. Less friction we have to using Glimpse the better. Thanks again for the feedback

@avanderhoorn
Member

Hey guys, this one bug issue has got a bit out of control. We have tried to incorporate as much feedback as possible (i.e. we now have an off button in the config, config page works with trailing /, etc) but I can't even work out form the thread at the moment if their is still a core issue or who is having it ;S

So after the next release (i.e. 0.81), once you have pulled it down off Nuget let me know if you are still having issues and we can go from there.

Cheers
Anthony

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment