www programming

mChat is working awesome right in iFrame.

[size=150][color=#FF0000]OBSOLETE[/color][/size]
[size=190][b][url=https://www.axew3.com/w3/forums/viewtopic.php?f=2&t=911]1.9.5 has been released and the procedure is available here[/url][/b][/size]
[strike]ok, here we go: new procedure and code, DO NOT require to edit any file.
The js code to add on overall_footer.html little changed.
Use latest mChat as it is. Replace any edited file, just use mChat default files, and just follow the [url=https://www.axew3.com/w3/forums/viewtopic.php?f=2&t=904]new easier procedure and apply the new js code[/url].[/strike]
[size=150][color=#FF0000]OBSOLETE[/color][/size]
[size=190][b][url=https://www.axew3.com/w3/forums/viewtopic.php?f=2&t=911]1.9.5 has been released and the procedure is available here[/url][/b][/size]

<script>
	var boardU = "{BOARD_URL}";
	// change 'forum' with the name of the wordpress page that embed/display the phpBB iframe (page-forum template name you coosed/created)
if( /\/forum\//ig.exec(document.referrer) == null && (document.referrer.indexOf(boardU) > -1) == false )
{	
	var w3_chat_phpBBpage = true;
}
</script>

over again finally:
since looking code and evaluating possibilities, about your header/not header or footer/not footer:
did you changed on the code added into [i]/ext/dmzx/mchat/styles/prosilver/template/mchat_body.html[/i] on the line
[code]<script>
var boardU = "{BOARD_URL}";
// change 'forum' with the name of the wordpress page that embed/display the phpBB iframe (page-forum template name you coosed/created)
if( /\/forum\//ig.exec(document.referrer) == null && (document.referrer.indexOf(boardU) > -1) == false )
{
var w3_chat_phpBBpage = true;
}
</script>[/code]
the word [i]forum[/i] to match the page you created for the wp forum page template?

no, no changes, iframe resizer files are the same.
I will re-check all things within today, if no external surprises come out.

The button shortcode code do not need to fire in case the iframed wp page-forum loaded.
And the point is to find out the way to avoid conflicts on loading things when specific events/pages.
We are near to solution ...

I just thought of something, did the iframeresizerjs change? Because that's the only thing I didn't change when adding the mChat. I still see some strange things in the iframe as it does not always open as it should.
I did all the rest in clearing the load and purging caches.

I am using current verision of WP mChat is 2.1.2, which says it latest. Theme is based on prosilver (black-silver split)
Browsers, IE, chrome, Firefox and mobile chrome. (On mobile the chat box is harder to close)