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 v4)

v4 version (for cool people)

FROM 2.1.1 USE V5 code: https://www.axew3.com/w3/2020/01/phpbb-wordpress-template-integration-iframe-v5/

OLD CODE: cool people moved to V5

FROM 2.1.1 USE V5 code: https://www.axew3.com/w3/2020/01/phpbb-wordpress-template-integration-iframe-v5/

SINCE 2.1.1 the following code, even if still working with his related page-forum (linked below) into any plugin version, is now obsolete.

PAGE HELP – JS code – UPDATED on 15 Gen 2020
(related addons/page-forum.phpupdated on 14 Gen 2020)

wp-w3all-phpbb-integration/tags/2.1.0/addons/page-forum.php

wp_w3all plugin 1.9.9 until 2.1.0

phpBB SEO mods compatible – (READ ALL this page)

wp_w3all responsive iframe procedure

WordPress phpBB iframe template integration

MEMO: to update to latest v4 code, you’ll need 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 need to update also the iframeResizer.contentWindow.min.js file you added into phpBB root, with the new one you find into /wp-content/plugins/wp-w3all-phpbb-integration/addons/resizer folder. Done this, substitute the phpBB overall_header.html and overall_footer.html code (re-adding needed values) with the new v4 code here below. Do not forget to rebuild phpBB template to make phpBB template modifications take effect.

 Domain/subdomains installations it’s REQUIRED to read this: How to Domain/subdomain iframe template integration

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 localhost 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://localhost/wp53/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, 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

