phpBB WordPress template integration (iframe v2)

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

Iframe resizer library by:
https://github.com/davidjbradshaw/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 (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):

<script type="text/javascript">
	
document.domain = 'axew3.com'; // THIS IS MANDATORY! Set/Change this value to your domain (example: axew3.com (or leave localhost if on localhost)) 
var wordpress_url_page_forum = 'https://www.axew3.com/w3/forum'; // MANDATORY! (DO NOT INCLUDE final slash here) Url that point to your wordpress forum page (without final slash)

var w3all_doc_domain = document.domain;
 
  $(document).on("click", "a", function() {
   var href = $(this).attr("href");
  $(this).attr("href", href.replace('iframe=true&', '')); // remove! or get loop in htaccess if var appended before ...
   var w3allappend = href;
   var w3all_parent_element_id = $(this).parent().get( 0 ).id; // detect click x ... (ex: return ID smiley-box, onclick post smiles) ... // detect and avoid/allow certain behaviors
   var w3all_onclick_smile  = (w3all_parent_element_id.indexOf('smiley-box') > -1);
   var w3all_onview_topic  = (href.indexOf('viewtopic.php') > -1);
   var w3all_onview_attach  = (href.indexOf('file.php') > -1);
   var w3all_onreview_post = /#[review]+/ig.exec(href);
   var w3all_onview_post = /#p[0-9]+/ig.exec(href);
   var w3all_ck_quickmod  = (href.indexOf('quickmod') > -1);
   var w3all_onreply_topic  = (href.indexOf('mode=reply') > -1);
   var w3all_ck_onindex  = (href.indexOf('index.php') > -1);
   var w3all_onsubmit_post = /^post?/ig.exec(href);
   var shortfaq = /^#[a-z][a-z0-9]+$/ig.exec(href);
   var shortinp = /^#[a-z][0-9]+$/ig.exec(href);
   var app = '';
   
if ( w3all_onclick_smile == false && w3all_onview_attach == false && w3all_onreview_post == null && shortfaq == null  && shortinp == null ) {
   if ('parentIFrame' in window) window.parentIFrame.scrollTo(0,50); // change 50 to another value may 0 or 100 or 500. Top distance gap in px when page scroll top

 if ( w3allappend.charAt(0) != '.' && w3allappend.charAt(1) != '/' ){
  app = href.split('app.php');
	w3allappend = './app.php' + app[1];
}

var newPath = /^.+(\.\/.+)/ig.exec(w3allappend); // remove ../.././ from passed path, it need to be ./
if(newPath != null){
		w3allappend = newPath[1];
	}
	
// check if link point to external resource	
if (/^(f|ht)tps?:\/\//i.test(href)){
	parent.location.replace(href);
	return;
} else {
   w3allappend = window.btoa(unescape(encodeURIComponent(w3allappend)));
  }
 if ('parentIFrame' in window) window.parentIFrame.sendMessage(w3allappend);
}
});
 
///////////////////////////////////////////////////////////////////////////
// w3all Ajax UPDATES for phpBB events
 
