locked
Got a Blank Login Page? Updated SP2 U2? RRS feed

  • General discussion

  • I’ve recently encountered a surge of complaints from companies reporting blank IAG Login Pages’ after updating to IAG SP2 Update 2.  The symptom is that they can see the title and background color but no content at all.  They also have a customized version of the login.asp page.

    It didn’t take too long to conclude that the problem was related to their customized versions of the login.asp file.  Many companies simply take the login.asp file >> duplicate and rename it.   The problem with doing this is that occasionally Microsoft will release an update to improve IAG functionality or fix problems.   If you take a copy of the login.asp file from Update1 and new features are added in Update2, it’s possible you will lose out on these features or fixes.  *note* this applies not only to the login.asp file but other files as well.


    Source of The Problem:  In SP2 U2,   IAG removed the “GetCookieDomain” function but your old login.asp file still calls it.

    The return errors were different between customers with different update-versions of the login.asp file.  Some clients reported “ASP Object Not Found” or “Type mismatch: 'GetCookieDomain’” or “internalsite.inc line ###”.



    The Fix:
      Revise your code OR redo your login.asp file OR migrate customizations to include files.


    Find the "selectLang" iavascript function by locating:   function selectLang() in your custom file and replace that ENTIRE function with the selectLang() function from your login.asp sp2 u2 version.    The reason you get an error is because selectLang function calls the "GetCookieDomain” function.  That function is no longer avaliable and was replaced by “GetCookieDomainAttri”.   


    I recommend doing this as a temporary fix and recommend companies put in more effort in utilizing INCLUDE files for their login page customizations.

    Thank you and happy long weekend for those who have Monday off J

    Dennis Lee

    Sunday, October 11, 2009 8:26 AM

All replies

  • Sticking to INC files for customization is the best approach. There is nothing that stops you modifying the asp files but with each update release these pages will over write your customization . So if you go down the route of INC files then things should work wthout problems with customization :).

    cheers,


    Faisal :>
    Monday, October 12, 2009 8:48 AM
  •  

    Hello,

    I recently got a few inquiries from people who read my article regarding the usage of INCLUDE files for customizations.


    Here is the explanation:

    IAG's LOGIN.asp file by default now calls the following .INC files

       - Logo.inc  (this is logo)
       - Wave.inc  (this is the whale wave & buttons)
       - Bottomtext.inc (this is the authorization and administrator email on the bottom)

    Try your best to use those files for your customizations.

    Do the files above not help you?  then create your own!!!

    In your Login.asp file insert a line of code similar to that of IAG calling logo/wave/bottomtext

    Example:
    <!--#include virtual="InternalSite/inc/customupdate/addcustomcode.inc"-->

    Go into your Celestix WSA / IAG and place your addcustomcode.inc file into the following directory
    C:\Whale-Com\e-Gap\von\InternalSite\inc\CustomUpdate

    Thanks!  hope this helps those who want to understand more about using INCLUDE files.




    Friday, October 16, 2009 1:47 AM
  • Hi Dennis,

    Thanks for your post.

    We're considering to add a note to the Update 2 KB to be published soon describing this issue.

    And as it was said using the INC files is the best approach to avoid such problems.

    Friday, October 23, 2009 10:34 PM