
Containers
I have recently installed the containers extension and have been having a bit of trouble with one site (the others are fine), which seems to originate from the manner in which the site is structured. As it references new pages, they are often in a different URL. For example, you start in login.site.com, which then tries to load dashboard.site.com, but it fails authentication on dashboard.site.com because it opens in a different container. Which then tries to open the login.site.com page again, which displays the login page, but showing it tying to complete the original authentication. I have tried to add each step along the way, but without success. Is there a way to overcome this?
Ọ̀nà àbáyọ tí a yàn
I have verified that one can get the entire set of URLs into the container by starting at the last URLS in the chain and adding them backwards, finally ending with the login URL. A bit tedious, and prone to redoing when one either discovers another previously unknown URL, or the site adds or changes to the current set.
Ka ìdáhùn ni ìṣètò kíkà 👍 0All Replies (3)
Right, sometimes it's quite problematic to use this extension. If you have dashboard.site.com opened in a different container, you have to left-click the extension icon and select "Always open this site in...", then choose the same container as for login.site.com.
Then you have to start over.
Ti ṣàtúnṣe
Thanks - that technique worked on another site, but the site in question never gives one the opportunity to "always open site" because it automatically switches (in this case) dashboard.site.com back to login.site.com. Theoretically, it should be possible to track through all the additional URLs the site is going to open (before assigning any to the target container), then, starting from the end of the chain, put each URL in the target container until you get back to login.site.com. I haven't actually tried this yet, as the site opens a lot of URLs.
Ọ̀nà àbáyọ Tí a Yàn
I have verified that one can get the entire set of URLs into the container by starting at the last URLS in the chain and adding them backwards, finally ending with the login URL. A bit tedious, and prone to redoing when one either discovers another previously unknown URL, or the site adds or changes to the current set.