Embed phpBB into WordPress template:
iframe responsive how to

This is the old  iframe procedure.
New iframe procedure and code is available here:
https://www.axew3.com/w3/2018/09/wordpress-phpbb-template-embed-v3/

!!OLD OBSOLETE!! follow link above for the new v3 code and procedure!

PAGE HELP – UPDATED on 19 Sept 2018
(related views/page-forum.php – updated on 27 Sep 2017)
/trunk/addons/page-forum.php

Iframe resizer library by:
https://davidjbradshaw.github.io/iframe-resizer/

wp_w3all responsive iframe procedure

After you’ve built/created the WP forum template page via
WP_w3all phpBB embedded on WordPress Template
option on WP_w3all admin config page, and the blank page on WordPress Admin -> Pages -> Add New, titled the same of  created wp_w3all template page, so forum or board etc…, to complete the procedure and get the responsive iframe height for the embedded phpBB into WordPress template page you need:

Open with a text editor your phpBB template file overall_footer.html

and just before the closing </body> tag, add this code (do not select lines numbers column on copied code):

after you pasted this code into phpBB overall_footer.html edit the second line on added code:

change localhost to fit your domain name (example axew3.com), do NOT add http(s):// OR the point in front, just add
yourdomain.com or leave localhost if on localhost. If phpBB is at subdomain.domain.com, add domain.com as value
(MANDATORY!) or resizer won’t work
now check

in the code you added (last line): this should correctly point to the  iframeResizer.contentWindow.min.js file that you’ll go to add into phpBB root folder. You need to use the absolute URL (use http or https as needed, and adjust the url to fit your needs)
(MANDATORY!) or resizer won’t work

AFTER EDITED, save and load the modified overall_footer.html into your phpBB style folder, overwriting the default one, and so

load through ftp on the phpBB root folder (or copy/paste), the file
iframeResizer.contentWindow.min.js
that is contained inside folder
YOURWP/wp-content/plugins/wp-w3all-phpbb-integration/addons/resizer

After this, phpBB require to recompile the template, or modifications to  template files not affect (to overall_footer.html in this case). Open phpBB ACP, and so under:

Server Configuration -> Load settings -> Recompile stale style components  set to YES and save. Load one time a phpBB full forum page. So return to ACP and reset to NO, save. This step is needed one time to load the template modifications on phpBB (and any time you edit a phpBB template file to for modifications take effect), but this option should be ever set to NO into an online/production site to save server resources. It is normally set to yes only for testing/devel purpose or to apply modifications on phpBB  templates files.



If you want phpBB email notification links to point to iframe, follow this step about htaccess:

phpBB htaccess for phpBB notification email to point WP forum page (1.6.9>)

to activate the rewrite right click/copy links on iframe, to point to iframe, activate the related code removing the two lines:

/* remove this line to activate htaccess trick
and
*/ //remove this line to activate htaccess trick

NOTE: to get the iframe to be responsive for ACP phpBB admin panel, read this post.

If any question, use the forum here or at axew3Posted on Categories Wordpress phpBB integrationTags , , , , ,

Configure phpBB
to set cookie available all over domain

To configure phpBB to set cookie to be available all over the domain (and subdomains), you need to setup cookie domain and path into phpBB ACP

Open phpBB Admin Control Panel, go under

Server configuration -> Cookie settings
Cookie domain value should be set like the domain name is: so if your site domain is as in this example, axew3.com, the correct value to set is:
axew3.com
in this way cookies become available all over axew3.com and any subdomain like mysubdomain.axew3.com.

Cookie path setting should be set as a single fraction slash: /
Save settings.
If changed cookie setting in phpBB in this way, logout, CLEAN cookies from browser, and re-login.

NOTE:
if on localhost, may leave the value as is. If on subdomain, like myforum.mysite.com, set it as above using only domain name mysite.com)

( Older browsers still implementing the deprecated » RFC 2109 may require a leading . (dot) to match all subdomains, so .mysite.com )

NOTE: if cookie setting changed to be available over all domain because it was not, then all phpBB users may need to re-login using new board’s cookie settings: in this case, you may would like to force all phpBB users to re-login in case they saved their session cookie with a ‘remember me login’. This can be done by accessing phpBB ACP main page: check for option
Purge all sessions
Purge all sessions. This will log out all users by truncating the session table.
Click the Run now button.
Be sure that the cookie setting is correct before to execute these steps, or you’ll be logged out by your board until you’ll not reset to the correct cookie domain!

mysite.co.uk OR mysubdomain.mysite.co.uk, correct setting will be: mysite.co.uk (while if you are on a subdomain hosting plan like mydomain.myhostingprovider.com, than the setting will be mydomain.myhostingprovider.com, but this is a more rare case)

The following help hint hint here is obsolete as latest patched wp_w3all 1.8.9 version.

from latest patched  1.8.9 plugin version it is just required that the phpBB cookie setting is set correctly to be available over all the domain: then the plugin code will setup correctly at any time the same value for himself in WordPress. The follow is here for reference, but not more useful or needed in effect.

If still in trouble with cookie setting (you can’t login with user via WP login after path to config.php has been setup) follow this step:

just in case, this is the way to fix any problem:

open file wp_w3all.php and +- on top you’ll see these lines:

change the second line, removing the two // in front, so the above become something like (change .domain.com with your domain name)

if on localhost, setup as ‘localhost’
save/overwrite the wp_w3all.php file, then test the login. If all ok, then the cookie setting for the plugin is ok now. Re-add the two // slashes in front of the edited line on wp_w3all.php to deactivate it (or remove the line), and save/overwrite the file wp_w3all.php.

That’s all here!