WP W3ALL 2.4.0> phpBB to WordPress

WP w3all WordPress phpBB plugin install help page

The phpBB to WordPress way

The faster, easy and secure

WordPress phpBB 2.4.0 > integration by email

Note: follow this instead, if you want to integrate, configuring the WordPress to phpBB integration way.

The difference between this way to integrate, respect the WordPress to phpBB way, is mainly one: update changes done by users or admins into their phpBB profiles, are updated into WordPress for the same user, when the same user will visit the WordPress side as logged user in phpBB , or when will login in the WordPress side. Because this is a WordPress plugin (along next 2.4.0> releases, may a phpBB extension will be provided that will allow a complete update at mean time integration in the phpBB to WordPress way, adding or updating users in WordPress at mean time when updates occur in phpBB side). It is possible to use redirects tricks: if you want to force user addition into WordPress when user register OR login in phpBB using redirects tricks check this:
Add user into WordPress when register OR login in phpBB side

The other important thing that you need to consider, integrating in the phpBB to WordPress way, so where you’ll leave users to update their email and register only in phpBB, is that since the integration works by email, if you let users login in WordPress also, this is the case where the plugin may works as unexpected, because when searching for user by email on WP login action, and the email has been changed in phpBB, there is no way to check a match for the same user if usernames/email pairs mismatch. The user could so try to login by username, and will work if username match, but if it mismatch (the integration works by email, but try to check for username in this case, when a match not found by email) and phpBB usernames with forbidden WP characters have been may added in WP after removing those forbidden chars, so (also) the username will not match OR will match the username of some other user!

Consider that if you let users login in WordPress side in this scenario, an user that change his email in phpBB, then come to login into WordPress using email (because you allow users to login also in WP) the user will not be able to login by email, but only by username until a login not executed (that will cause so the email to be updated, based on username) and if username match. For the same reason, usernames on both phpBB and WordPress needs to match in this case.

In the phpBB to WordPress way you so choose to let users to Login, Register, Update Password in phpBB side BUT if managing an integration where mismatching usernames exists in some case, you SHOULD SO (it is REQUIRED in this case) LEAVE USERS to Register and update their email ONLY IN WordPress.

Note that it is not mandatory to transfer old phpBB users into WordPress when integration start, anyway there is a transfer option on plugin admin that you can activate to transfer old phpBB users into WordPress. Note also that as admin, if you want to change an email for an user at mean time also in WordPress when you change it may via phpBB ACP, you’ll have to do the same for the same user in WordPress, or until the same user will not visits the WP side, you’ll not see the same update in WordPress.

Consider that as WordPress admin, you could see that so in phpBB there are users that are still not existent in WordPress. The reason is the above explained when using the plugin in the phpBB to WordPress way.

This mode to integrate, phpBB to WordPress way, require as MANDATORY to disable user’s registration in WordPress and avoid user’s email change in WordPress. It is your task to not allow user’s registration and email update in WordPress side.

About the way on how phpBB usernames containing forbidden and not allowed characters into WordPress, are added or transferred into WordPress since 2.4.0> read this post:

phpBB usernames with forbidden characters in WordPress

Disable registration in WordPress, and be sure that users are NOT allowed to change/update password in WordPress.

Said all that, you need to follow same instructions, configuring phpBB and WordPress, as explained on WP to phpBB help, where

To Install and Configure

FOLLOW THESE STEPS

wordpress-phpbb-integration/#installAndConfig

Follow phpBB Side and WordPress Side steps on that page, and remember (again) that it is your task to avoid user’s email update, and registration in WordPress, configuring based on all said above the integration in the phpBB to WordPress way.

More considerations:

…..

phpBB WordPress template integration (iframe v5)

v5 version (for cool people)

PAGE HELP – JS code – updated on 03 Mar 2021
(related addons/page-forum.phpupdated on 03 Mar 2021)

wp-w3all-phpbb-integration/trunk/addons/page-forum.php

wp_w3all plugin 2.1.1 or >

phpBB SEO mods compatible – (READ ALL this page)

