locked
Logo Update RRS feed

  • Question

  • We updated our logo in the Developer area and it appears that the users are unable to view and click the logo in order to test the integration.  The format is in 145X 62
    Monday, March 9, 2009 2:40 PM

Answers

  • I intially thought you were mentioning that you are not seeing the recent image that you uploaded for the application.

    Reading your original message again I understand that you are trying to say that you are not able to click on the logo?  The logo that is shown in login page, and when a user authroize an application is not clickable..

    Which page are you referring here?

    Raj

    Raj HealthVault Developer Tool http://xray.getrealconsulting.com
    Monday, March 9, 2009 4:00 PM

All replies

  • In most cases what I have seen, it is because of browser caching the image.  The image url is a constant and will not change even after you upload a new image. So there is every chance that the browser caching it.

    Try clearing the browser cache and visit the application again. 

    Rajesh
    Raj HealthVault Developer Tool http://xray.getrealconsulting.com
    Monday, March 9, 2009 3:48 PM
  • I intially thought you were mentioning that you are not seeing the recent image that you uploaded for the application.

    Reading your original message again I understand that you are trying to say that you are not able to click on the logo?  The logo that is shown in login page, and when a user authroize an application is not clickable..

    Which page are you referring here?

    Raj

    Raj HealthVault Developer Tool http://xray.getrealconsulting.com
    Monday, March 9, 2009 4:00 PM
  • We'll definitely need some more information to help out here-- can you provide more information about what you're trying to do, which page, and what the expected/actual behavior is?

    Also, it's possible this could be due to a mismatch of application IDs, in that you are configuring one ID and your users are seeing an application using a different ID.  I've seen that a number of times, and is often a simple config file mistake with copy/paste.

    If you can share the application ID you are using and the URL that you are using, I can check the configuration on the server side as well to determine if the issue is on the application side or on the server configuration side.

    Tuesday, March 10, 2009 10:34 PM