The new V4 w3all iframe code do not use anymore htaccess to force redirects, 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 (for example) on notification email link or some other forum’s 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.

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 just immediately after this code (or by the way, just 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.

All working!?

Reset to No the Recompile phpBB template option, here we go!

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:

P.s – 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:

* For domain/subdomain installations
READ THIS HOW TO:
How to Domain/subdomain iframe template integration

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

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

  • Integration has stopped working

    Hi

    The integration on our site has stopped working suddenly 24 hours ago. Users now can not login to the Wordpress site using their existing passwords, but can login to the forum.

    I logged in as WP admin and changed the password of one user who's details I know, and now they can login to the WP site but they have to log in separately to the forum.

    Nothing changed and this started happening suddenly.

    Any ideas please?

    Thanks
    Jon

    Statistics: Posted by thewebguys — Thu Jul 29, 2021 7:44 am — Replies 0 — Views 7


  • I'm back soon!

    Sorry guys! It has been a terrible 2021 start for me!
    Still fighting with some personal problem but all will be ok very soon.
    I will fully return back within a month or before over all things.
    In the while i will try to fix up all the reported and on queue by months now, even before, one of these days.

    It has been really hard time. Anyway the important is: i'm here again!

    Statistics: Posted by axew3 — Mon Jul 26, 2021 5:17 am — Replies 0 — Views 15


  • How to make links opened in new tab go to the right place?

    Hi. If we click a link on a topic and ask it to open in a new tabe, it always opens the forum home page. What is the right way to make sure it opens the correct thread or topic please?
    Thanks, Jon

    Statistics: Posted by thewebguys — Thu Jun 17, 2021 12:48 pm — Replies 4 — Views 228


News from engadget.com

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

  • US watchdog rejects Blue Origin’s protest of NASA lunar lander contract

    The US Government Accountability Office (GAO) has dismissed protests from Blue Origin and defense contractor Dynetics over NASA’s decision to hand out a single $2.9 billion contract to SpaceX as part of its Human Landing System program. On Friday, the watchdog said NASA’s “evaluation of all three proposals was reasonable and consistent with applicable procurement law, regulation, and the announcement’s terms.”

    When Blue Origin first challenged the lunar lander contract in April, the company claimed the selection process was “fundamentally unfair” because it didn’t get a chance to revise its bid. To that point, NASA could afford to give SpaceX the contract because the company agreed to modify its payment schedule. Blue Origin also took issue with the fact that the space agency selected a single contractor for the project when the initial announcement had called for two manufacturers to be involved.

    In reviewing NASA’s decision, the GAO says the space agency “did not violate procurement law or regulation when it decided to make only one award.” It notes NASA gave itself the flexibility to hand out a single contract, multiple awards or none at all when it first announced the Human Landing System program. 

    What’s more, the GAO concluded there “was no requirement for NASA to engage in discussions, amend, or cancel the announcement” due to the amount of funding it had available for the project. Notably, the GAO also points in its press release that its role is not to judge the relative merits of a contract decision. Both Blue Origin and Dynetics had argued that NASA chose the most “high risk option available” since SpaceX’s bid involved its Starship rocket, which at that point in the procurement process had yet to land in one piece.

    "We stand firm in our belief that there were fundamental issues with NASA’s decision, but the GAO wasn’t able to address them due to their limited jurisdiction. We’ll continue to advocate for two immediate providers as we believe it is the right solution," a spokesperson for Blue Origin said following the decision. "We’ve been encouraged by actions in Congress to add a second provider and appropriate additional resources to NASA's pursuit to return Americans to the Moon. We’re also very encouraged by Administrator Nelson’s comments over the past week that reaffirm NASA’s original intent to provide simultaneous competition. The Human Landing System program needs to have competition now instead of later — that's the best solution for NASA and the best solution for our country.”

    The decision comes mere days after Blue Origin founder and former Amazon CEO Jeff Bezos offered to waive $2 billion in payments from NASA in return for a lunar lander contract. Following Blue Origin’s protest, NASA told SpaceX to stop work on the Human Landing System while the GAO sorted out the challenge. Today's decision allows the project and the Artemis program more broadly to move forward unless Blue Origin asks the US Court of Federal Claims to examine the case. 

    Update 2:28PM ET: Added comment from Blue Origin. 

  • This toe tickling navigation system will help the visually impaired walk tall

    Following the death of a sight-impaired relative, Wataru Chino had no choice but to take action. In response to the tragedy, the Honda EV engineer developed an in-shoe navigation system, dubbed Ashirase (both the name of the product and the name of the company) that allows low-sighted people to use their feet to navigate, rather than cell phones or other visual aids. The tactile navigation system has earned the financial backing of Honda’s Ignition startup incubator program and continues to gain traction.

    The Ashirase system is two-part, consisting of the dedicated Ashirase navigation app running on the user’s smartphone and a silicone shoe insert cradling a combination motion sensor-electronic compass. Once the user programs their walking destination into the app, the shoe inserts will vibrate in various patterns and tempos — “walk forward” causes vibrations under the balls of the feet, “turn left” rubs the appropriate side of both feet and the speed at which the inserts vibrate indicate proximity to the turn or obstacle.

    The idea behind the system is to allow users to remain more aware of their surroundings while they walk, using their feet to navigate rather than repeatedly stopping to consult their smartphones or passersby for directions.

    Ashirase
    Ashirase

    Currently the insert prototypes can only be used in low top sneakers and dress shoes but Chino already has plans to expand the footwear selection. “We are thinking about [new footwear styles], and the idea is twofold at this moment,” Chino told Engadget through an interpreter. “One is to try to change, modifying the [electronic] device so that the shape can be fitted to other types of shoes.”

    “Otherwise,” he continued, “what we can do is to change the yellow parts of this device so that it fits other types of shoes” noting that the white “puck”part can be disconnected from the flexible yellow insert that sits around the wearer’s foot and houses the various vibrating navigation gyroscopes. The system has a reported week-long battery life when using the system to navigate an average of three hours a day. Initially, the insert will be offered in generic small, medium and large sizes in Japan but he plans to offer more personalized fittings once the product hits market.

    The navigation system is currently a bit limited, based on the Google Maps API rather than an HD map source, in that it will work so long as a navigation data signal is available. That means that the system may not initially work in indoor areas like malls or hotels — though hiking trails, parks and other public lands should be no problem.

    Chino and his team are reportedly looking into incorporating either a Personal Dead-reckoning (PDR) system, Wi-Fi-based positioning or IoT navigation capability to help users make their ways through indoor public spaces at a later date. The team also reportedly plans to add public transportation options to the program in the future.

    The company plans to release a beta version of the Ashirase system in Japan in October or November of this year. Users will be given free use of the insert and app for one week before being asked for feedback. Following the public beta, Ashirase executives expect the commercialized product to be ready by October 2022 and include a 2,000 - 3,000 yen ($18 - $27) monthly subscription.

    Before that can happen, however, the startup is seeking some 200 million yen in additional funding — not including the 70 million yen in equity the Ignition program already provided — in order to scale up to full production.

  • Spotify's Noteable Releases playlist showcases the songwriters behind popular music

    For the better part of its recent history, Spotify’s Discover Weekly and Release Radar playlists have been the company’s go-to way to help people discover new music. In the span of a week, it has added two additional discovery tools. The first, What’s New, is a panel that highlights new releases from your favorite artists and podcasts. The second, which the company detailed today, is a curated playlist, but one that’s aimed at those who want to know more about the music industry.

    Dubbed "Noteable Releases," the weekly playlist collects new tracks from the world’s leading producers and songwriters. Expect to see contributions from people like frequent Billie Eilish collaborator Finneas O’Connell and Ester Dean, who helped write Katy Perry’s 2010 hit “Firework.” The result is an eclectic playlist that doesn’t stick to any one genre, though pop music is represented strongly for obvious reasons.

    The introduction of Noteable Releases follows last year’s rollout of songwriter pages and is another example of the company trying to cater to the broader music industry. You’ll notice at the top of the playlist that Spotify encourages digging into a song’s credits to find out more about the people who worked on it. You can do that by tapping the three dots icon and then “show credits.”

  • Why Tesla is delaying the Semi EV until 2022

    Following its Q2 earnings call this week, Tesla representatives confirmed previous reports that its commercial EV project, Semi, will be delayed until 2022. The company cites both the ongoing global processor shortage and its own currently-limited battery production capability for the new 4680 style cells as contributing to its decision. 

    On the plus side, Tesla executives also confirmed that development of the highly-anticipated Cyber Truck continues apace. What's more,they explained that once production fully ramps up for the Model Y in the new Berlin and Texas plants, Tesla intends to launch production lines to begin the Semi line. For the full story, watch the video above, and for continuing coverage of all things Tesla, stay tuned to Engadget!

  • Samsung's 'history of electronics' animated videos seem like great sleep aids

    Samsung wants to teach you about the history of electronics, as long as you can stay awake long enough to sit through the dull lessons. Through its Innovation Museum, the company is releasing five animated videos about inventions that shaped society. If the first episode is anything to go by, they might as well be classified as sleep aids.

    The series premiere delves into the history of telecommunications, starting with Morse code and how it paved the way for more recent innovations such as smartphones, 3G, 4G and (would you believe it?) 5G. The tone and narration is Atacama Desert dry, though. Even the name of the series is melatonin-inducing: "The History of the Electronics Industry That Changed the World."

    There's no denying the importance of Morse code, including how it's helped save the lives of many who were able to send an SOS message when they were in peril. But Samsung could have presented the story in a much more interesting way. For what it's worth, the episode is educational. But, if you're going to create a video in which "some aspects have been fictionalized," at least make it fun. 

    Upcoming installments will cover John Logie Baird's TV, telephone inventor Alexander Graham Bell, James Harrison's refrigerator and William Shockley and the semiconductor. Perhaps those will be more compelling, but it's hard to imagine anyone excitedly dashing off a telegram to a friend about it.

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

WordPress phpBB integration without linking users

NOTE: from 1.9.4 > this feature become option on plugin admin page, so may it is needed further read more below only if updating from old plugin versions: update the plugin, then login plugin admin and setup as YES the new plugin option

Activate integration without linking users between WordPress and phpBB

Will not be further more necessary to edit the wp_w3all.php file each time plugin update, to set it up the integration as Not Linked Users.

It is possible to use the plugin without linking users between WordPress and phpBB. You can display Last Topics Widgets and Shortcodes to display phpBB Last Posts or Posts content into WordPress Pages/Posts. It is also possible to use the iframed WP page, to display the phpBB forum into a WordPress page (also cross domain*). Without linking users, you may can integrate also a version of phpBB prior (<) of phpBB 3.1 to display phpBB Last Topics Widgets/Shortcodes or phpBB Posts Shorcodes into WordPress.

The plugin can be used in this state also to transfer/migrate users between phpBB and WordPress or viceversa.


It is necessary to activate the plugin: setup the Path and URL setting following instructions into WP admin -> Settings -> WP_w3all config page. You do not need to follow any other further instruction about cookie setup and/or phpBB ACP settings in this case. So after plugin has been activated, by setting Path to a valid phpBB config.php file and URL setting, you can use Widgets Last Topics Posts and use Shortcodes into WP pages and posts, to display phpBB contents or to use the users transfers options in this state. The URL setting if the plugin is merely used to transfer users, is not needed. Just setup the path to a valid phpBB config.php file.

Hint Note*: without linking users between phpBB and WordPress, it is also possible to use the plugin for cross domains installations (not only domain and subdomain). Just create a valid custom phpBB config.php file, as suggested into Wp admin -> WP_w3all config page, and use it.

NOTE: from 1.9.4 this feature has become option, so if updating from old plugin versions, just update the plugin, and repeat the above predure last time: then login plugin admin and setup the new option

Activate integration without linking users between WordPress and phpBB: The Old Way

OBSOLETE step OR to update from old versions prior 1.9.4:

To install WP_w3all integration without linking users, follow these steps:
Install the plugin

open with text editor the file:
/wp-content/plugins/wp-w3all-phpbb-integration/wp_w3all.php
+- on top of the file, search for this line

if on 1.9.4 > and updating you’ll find this instead:

change into

save/replace the edited wp_w3all.php file into plugin folder.