Page 2 of 2
Re: V3 concept for the iframe integration
Posted: Sat Jan 05, 2019 8:57 pm
by xray
I understand the code change for direct access which means the crawlers will index those pages likewise if people know that they will be able to access the direct forum URL outside iFrame.
I think the previous code is fine and if access is needed to forum to fix simething then remove the overall_header.html code to allow access while fixing.
Re: V3 concept for the iframe integration
Posted: Sat Jan 05, 2019 9:40 pm
by axew3
Good point, you may have reason. By the way since more advanced users can find this easy and short to do, for some other it is maybe a pain in the a** if something goes wrong on some configuration. And it is commonly useful to have two tabs opened to check front end while operating on ACP.
To switch back and let load ACP into iframe, will be by the way just commenting out two lines in this way x overall_header code:
Code: Select all
if ((window.self !== window.top) != true) { //(or get loop)
// if(/adm\//ig.exec(window.location.href) === null){ // avoid x ACP
var w3all_r = window.location.href.replace(/sid=.+/gi, '');
w3all_r = w3all0Normalize_phpBBUrl(w3all_r);
hrefEnc = window.btoa(unescape(encodeURIComponent(w3all_r)));
href0 = wordpress_url_page_f + '/?w3=' + hrefEnc;
document.location.replace(href0);
}
//}
// END force w3all to iframe redirect
</script>
and into overall_footer code comment out or remove:
Code: Select all
if( /\/adm\//ig.exec(href) !== null ){
e.preventDefault();
window.open(href,'_blank');
return;
}
So this will be added into bottom iframe procedure (or as hints on inline code), with corrected hints on how to achieve the easy joke.