if (window.frameElement) { // if in iframe 
 
window.onload = function() {
var pmn = "{PRIVATE_MESSAGE_COUNT}";
var w3all_phpbb_u_logged = "{S_USER_LOGGED_IN}";
// to send to wp at once here, like this: #w3all_phpbbpmcount=val#w3all_phpbbnotifycount=val#etc etc etc
var w3appendevents = '#w3all_phpbbpmcount=' + pmn + '#w3all_phpbb_u_logged=' + w3all_phpbb_u_logged;
parent.w3all_ajaxup_from_phpbb(w3appendevents);
}
 
// fix vertical iframe centered on viewtopic.php, preview or where # anchor etc
// skip iOS
var w3iOS = !!navigator.platform && /iPad|iPhone|iPod/.test(navigator.platform);
if(w3iOS == false){
$(window).load(function() {
var bd = document.getElementsByTagName("body");
for (var i = 0; i < bd.length; i++) { 
    var bdID = bd[i].getAttribute("id"); 
}
var elt = document.getElementById(bdID);	
elt.setAttribute("style", "position:fixed;top:0%;left:0%;width:100%;margin:0px;");
});
}

// htaccess isn't needed anymore 
$( "a" ).contextmenu(function() {
  var href = $(this).attr("href");
  var ohref = href;
  var applink = /app\.php[\w\/]+/ig.exec(href);
	var ckext = /^(f|ht)tps?:\/\//i.test(href); // external resource url?
	var ffile = '';
	var shortinp = /^#[a-z][0-9]+$/ig.exec(href);
	var shortfaq = /^#[a-z][a-z0-9]+$/ig.exec(href);
	var hrefu = document.location.href;
if ( href.charAt(0) == '.' && href.charAt(1) == '/' ){
	ffile = ohref;
} else {
  pu = href.split('app.php');
	ffile = './app.php' + pu[1];
}

if( shortinp != null ){
	 ffile = './' + hrefu.split('\\').pop().split('/').pop();
 }
 
 if( shortfaq != null && href.charAt(1) != 'p'){
 	pu = hrefu.split('app.php');
	ffile = './app.php' + pu[1] + shortfaq;
 }
 
var d = ffile;	 
if( href.length < 2 ){ // #
  d = document.location.href;
 }

  hrefEnc = window.btoa(unescape(encodeURIComponent(d)));
  href1 =  wordpress_url_page_forum + '/?w3=' + hrefEnc;
     
 if( ckext != false ){ // external Url
 	href1 = ohref;
 }
      
  $(this).attr("href", href1); // send out encoded
  $(this).mouseout(function() { // reset
  $(this).attr("href", ohref);
});

});

} // END if (window.frameElement) {
</script>
<script type="text/javascript" src="https://www.axew3.com/w3/forums/iframeResizer.contentWindow.min.js" defer></script>

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

document.domain = 'axew3.com'; // THIS IS MANDATORY! Set/Change this value to your domain (example: axew3.com (or leave localhost if on localhost))

var wordpress_url_page_forum = 'https://www.axew3.com/w3/forum'; // MANDATORY! (DO NOT INCLUDE final slash here) Url that point to your wordpress forum page (without final slash)

var w3all_doc_domain = document.domain;

$(document).on("click", "a", function() {

var href = $(this).attr("href");

$(this).attr("href", href.replace('iframe=true&', '')); // remove! or get loop in htaccess if var appended before ...

var w3allappend = href;

var w3all_parent_element_id = $(this).parent().get( 0 ).id; // detect click x ... (ex: return ID smiley-box, onclick post smiles) ... // detect and avoid/allow certain behaviors

var w3all_onclick_smile = (w3all_parent_element_id.indexOf('smiley-box') > -1);

var w3all_onview_topic = (href.indexOf('viewtopic.php') > -1);

var w3all_onview_attach = (href.indexOf('file.php') > -1);

var w3all_onreview_post = /#[review]+/ig.exec(href);

var w3all_onview_post = /#p[0-9]+/ig.exec(href);

var w3all_ck_quickmod = (href.indexOf('quickmod') > -1);

var w3all_onreply_topic = (href.indexOf('mode=reply') > -1);

var w3all_ck_onindex = (href.indexOf('index.php') > -1);

var w3all_onsubmit_post = /^post?/ig.exec(href);

var shortfaq = /^#[a-z][a-z0-9]+$/ig.exec(href);

var shortinp = /^#[a-z][0-9]+$/ig.exec(href);

var app = '';

if ( w3all_onclick_smile == false && w3all_onview_attach == false && w3all_onreview_post == null && shortfaq == null && shortinp == null ) {

if ('parentIFrame' in window) window.parentIFrame.scrollTo(0,50); // change 50 to another value may 0 or 100 or 500. Top distance gap in px when page scroll top

if ( w3allappend.charAt(0) != '.' && w3allappend.charAt(1) != '/' ){

app = href.split('app.php');

w3allappend = './app.php' + app[1];

}

var newPath = /^.+(\.\/.+)/ig.exec(w3allappend); // remove ../.././ from passed path, it need to be ./

if(newPath != null){

w3allappend = newPath[1];

}

// check if link point to external resource

if (/^(f|ht)tps?:\/\//i.test(href)){

parent.location.replace(href);

return;

} else {

w3allappend = window.btoa(unescape(encodeURIComponent(w3allappend)));

}

if ('parentIFrame' in window) window.parentIFrame.sendMessage(w3allappend);

}

});