wp_w3all responsive iframe procedure

WordPress phpBB iframe template integration

MEMO: to update to latest code, it is required to rebuild page-forum.php (or whatever you named it) via plugin admin, OR manually substitute it into your active WP template folder, with the new one that you find/copy into /wp-content/plugins/wp-w3all-phpbb-integration/addons. You’ll may need to update also the iframeResizer.contentWindow.min.js and iframeResizer.contentWindow.map files added into phpBB root, with news updated files you’ll find into /wp-content/plugins/wp-w3all-phpbb-integration/addons/resizer folder (this step is not ever required, but only when iframe resizer library updates, which is notified on plugin changelog when plugin released). Done this, substitute the phpBB overall_header.html and overall_footer.html code (re-adding needed values) with the new v5 code here below. Do not forget to rebuild phpBB template to make phpBB template modifications take effect.

NOTE for domains like: mydomain.co.uk – note that to fix the resizer to work fine on this kind of domains you have to open page-forum(or whatever you named it).php into your active WP template folder and search for these two lines of code, adjusting as they need to be, to match the same domain you setup into overall_footer.html code

WP_w3all template integration steps

After you built/create the WP forum template page via option
WP_w3all phpBB embedded on WordPress Template
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 (then you’ll have into your active WordPress template folder a file named page-forum.php or page-board.php etc), to complete the procedure and get the responsive iframe height for the embedded/iframed phpBB into WordPress template page you need:

overall_footer.html code

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 rows numbers on copied code):

after you pasted this code into phpBB overall_footer.html
edit following lines:

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

change value
https://subdomain.w3host.com/wordpress/forum
on this line, to point to the URL of the WordPress created/named forum page (do not add final slash and change http or https as needed)
MANDATORY!

Change the w3 value of the line

to fit the value you may changed in plugin admin where option: Fancy URL query string for the WordPress page forum that embed phpBB

Finally, check this line

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 via ftp into the phpBB root folder (or copy/paste), both files
iframeResizer.contentWindow.min.js AND iframeResizer.contentWindow.map
that you find inside the folder
wp/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. Leave as is at moment, especially if you follow adding also the code on overall_header.html (more below) to redirect any phpBB direct URL to the iframed WP page: then after tested that all work fine, return to ACP, and reset to NO and save. This step is needed 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.

overall_header.html code

If you want phpBB email notification links or any phpBB direct url to be redirected to the wp iframed forum page follow this step:

Open with a text editor your phpBB template file overall_header.html and immediately after the closing </title> tag add the following code:

On added code, change URL on the line where:

to fit/point to the WordPress iframed forum page: DO NOT ADD final slash and setup as http or https as needed.

Change the w3 value of the line:

to fit the value you may changed in plugin admin where option: Fancy URL query string for the WordPress page forum that embed phpBB

Reset to No the Recompile phpBB template option. Before to follow READ NEXT NOTE and memorize!

NOTE: if you need to disable/remove the overall_header.html javascript code, that do not allow (until javascript enabled on browser) to access front end real phpBB urls, forcing the redirect to the WP forum page. You can  disable javascript on browser, if you do not want to remove/disable the added js snippet into the phpBB overall_header.html file. It is also !important to remember this if in trouble with login, and recompile Stale Template option in phpBB is set to Off at this time.

For testing or for any other reason, you could also comment out the line where:

change into this:

so phpBB direct URL’s will not being redirected to the WP page forum URL. Remember that to apply template modifications, phpBB require to recompile templates files.

NOTE: if you added the code above into phpBB overall_header.html then you’ll never activate (it is not active by default) this part of the code you added into the overall_footer.html:

Refer to v2 or v1 code for htaccess old solution editing phpBB notifications files.

[w3allcustomiframe] shortcode how to

check all others shortcodes listed under the “common how” to section

Note: this shortcode work only if it is activated option into WP plugin’s admin (advanced shortcode):

Activate shortcode

It may require you to know something about iframes and how they work, but looking into examples may you can easily understand the way:

the shortcode to embed a page need to be used for example like this:

Params
resizer
check_origin
url_to_display
css_iframe_wrapper_div
css_iframe_elem_iframe

resizer (yes/no)
default false. * use the iframe resizer or not (if no may pass fixed width and height values for the iframe to display, via css_iframe_elem_iframe param)

checkOrigin (true/false)
Default true. See checkOrigin reference.
Pass false to disable.
To provide a value for checkorigin, set this param (for example) to https://mysite.com (it will be so converted into array to pass the valid domain value you want to set)

url_to_display (url)
the src url to the page that the iframe will point to

css_iframe_wrapper_div (inline css inside attribute style=”…”)
css inline style of the iframe wrapper, element <div style="..."

css_iframe_elem_iframe (inline style inside attribute style=”…”)
css inline style for the element <iframe style="..."

* Note: to use the iframe resizer, the page that contain the content to display, that reside outside WordPress (like the integrated phpBB forum into this online example) need to embed this code just before the closing </body> tag:

The iframeResizer.contentWindow.min.js file to point to can be copied into plugin folder:

wp-content/plugins/wp-w3all-phpbb-integration/addons/resizer

and added/pasted where necessary

A shortcode example:

The follow example, display the content within this domain: since using resizer, it has been necessary to add the iframe resizer lib into the phpBB template file viewtopic_print.html, just before the closing </body> tag. Click into links to see behavior (pages within this domain will continue to display, and (may, may not) also some other external link you’ll click will load here)

Shortcode: phpBB PM into WordPress

WP_w3all phpBB WordPress 1.9.9 >

WP_w3all phpBB PM into WordPress shortcode version 1.0

check all others shortcodes listed under the “common how” to section

The [w3allphpbbupm] shortcode just display phpBB Private Messages count into a div, which html output result will be by default like this:

<div id="w3pm_id" class="w3pm_class"><a href="https://localhost/wp51/phpBB3/ucp.php?i=pm&folder=inbox">You have 1 unread forum PM</a></div>

To display this way, you’ll add the shortcode as is: [w3allphpbbupm]

To change attributes class name, id or to get a element link with target _blank or to add inline style to the div element, arguments that are possible to pass are:

'w3pm_class' => 'w3pm_class',
'w3pm_id' => 'w3pm_id',
'w3pm_inline_style' => '',
'w3pm_href_blank' => ''

[w3allphpbbupm w3pm_class="myclass" w3pm_id="myid" w3pm_inline_style="padding:10px;border:1px solid grey;" w3pm_href_blank="1"]

w3pm_class and w3pm_id are setup by default with same name as value for the id and class div’s element attributes if not passed as arguments, others two w3pm_inline_style and w3pm_href_blank simply not affect if not passed.

To get target="_blank" , pass as on example the w3pm_href_blank="1" argument

[w3allfeed] RSS raw examples

How to use w3allfeed shortcode

These examples show raw results (scroll down to see RSS from external resource) of the w3allfeed shortcode used like this, with little style applied to li elements:

that grab last 3 forums news within this same domain forum:

Latest 3 news from axew3.com forums

  • The older, the simpler: robotstxt.org. robots.txt in a nutshell

    I fall on this today, after i know it since his creation: has been a surprise to see that, in all these years, it changed nothing at all!
    http://www.robotstxt.org

    Statistics: Posted by axew3 — Mon Apr 05, 2021 7:35 pm — Replies 0 — Views 15


  • Avatar bug on last topics: non registered user's post associated with actual logged in user (in certain conditions)

    Manual fix (or download the ready file more below)
    file
    /wp-content/plugins\/wp-w3all-phpbb-integration/views/phpbb_last_topics.php
    search for:

    CODE:

    $w3all_avatar_display = ( is_email( $phpbbUAVA ) !== false ) ? get_avatar($phpbbUAVA, $w3all_last_t_avatar_dim) : '<img alt="" src="'.$phpbbUAVA.'" class="avatar" width="'.$w3all_last_t_avatar_dim.'" height="'.$w3all_last_t_avatar_dim.'">';

    change into:

    CODE:

          if(is_email( $phpbbUAVA )){      $w3all_avatar_display = get_avatar($phpbbUAVA, $w3all_last_t_avatar_dim);      } elseif(!empty($phpbbUAVA)){      $w3all_avatar_display = '<img alt="" src="'.$phpbbUAVA.'" class="avatar" width="'.$w3all_last_t_avatar_dim.'" height="'.$w3all_last_t_avatar_dim.'">';      } else {      $w3all_avatar_display = get_avatar(0, $w3all_last_t_avatar_dim);       }

    then search for

    CODE:

    $countn++;

    change into:

    CODE:

      $phpbbUAVA = '';  $countn++;


    or download the ready and updated file on repo:

    https://plugins.trac.wordpress.org/expo ... topics.php
    and substitute it into folder:
    /wp-content/plugins/wp-w3all-phpbb-integration/views/phpbb_last_topics.php

    Result: if an user is not existent into wordpress, and own an avatar in phpBB his phpBB avatar will display.
    If the user exist in WP and own an avatar, the avatar will display.
    It the user do not own any avatar that can display, both in wp and phpBB, then the dafault WP gravatar, based on WP Settings -> Discussion -> Gravatar will display for the user.

    Statistics: Posted by axew3 — Mon Apr 05, 2021 9:16 am — Replies 0 — Views 64


  • Apache HTTPS/SSL on Windows procedure 2021 - virtualhost, subdomains

    To setup virtual hosts, mysql, apache and php, read this (on bottom about setup virtual hosts), where there is line "To setup custom domain name or subdomains":
    https://www.axew3.com/w3/forums/viewtop ... f=7&t=1637

    From 2010, when this article has been write http://rubayathasan.com/tutorial/apache-ssl-on-windows/, nothing +- have been changed about how to setup https ssl on Apache in a Windows os.
    Here on 2021 report in steps, with corrections and my hints (to get work my test HTTPS on Apache server in Win, as reminder):
    Start assuming that you have an apache web server installed and configured already with virtual hosts on htdocs.conf.
    So the htdocs.conf will contain something like this for my working example:

    CODE:

    # All of these directives may appear inside <VirtualHost> containers,# in which case these default settings will be overridden for the# virtual host being defined.##NameVirtualHost *:80<VirtualHost *:80># ServerAdmin alias@example.com DocumentRoot "F:/HTDOCS" ServerName w3host.com# ErrorLog "logs/www.w3host.com-error_log"# TransferLog "logs/localhost-access_log"</VirtualHost><VirtualHost *:80># ServerAdmin alias@.example.com DocumentRoot "F:/HTDOCS/subdomain" ServerName subdomain.w3host.com</VirtualHost>
    We need to setup the Windows environment variable OPENSSL_CONF ...

    Open Control Panel\System and Security\System\Advanced System Settings choose Environment Variables
    and under System Variables set the correct value to the openssl.cnf file, so for example:
    as Variable value set OPENSSL_CONF
    as Value set something like:
    C:\Apache2.4\conf\openssl.cnf
    or C:\Program Files (x86)\Apache Software Foundation\Apache2.4\conf\openssl.cnf
    Check that there is not already present a Variable named OPENSSL_CONF maybe due to previous install: in case edit value to correct path only.
    (I had to restart win to get effectively loaded as changed the OPENSSL_CONF value after edited and saved it. I have read somewhere that should not be necessary: i do not know, on my test, i had to restart win. Maybe you have not to restart, or you know how to refresh win, loading new or changed environment vars, without restarting).

    now from promt as admin, on bin folder of Apache install folder, execute:
    openssl req -new -out server.csr

    It will ask you some questions and you can safely ignore them and just answer the following questions:
    PEM pass phrase: Password associated with the private key you’re generating (anything of your choice).
    Common Name: The fully-qualified domain name associated with this certificate (i.e. http://www.domain.com).

    NOTE about Common Name: maybe you would like to setup an unique .crt and .key for subdomains, so, enter *.domain.com (for my test i've give *.w3host.com) as Common Name value.

    Now we need to remove the passphrase from the private key. The file "server.key" created from the following command should be only readable by the apache server and the administrator. You should also delete the .rnd file because it contains the entropy information for creating the key and could be used for cryptographic attacks against your private key.

    openssl rsa -in privkey.pem -out server.key

    Now we need to set up an expiry date, it could be any time of your choice, we use 365 days below:

    openssl x509 -in server.csr -out server.crt -req -signkey server.key -days 365

    We have the Self-signed SSL certificates ready now on apache bin folder. Now we need to MOVE the "server.csr", "server.crt" and "server.key" files to the
    "C:\Apache2.4\conf" location

    or to the folder where the SSLCertificateFile directive point to, into file
    /conf/extra/httpd-ssl.conf

    Now configure Apache to run SSL/HTTPS server:

    Now that we have the Self-signed SSL certificate ready, all we need is to configure Apache to start the SSL server.

    First we modify the "C:\Apache2.4\conf\httpd.conf" file.

    Open up conf\httpd.conf in a text editor and look for these three lines:

    LoadModule ssl_module modules/mod_ssl.so and remove pound sign (#) character preceding it.
    LoadModule socache_shmcb_module modules/mod_socache_shmcb.so and remove pound sign (#) character preceding it.

    Include conf/extra/httpd-ssl.conf and remove pound sign (#) character preceding it.

    Now we need to modify the "C:\Apache2.4\conf\extra\httpd-ssl.conf". Let all the default options as it is but make sure to modify the following section according to your need:

    <VirtualHost _default_:443>
    ServerAdmin some@email.com
    DocumentRoot "Your Root folder location"
    ServerName http://www.domain.com:443
    ServerAlias domain.com:443
    #ErrorLog "logs/anyFile-error.log"
    #CustomLog "logs/anyFile-access.log" common
    SSLEngine on
    ..... .....
    .....
    SSLCertificateFile "C:\Apache2.4\conf\server.crt"
    ..... .....
    .....
    SSLCertificateKeyFile "C:\Apache2.4\conf\server.key"
    </VirtualHost>

    Make sure that "SSLCertificateFile" and "SSLCertificateKeyFile" are properly located.

    search for line:
    SSLPassPhraseDialog builtin
    change into:
    #SSLPassPhraseDialog builtin

    may, may not, search also for line
    SSLCertificateChainFile "${SRVROOT}/conf/server-ca.crt"
    comment out:
    #SSLCertificateChainFile "${SRVROOT}/conf/server-ca.crt"

    restart Apache

    Statistics: Posted by axew3 — Sun Apr 04, 2021 5:18 pm — Replies 0 — Views 27


News from engadget.com

Latest 5 news from – engadget.com/rss.xml – target _blank – inline styled, used like this:

Shorcode: RSS feeds into WordPress

WP_w3all phpBB WordPress 1.9.7 >

WP_w3all feed version 1.0

check all others shortcodes listed under the “common how” to section

Note that substantially this shortcode can substitute with easy all others old phpBB last topics shortcodes. It can retrieve any kind of posts/topics list and display as more like using style/classes or inline style. Follow read more below …

Note: this shortcode work ok also if a valid path to a phpBB config.php file has not been setup and the plugin result as not activated (RED text) on plugin admin page

Note also that this shortcode as it is coded, like the related WP hook, caches results for 12 hours by default

Look two raw examples

As basic default the shortcode feeds, that can point to a phpBB generated feed OR to any other valid feed resource, need to be used like this:

The example of feed to retrieve is here for phpBB, but it’s possible to use any valid feed URL to display feeds from any resource. Check some feed example to grab here http://simplepie.org/demo/ or any other you want and use into the shortcode like this:

here as example the w3feed_items_num attribute limit to 10 items to retrieve and display from the RSS source:

To display phpBB posts feeds styled, there are some more attribute that is possible to use except the default 2 above explained:

using all together, look this example, that not contain the w3feed_text_words attribute, in which, one possible value to use, is may reserved (may not) to phpBB news/last post RSS, and explained separately more below:

the attribute w3feed_ul_class=”myexampleClassXUL” will assign class name myexampleClassXUL to the wrapper element ul. w3feed_li_class do the same for nested li assigning myexampleClassXLI to all li elements of this feed.

adding w3feed_href_blank=”1″ will cause that links elements <a> that point to topics or links to authors will include/output with the html attribute target=”_blank”

w3feed_inline_style attribute can be used to inject inline style into each li element. Note that by the way it has been tested without using special chars on it, so that special characters may need to be properly escaped to be used in this case.

It’s possible to assign different classes and display each shortcode feeds output, ul and li elements, styled as it need to be or/and as more like.

Here you can see examples for phpBB to retrieve feeds: forums news, all forums, single forum, single topic and more, plus advanced features:

https://www.phpbb.com/support/docs/en/3.1/kb/article/faq-phpbb-atom-feeds/

The w3feed_text_words=”numOfWords” attribute is may reserved to be used only for phpBB posts feeds, while the 0 (zero) and content values are ok to be used on any other feed, not only phpBB:

0 | num of words | content

if omitted w3feed_text_words=”content” is the default behavior/result, that will return all the content of the post or feed item, changing nothing on output.

while adding an integer value, as example 30, so, w3feed_text_words=”30″ will cause that firsts 30 post’s words will display, and the default Statistics: phpBB text on output removed, while will be maintained all the rest, and the result will be something like:

Post Title
Post Content
Posted by axew3 — Sat Mar 09, 2019 12:04 am

w3feed_text_words=”numOfWords” int value can may also be used for any feed and not only for phpBB posts, but check before that the result is what you expect to be.

Using 0 (zero), so w3feed_text_words=”0″ , will cause that only topic’s titles links will display.

Except the mandatory w3feed_url attribute, any of the attributes can be mixed, applied or not applied, on each shortcode feed.

WordPress phpBB
mChat integration

This procedure assume you installed the wp_w3all WordPress phpBB integration plugin (in linked or not linked users mode) into WordPress, and phpBB mChat into your phpBB. At date of this post, the code as is can be applied by anyone, but this is a raw procedure may easy to be changed by advanced users. Work fine, but to optimize at best for your site, you may have to change something on the little javascript code you’ll add as explained on install steps. You can see the concept and code to apply available here:

WordPress phpBB mChat w3all procedure

See live raw working examples here:

WordPress phpBB mChat integration example

Just a good point to start from, that can be easily improved under any aspect and to fit any needs. Will be upgraded along the time.

phpBB WordPress template integration (iframe v3)

v3 version (for cool people) old v2 version is here

NOTE THAT THIS CODE IS SUITABLE UNTIL 1.9.8 or <

Cool people are actually using version 4:

phpBB WordPress template integration (iframe v4)

THIS IS OLD CODE! REFER TO V4 IFRAME CODE FOR WP_W3ALL 1.9.9 OR >

phpBB WordPress template integration (iframe v4)

PAGE HELP – JS code – UPDATED on 24 Feb 2019
(related views/page-forum.phpupdated on 3 Gen 2019)

/trunk/addons/page-forum.php

phpBB SEO mods compatible

wp_w3all plugin 1.9.4 >

(READ ALL this page)

wp_w3all responsive iframe procedure v3

After you built/create the WP forum template page via option
WP_w3all phpBB embedded on WordPress Template
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 (then you’ll have into your active WordPress template folder a file named page-forum.php or page-board.php etc), to complete the procedure and get the responsive iframe height for the embedded/iframed 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 rows numbers on copied code):

after you pasted this code into phpBB overall_footer.html
edit following lines:

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

change value
https://www.axew3.com/w3/forum
on this line, to point to the URL of the WordPress created/named forum page (do not add final slash and change http or https as needed)
MANDATORY!

Finally, check this line

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
wp/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. Leave as is at moment, especially if you follow adding also the code on overall_header.html (more below) to redirect any phpBB direct URL to the iframed WP page: then after tested that all work fine, may return to ACP, and reset to NO and save. This step is needed 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.

Notification email links to point to iframe: follow read more below for the pure Javascript solution. Refer to v2 or v1 code for htaccess or js solution editing phpBB notifications files.

The new V3 w3all iframe code do not use anymore htaccess to force redirect as on V1 code, and substantially not rewrite URLs forcing redirect to iframe, but use pure Javascript (reload) code, that as you may imagine, lead to some different result: you’ll not have to edit phpBB notification links on phpBB notification files as on V1 or V2 code, to force users redirect to iframe when they click on notification email link. But in this case, any user except bots, will be redirected (as code is, but it can be easily changed to assume different behaviors, may excluding admins or moderators etc) to the WP iframed page, if the forum accessed via real phpBB url.

To apply same smooth scroll effect as it is on this online example, after finished with this procedure, follow with this steps:

Smooth scroll for phpBB WordPress template integration (iframe v3)



If you want phpBB email notification links or any phpBB direct url to be redirected to wp iframed forum page using pure javascript, follow this step:

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

and just immediately after this code (or by the way, before the closing tag </head>)

add the following code:

On added code, change URL on the line where (line 3):

to fit/point to the WordPress iframed forum page: DO NOT ADD final slash and setup as http or https as needed.

NOTE: if you added the code above into phpBB overall_header.html then you’ll need to remove or comment out this part by the code you added into the overall_footer.html:

Recompile phpBB template and reset to no the option when changes applied

whenever you want: to get the iframe responsive for ACP phpBB admin panel, read this post. My (personal) suggestion is to stop here and try to use the integration leaving ACP out of iframe joke. If by the way you want to follow, before to apply then you’ll have to little change the above code for overall_footer.html and overall_header.html in this way:

on code for overall_footer.html remove this part:

on code for overall_header.html remove this part:

change into:

phpBB WordPress template integration (iframe v2)

See  NEW v3 phpBB WordPress template integration code

v2 version (OBSOLETE)

See  NEW v3 phpBB WordPress template integration code

PAGE HELP and JS code – UPDATED on 21 Dec 2018
(related views/page-forum.phpupdated on 26 Sep 2018)

you need to use this version of page-forum.php for this javascript code:
/tags/1.9.3/addons/page-forum.php

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 (then you’ll have into your active WordPress template folder a file named page-forum.php or page-board.php etc), to complete the procedure and get the responsive iframe height for the embedded/iframed 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 following lines:

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

change value
https://www.axew3.com/w3/forum
on this line, to point to the URL of the WordPress created forum page
(do not add final slash and change http or https as needed)
MANDATORY!

Finally, check this line

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
wp/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.

How to update to latest iframe js code and page-forum.php?

Update the plugin (or download plugin and copy files by /resizer folder)
so files inside folder
/wp-content/plugins/wp-w3all-phpbb-integration/addons/resizer
results updated (or do it manually substituting these files with latest released https://github.com/davidjbradshaw/iframe-resizer)
so substitute/replace the file you added into phpBB root folder with latest iframeResizer.contentWindow.min.js
copy it from
/wp-content/plugins/wp-w3all-phpbb-integration/addons/resizer
folder and replace in phpBB root folder.

Replace the old code added into phpBB overall_footer.html file with the new one above into this page, take care to setup on it needed values as now  required.

Remember to rebuild phpBB template after these steps to let changes take effect.

Now rebuild the page forum in WP w3all admin page, or manually copy the new page-forum.php version contained on folder
/wp-content/plugins/wp-w3all-phpbb-integration/addons
and paste it into your WordPress template folder, renaming it as needed, so for example page-board.php if you setted up board for the forum page name on wp_w3all admin page.

Done.

Note: if you want a custom page-forum, just open the page-forum.php (or whatever you named it) and read inline hints inside. It is so easy to create a custom page forum (for example with two columns etc). If any help more. just post on help forums here at axew3.com or at wordpress.org.



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.

Transfer phpBB users into WordPress or WordPress users into phpBB

If you want to use the phpBB WordPress integration plugin just to transfer users between WordPress and phpBB or phpBB to WordPress, follow instructions on this help page:

WordPress phpBB integration without linking users