Blank page with 0 0 - no other content.

[graphicz]

This is posted in case anyone has a similar issue. No response necessary.

I have a client's site which had an issue where, when logging in, either immediately or after a brief period of clicking around, you got a blank page with '0 0' in the top left corner. By extensive process of elimination it seemed to be related to Tabber Setup. When Tabber SetUp in Javascript header functions was commented out the logging in was successful and the site could be browsed and items purchased. The Drillpine Forum (http://www.drillpine.biz/forums/view...php?f=12&t=731) sugested it was a custom additional tab displaying the FeeFo Table and/or Google Analytics causing the problem, however, reinstating the default Tabber codes and removing the Google analytics code still produced this strange blank page with '0 0' top left on logging in. The site had been upgraded to v2013 (12.0.2) and the Tabber had apparently been upgraded with it. Drillpine then stated "it's a weird bug / notabug (depending on who you listen to) in the current jQuery Tabs which only happens when a page contains a <base ... /> tag. I fixed this back in January 2013 and have sent an updated Tabber to your client." The patch is JQ-TabbedProductDescriptionsV405-UI-1-10-1 1200.zip.

Thanks to Drillpine for a solution.

[NormanRouxel]

This was a really weird one as the only JavaScript errors showing were for minor problems with other bits of code.

Once they were eliminated it was obviously a Tabber V4 issue.

Tabber V4 uses jQuery UI Tabs to do the tab display and this is very sophisticated in that the links that display a tab can have a simple href like "#tabname" which loads the tab with in-line content from a div on the page with id tabname. This is how the SellerDeck Tabber V4 works.

An alternative href like "http://www.google.com" would switch Tabs to using Ajax to fill the tab with content from a remote site. Very powerful but we don't need it for the SD Tabber.

Now, when a page is sent from a Perl based part of the site (logged-in customer, search results, etc) SD is serving these pages from cgi-bin and not acatalog. SD automatically generates a <base ...> tag pointing to acatalog that lets the page know where it can get its images, scripts, etc from.

Here's where Tabs goes bonkers. Because the page is coming from a cgi-bin url and the base tag is referring to acatalog, Tabs sees the nice simple href="#tabname" as a request for an Ajax page and goes off to a non-existent URL - hence the blank page.

The maintainers of Tabs say that this is correct behaviour (as it's strictly following what the BASE tag is for) but nearly every affected user thinks it's dumb and a simple link like href="#tabname" should always load in-line content - especially if there's a matching div on the page.

Spirited discussion on http://bugs.jqueryui.com/ticket/8637 and an article on this behaviour on http://tjvantoll.com/2013/02/17/usin...-the-base-tag/

I fixed this in Tabber V4.02 in January 2013, about a month after Tabber V4 come out so there will only be about 3 affected users.

[graphicz]

Once again, thanks to the Drillpine forum