///////////////////////////////////////////////////////////////////////////

// w3all Ajax UPDATES for phpBB events

if (window.frameElement) { // if in iframe

window.onload = function() {

var pmn = "{PRIVATE_MESSAGE_COUNT}";

var w3all_phpbb_u_logged = "{S_USER_LOGGED_IN}";

// to send to wp at once here, like this: #w3all_phpbbpmcount=val#w3all_phpbbnotifycount=val#etc etc etc

var w3appendevents = '#w3all_phpbbpmcount=' + pmn + '#w3all_phpbb_u_logged=' + w3all_phpbb_u_logged;

parent.w3all_ajaxup_from_phpbb(w3appendevents);

}

// fix vertical iframe centered on viewtopic.php, preview or where # anchor etc

// skip iOS

var w3iOS = !!navigator.platform && /iPad|iPhone|iPod/.test(navigator.platform);

if(w3iOS == false){

$(window).load(function() {

var bd = document.getElementsByTagName("body");

for (var i = 0; i < bd.length; i++) {

var bdID = bd[i].getAttribute("id");

}

var elt = document.getElementById(bdID);

elt.setAttribute("style", "position:fixed;top:0%;left:0%;width:100%;margin:0px;");

});

}

// htaccess isn't needed anymore

$( "a" ).contextmenu(function() {

var href = $(this).attr("href");

var ohref = href;

var applink = /app\.php[\w\/]+/ig.exec(href);

var ckext = /^(f|ht)tps?:\/\//i.test(href); // external resource url?

var ffile = '';

var shortinp = /^#[a-z][0-9]+$/ig.exec(href);

var shortfaq = /^#[a-z][a-z0-9]+$/ig.exec(href);

var hrefu = document.location.href;

if ( href.charAt(0) == '.' && href.charAt(1) == '/' ){

ffile = ohref;

} else {

pu = href.split('app.php');

ffile = './app.php' + pu[1];

}

if( shortinp != null ){

ffile = './' + hrefu.split('\\').pop().split('/').pop();

}

if( shortfaq != null && href.charAt(1) != 'p'){

pu = hrefu.split('app.php');

ffile = './app.php' + pu[1] + shortfaq;

}

var d = ffile;

if( href.length < 2 ){ // #

d = document.location.href;

}

hrefEnc = window.btoa(unescape(encodeURIComponent(d)));

href1 = wordpress_url_page_forum + '/?w3=' + hrefEnc;

if( ckext != false ){ // external Url

href1 = ohref;

}

$(this).attr("href", href1); // send out encoded

$(this).mouseout(function() { // reset

$(this).attr("href", ohref);

});

} // END if (window.frameElement) {

</script>

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

document.domain = 'axew3.com'; // THIS IS MANDATORY! Set/Change this value to your domain (example: axew3.com (or set localhost if on localhost))

1	document.domain = 'axew3.com'; // THIS IS MANDATORY! Set/Change this value to your domain (example: axew3.com (or set localhost if on localhost))

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:

var wordpress_url_page_forum = 'https://www.axew3.com/w3/forum'; // MANDATORY! (DO NOT INCLUDE final slash here) Url that point to your wordpress forum page (without final slash)

1	var wordpress_url_page_forum = 'https://www.axew3.com/w3/forum'; // MANDATORY! (DO NOT INCLUDE final slash here) Url that point to your wordpress forum page (without final slash)

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

<script type="text/javascript" src="https://www.axew3.com/phpBB/iframeResizer.contentWindow.min.js" defer></script>

1	<script type="text/javascript" src="https://www.axew3.com/phpBB/iframeResizer.contentWindow.min.js" defer></script>

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

src="https://www.yoursite.com/your-phpbb-folder/iframeResizer.contentWindow.min.js"

1	src="https://www.yoursite.com/your-phpbb-folder/iframeResizer.contentWindow.min.js"

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.

If any question, use the forum here or at wordpress.org wp-w3all-phpBB

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

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.

You could use the plugin in this way just to transfer/migrate users between phpBB and WordPress or viceversa.

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

//define('WPW3ALL_NOT_ULINKED', true);

1	//define('WPW3ALL_NOT_ULINKED', true);

change into

define('WPW3ALL_NOT_ULINKED', true);

1	define('WPW3ALL_NOT_ULINKED', true);

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

Now 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.

WordPress Shortcode: last phpBB topics/posts into WP post

WP_w3all 1.7.5 or >

Vers. 1.0

WordPress phpBB Latest phpBB Topics shortcode how to

To add a WP_w3all shortcode, and display a list of Latest updated phpBB Topics into a WordPress post/page, the WordPress shortcode to use is like this:

[w3allastopics topics_number="5"]

1	[w3allastopics topics_number="5"]

change the topics_number value 5 with the number of Last phpBB topics/posts you need to retrieve and display.

To display with post text, use the shortcode in this way:

[w3allastopics topics_number="5" post_text="1" text_words="30"]

1	[w3allastopics topics_number="5" post_text="1" text_words="30"]

change the text_words value 30 based on how many words you want to display for listed posts.

This feature will use the same settings you have choose for avatars in WP_w3all config page.

Note: in case you want to add custom style the output of Last Topics/post shortcode, the file used by the Last Topics/post shortcode you need to look for, may to add custom modifications is:

wp-content/plugins/wp-w3all-phpbb-integration/views/phpbb_last_topics_output_shortcode.php

that is not the same used to output phpBB Last Topics on widgets, which is instead the file phpbb_last_topics.php (as you’ll see on same folder).

How to activate shortcode into WordPress Posts Replies or Widgets or even Excerpt?

About the above, consider the fact that if shortcode is activated in this way on comments, the shortcode (any, not only the WP_w3all shortcode) can be used by any commenting user on comments, if a plugin not provide explicitly the feature to disable on comments the shortcode for all users except specifics groups.

WordPress and Buddypress phpBB profile fields integration

NOTE x Buddypress profile fields integration: IT IS MANDATORY that the User Groups option on
WP admin -> Settings -> Buddypress
is active option!
NOTE x Buddypress: phpBB 3.2 or > required.

Note: Buddypress avatar integration option work in another way by others profile fields (more below explained) so is possible to activate the Buddypress avatar integration option without activating the Buddypress profile fields integration option.

How the WordPress + phpBB or WordPress + phpBB + Buddypress profile fields integration work:

On WordPress + Buddypress, it’s required that default phpBB profile fields exists as they are into a default phpBB install, while in the case of WordPress default without Buddypress it is not required: if phpBB profile fields mismatch from default, no update will be executed, EXCEPT for email and password fields (updated in any case). By the way, into a default WordPress there is only another field of interest on user’s profile, that’s site URL.

Remember that in the case phpBB profile fields aren’t the same like into a default phpBB install, no update will be done on phpBB profile fields (EXCEPT for email and password) when profile update will be executed in WordPress side.

The how to resolve and check about this, can be done reading this post:
WP_w3all phpBB integration and phpBB PROFILE FIELDS

The following is ONLY if Buddypress installed in WordPress and Buddypress integration option activated:

If on Buddypress, the WP_w3all feature about integration of Profile Fields can be activated on WP_w3all config.
If you choose to activate this option, check that phpBB profiles fields matches a phpBB default install configuration ( WP_w3all phpBB integration and phpBB PROFILE FIELDS ), so will be also necessary to name these fields in Buddypress as explained in this procedure:

any custom field can be added into Buddypress, but only default phpBB default profile fields are synchronized and updated between phpBB and WP Buddypress, and only if these Profile Fields in Buddypress are named as explained here below. You can add any profile field in Buddypress. But only these that match phpBB as explained below are synchronized/updated.
To have Buddypress integrated about profile fields and synchronized with phpBB profile fields, phpBB profile fields need to be AS are ON A DEFAULT phpBB installation (as the code is), plus it is required to name these Profile Fields Names in Buddypress in this way:

Buddypress and phpBB default fields integration how to

In Buddypress, is possible to name any field as more like, but if it need to be updated also in phpBB and vice versa, the field name shown to the user, need to contain:

for youtube, the word youtube (lower or capital or both mixed letters, also into a phrase)
for facebook, the word facebook (lower or capital or both mixed letters, also into a phrase)
for icq, the word icq (lower or capital or both mixed letters, also into a phrase)
for skype, the word skype (lower or capital or both mixed letters, also into a phrase)
for twitter, the word twitter (lower or capital or both mixed letters, also into a phrase)
for googleplus, the word google (lower or capital or both mixed letters, into a phrase also (just google, so it can be used for any google service, and not just googleplus: so for gmail may could be used Google gmail))
for yahoo, the word yahoo (lower or capital or both mixed letters, also into a phrase)
for aol, the word aol (lower or capital or both mixed letters, also into a phrase)

So it is important to not repeat these words using as Profile Fields Names on Buddypress some word that is already used to detect another field name (or one of the others 4 fields below).

This can work very fine until the name of the field is about services, because normally these are named in any language the same, while remaining 4 (four) default phpBB profile fields, which are: occupation, interests, location, website can be differently named: in Italian the Eng word occupation is written occupazione, in Dutch it is bezetting etc etc.

For those 4 fields, IT IS REQUIRED that these Profile Fields Names named in Buddypress as single word, or changed to fit your language or different language or phrase or word, as explained more below.

For occupation, the word occupation, lower or capital or both mixed letters, or anyone of the words in the following array:

$w3_bpl_profile_occupation = array(
    "en" => "occupation",
    "it" => "occupazione",
    "fr" => "occupation",
    "de" => "occupation",
    "nl" => "bezetting",
    "es" => "ocupacion"
);

$w3_bpl_profile_occupation = array(

"en" => "occupation",

"it" => "occupazione",

"fr" => "occupation",

"de" => "occupation",

"nl" => "bezetting",

"es" => "ocupacion"

);

for interests, the word interests, lower or capital or both mixed letters, or anyone of the words in the following array:

$w3_bpl_profile_interests = array(
    "en" => "interests",
    "it" => "interessi",
    "fr" => "interets",
    "de" => "interest",
    "nl" => "belangen",
    "es" => "intereses"
);

$w3_bpl_profile_interests = array(

"en" => "interests",

"it" => "interessi",

"fr" => "interets",

"de" => "interest",

"nl" => "belangen",

"es" => "intereses"

);

for location, the word location, lower or capital or both mixed letters, or any of the words in the following array:

$w3_bpl_profile_location = array(
    "en" => "location",
    "it" => "locazione",
    "fr" => "emplacement",
    "de" => "lage",
    "nl" => "plaats",
    "es" => "location"
);

$w3_bpl_profile_location = array(

"en" => "location",

"it" => "locazione",

"fr" => "emplacement",

"de" => "lage",

"nl" => "plaats",

"es" => "location"

);

for website, the word website, lower or capital or both mixed letters, or any of the words in the following array:

$w3_bpl_profile_website = array(
    "en" => "website",
    "it" => "sito web",
    "fr" => "site web",
    "de" => "website",
    "nl" => "website",
    "es" => "sitio web"
);

$w3_bpl_profile_website = array(

"en" => "website",

"it" => "sito web",

"fr" => "site web",

"de" => "website",

"nl" => "website",

"es" => "sitio web"

);

as is easy to understand, these arrays for these four BP profile fields names, contains pairs of values:
“language” => “translated word/or phrase”

in these arrays, is possible to add any other language, OR, you can also choose to modify the translation of some of the Profile Field Names into something different, like for example:
“en” => “website”
could be changed into (use EVER lower case letters here!):
“en” => “your web space”
so as Profile Field name in Buddypress, we’ll set for the website field name:
Your Web Space OR Your web space, or any other mixed lower/capital letters, but the phrase NEED TO BE THE SAME as it is set on the related array.

These arrays can be added into the custom WP_w3all phpBB config.php file, or root phpBB config.php if you use it, so on plugin update nothing will be lost in case of custom additions or modifications, maybe due to addition of your language, or translated phrase/word change.
To do this, open your wp_w3all custom phpBB config.php file (or phpBB root config.php file if you use it) and add the follow (or what for you needed) just below all others existent code lines:

$w3_bpl_profile_occupation = array(
    "en" => "occupation",
    "it" => "occupazione",
    "fr" => "occupation",
    "de" => "occupation",
    "nl" => "bezetting",
    "es" => "ocupacion"
);

$w3_bpl_profile_location = array(
    "en" => "location",
    "it" => "locazione",
    "fr" => "emplacement",
    "de" => "lage",
    "nl" => "plaats",
    "es" => "location"
);

$w3_bpl_profile_interests = array(
    "en" => "interests",
    "it" => "interessi",
    "fr" => "interets",
    "de" => "interest",
    "nl" => "belangen",
    "es" => "intereses"
);

$w3_bpl_profile_website = array(
    "en" => "website",
    "it" => "sito web",
    "fr" => "site web",
    "de" => "website",
    "nl" => "website",
    "es" => "sitio web"
);

$w3_bpl_profile_occupation = array(

"en" => "occupation",

"it" => "occupazione",

"fr" => "occupation",

"de" => "occupation",

"nl" => "bezetting",

"es" => "ocupacion"

);

$w3_bpl_profile_location = array(

"en" => "location",

"it" => "locazione",

"fr" => "emplacement",

"de" => "lage",

"nl" => "plaats",

"es" => "location"

);

$w3_bpl_profile_interests = array(

"en" => "interests",

"it" => "interessi",

"fr" => "interets",

"de" => "interest",

"nl" => "belangen",

"es" => "intereses"

);

$w3_bpl_profile_website = array(

"en" => "website",

"it" => "sito web",

"fr" => "site web",

"de" => "website",

"nl" => "website",

"es" => "sitio web"

);

Edit any of those adding custom language for Buddypress profile fields names, that you’ll use to name the related Buddypress profile field. Memo that all added values in these arrays need to be LOWER CASE.

As example, assume we need to add for the occupation field a language like Icelandic, that translate the word occupation in starf: then we’ll go to modify the array $w3_bpl_profile_occupation adding what needed just in this way:

$w3_bpl_profile_occupation = array(
    "icelandic" => "starf",
    "en" => "occupation",
    "it" => "occupazione",
    "fr" => "occupation",
    "de" => "occupation",
    "nl" => "bezetting",
    "es" => "ocupacion"
);

$w3_bpl_profile_occupation = array(

"icelandic" => "starf",

"en" => "occupation",

"it" => "occupazione",

"fr" => "occupation",

"de" => "occupation",

"nl" => "bezetting",

"es" => "ocupacion"

);

As you can see, it has been added to the array $w3_bpl_profile_occupation the value
“icelandic” => “starf”,

NOTE how it is not important the first value “icelandic” that could be also setup with any other word (if isn’t already used as key for another value in the same array): the important is the word starf
added as LOWER CASE, that you’ll use as Buddypress Profile Field Name you’ll dedicate to the occupation field (and that will be recognized and synchronized also in phpBB). So you can use as field name in Buddypress Starf, or StarF, or any mixed lower/capital letters. Remember for these four fields that you can name these Fields Names in Buddypress as lower or capital or both mixed letters, but exactly like the phrase or word as is the value in one of these arrays.

Synchronize Buddypress and phpBB user’s profile fields

WP_w3all 1.7.5 or >

WordPress and Buddypress phpBB profile fields integration

WordPress shortcode for comments, widgets and excerpts

The following add_filter lines of code that will activate shortcode for Posts Comments, Widgets and Excerpts in WordPress, could also be added into your theme functions.php file.

Or if you wish, you can add it on WP_w3all plugin (that allow you to show phpBB posts into WordPress) inside the wp_w3all.php file (NOTE: when plugin update you’ll lost these modifications).

Open wp_w3all.php and search for line:

add_shortcode( 'w3allforumpost', array( 'WP_w3all_phpbb', 'wp_w3all_get_phpbb_post' ) );

1	add_shortcode( 'w3allforumpost', array( 'WP_w3all_phpbb', 'wp_w3all_get_phpbb_post' ) );

immediately after, add the follow line/s, about what/where you want to activate shortcode

Activate shortcode for Posts Comments:

add_filter( 'comment_text', 'do_shortcode' );

1	add_filter( 'comment_text', 'do_shortcode' );

Activate shortcode for Widgets:

add_filter( 'widget_text', 'do_shortcode' );

1	add_filter( 'widget_text', 'do_shortcode' );

Activate shortcode for Excerpt:

add_filter( 'the_excerpt', 'do_shortcode');

1	add_filter( 'the_excerpt', 'do_shortcode');

As said above, you could instead add these “activation” code lines for shortcode in Posts Comments, Widgets or Excerpts in WordPress, into the functions.php file of your WordPress theme.

WordPress Shortcode: phpBB posts into WP post

WP_w3all 1.7.4 or >

phpBB posts – WP post shortcode how to

To add a WP_w3all shortcode, and display a phpBB post into a WordPress post, you need to choose a phpBB Post ID (note: post ID NOT Topic ID) to display, and add it into WordPress post, like this:

[w3allforumpost id="1202"]

1	[w3allforumpost id="1202"]

Change the value 1202 with the post ID you need to display.
( POST ID NOT TOPIC ID )

If you want display the post as plain text (so the bbcode will be removed from the output) use:

[w3allforumpost id="1202" plaintext="1"]

1	[w3allforumpost id="1202" plaintext="1"]

The simple bbcode parser function, display all default bbcode tags, excluded flash, attachments and email, check the list on this phpBB help page, phpBB bbcode how to
which are:

[b] [u] [i] [list] (all lists type) [size] [color] [url] [image] [code]

added: [media] bbcode parsing (video etc embed)
useful if in phpBB is installed the media embed mod.

Note: on this phpBB installation, is not installed the phpBB Media Embed mod to display media/video into phpBB posts, by the way, adding the [media] bbcode into a phpBB post like this:

[media]https://www.youtube.com/watch?v=r8NZa9wYZ_U[/media]

1	[media]https://www.youtube.com/watch?v=r8NZa9wYZ_U[/media]

in this case the [media] bbcode into the real phpBB post will not be parsed (because the Media Embed mod has not been installed in phpBB) but will be parsed into the WP post, because recognized and parsed by the WP_w3all plugin code.

It can be considered as 1.0 version, that work quite fine until bbcode tags structure is respected.

Here an example for a phpBB postID 2249
which you can see in phpBB at this link: https://www.axew3.com/w3/forums/viewtopic.php?f=13&t=566&p=2249#p2249

the shortcode used into this WP post to display the phpBB postID 2249, with bbcode formatted, will be this:

[w3allforumpost id="2249"]

1	[w3allforumpost id="2249"]

Shortcode output for post id 2249 is right here:

This is huge red text
so i want this text bold,
and after i like to display a piece of code:


<?php
function test() {
    $foo = "local variable";

    echo '$foo in global scope: ' . $GLOBALS["foo"] . "\n";
    echo '$foo in current scope: ' . $foo . "\n";
}

$foo = "Example content";
test();
?>

then i want display a big test but without colorize it:
WoW! i like it ...
and i hev some list to display:

The first possible answer
The second possible answer
The third possible answer

in different format

The first possible answer
The second possible answer
The third possible answer

and i want underline text
or quoted text:

una canzone per te

so a nice image:

then more strange bad code:

<test  />$find = array(
		 '~\[img\].*?\[/img\]~si', // if there links/text for the image elsewhere, remove. Done above
    '~(^(\r\n|\r|\n))|^\s*$~m', .........
	);

an url with text
Visit phpBB!
and an url
https://www.wordpress.org/
and more code for bbcode parsing:

// partial bbcode regex 
$find = array(
		'~\[b\](.*?)\[/b\]~usi',
		'~\[i\](.*?)\[/i\]~usi',
		'~\[u\](.*?)\[/u\]~usi',
		'~\[quote\](.*?)\[/quote\]~usi',
		'~\[size=(.*?)\](.*?)\[/size\]~usi',
	);

and an image link also:

NOTE: on this phpBB example is not installed the phpBB Media Embed mod, to display video into phpBB posts, but if i add this bbcode into this phpBB post like this:

it will not be parsed into this phpBB post, because the mod has not been installed in phpBB, but will be parsed into the WP post because recognized and parsed by the WP_w3all plugin code.

you cannot add, expecting it will be parsed: an attachment, flash or email bbcode tag.
see the result of this post parsed into a WordPress post via Shortcode here: https://www.axew3.com/w3/2017/07/wordpress-shortcode-phpbb-posts-into-wp-post/

you need a more improved version of the function that do this? email me here: me@you.us
As you see was not so important to add email parsing .... (what?)

Cheers to all cool people!

WP_w3all for WordPress MS MU (Multisite, Multiuser network installations)

To configure WP_w3all on WordPress MS MU please read all the follow:

WP_w3ll plugin from 1.7.0 – WordPress MU MS . The plugin can be also network activated, but the linked phpBB on each subsite, need to be the same (same path and same url setting value). If plugin is network activated, it is mandatory that the sub admin or super admin, setup/configure into (each) subsite the same config of the main site for the integration plugin, because if not, when an user login into a subsite where the plugin is not configured, the phpBB cookie will not be released, and when same logged user visit the main site or another subsite where the plugin run instead configured, the user will be logged out. Registered phpBB users are added as users only into the FIRST WP site (or subsite) where users will login or that they will visits while coming already logged in into phpBB. *But you could use a plugin to add coming phpBB logged users, into each or just few WordPress site/subsites they visits, see more below.

NOTE: from 1.9.0 patched at date of this post ( or from 1.9.0 > ) it is NOT more necessary to execute this step editing the wp-config.php file
but check an hint and a warning more for WP mums installations more below on this same post.

OPEN wp-config.php file:

search for line (value wp_ can be maybe different):

$table_prefix = 'wp_';

1	$table_prefix = 'wp_';

immediately after ADD:

define( 'WPW3ALL_MAIN_DBPREFIX', $table_prefix );

1	define( 'WPW3ALL_MAIN_DBPREFIX', $table_prefix );

BEWARE that if a different phpBB is linked on subsites, the integration in this state lead to unpredictable results! … in true it is very predictable what can happen, but really long to explain and too hard for my Eng! In short, it is NOT possible to link a different phpBB into WP network subsites with actual code.
Setup into sub-sites, if the plugin is network activated, same path and url in WP_w3all config, with same values of main site.

*Hint: you could use a plugin to add coming phpBB logged users, into each WordPress they visits, or just to few, and with several different features: search for Join My Multisite plugin at WordPress plugins directory.

NOTE: WP_w3all phpBB integration plugin when an user is deleted in WordPress (so it become deactivated in phpBB, and then you may go to delete this user in phpBB) also clean up from signup table in WordPress this user. This is necessary for compatibility (as the code is) with phpBB integration to avoid that another user register with same email into phpBB (if you allow users to register also on phpBB side, and you have also deleted this user also in phpBB) while the user has been deleted in WP, but his email/username remain stored into WP database signups table for some more time.

WP_w3all overall_footer.html for iframe JS/Ajax: PM on address bar and right click/copy links

Since 1.7.2, follow iframe instructions installation:

Embed phpBB into WordPress template:iframe responsive how to