Hi.
This seems simple enough in premise, but I'm totally stumped... What's the accepted wisdom on creating links to the site index page and the catalog index page (ie: top level section)?
If I create a link to "/index.html", the B2B script (bb.pl) doesn't parse/replace the link. It does the same thing with "/", and "../" and "../index.html", and "/acatalog/", and "../acatalog", etc. The upshot of this is that if a logged-in user visits the home page, or links to the catalog homepage from a brochure page, he gets presented with the login prompt again on his return because the bb.pl script has dropped the ball.
Presumably, the bb.pl script doesn't know what to do with links that contain paths, so it ignores them. Is this the case? If so, is this likely to be fixed any time soon? I can create a page outside of the /acatalog folder (/index.html) using Business, so surely it should be able to deal with linking to and from it?
As always, any help would be appreciated.
This seems simple enough in premise, but I'm totally stumped... What's the accepted wisdom on creating links to the site index page and the catalog index page (ie: top level section)?
If I create a link to "/index.html", the B2B script (bb.pl) doesn't parse/replace the link. It does the same thing with "/", and "../" and "../index.html", and "/acatalog/", and "../acatalog", etc. The upshot of this is that if a logged-in user visits the home page, or links to the catalog homepage from a brochure page, he gets presented with the login prompt again on his return because the bb.pl script has dropped the ball.
Presumably, the bb.pl script doesn't know what to do with links that contain paths, so it ignores them. Is this the case? If so, is this likely to be fixed any time soon? I can create a page outside of the /acatalog folder (/index.html) using Business, so surely it should be able to deal with linking to and from it?
As always, any help would be appreciated.
Comment