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 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:


[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!

    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)
    search for:


    $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:


          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



    change into:


      $phpbbUAVA = '';  $countn++;

    or download the ready and updated file on repo:

    https://plugins.trac.wordpress.org/expo ... topics.php
    and substitute it into folder:

    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:


    # 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:
    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

    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"

    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:

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


Cool people are actually using version 4:

phpBB WordPress template integration (iframe v4)


phpBB WordPress template integration (iframe v4)

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


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

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
that is contained inside folder

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:

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 by defaults, 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, even if you activate this option, 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, you can activate the WP_w3all option Buddypress Profile Fields integration.
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:

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

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

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

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.

Since 2.4.0 > the file to edit is:


So using custom files config into plugin admin, it will be:


then during plugin update, edited arrays (if they have been edited) will not be overwritten. Follow read here below to understand how to edit those arrays to match your needs

Until 2.3.9 <

Arrays can be added/edited into the custom WP_w3all phpBB config.php file, or root phpBB config.php

Arrays can be added/edited 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:

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:

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.

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

Configure WP_w3all on WordPress MS MU

WP_w3all plugin from 2.0.2 – 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 the 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. Users that register in phpBB (if you allow this in phpBB) 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.

OPEN wp-config.php file:

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

immediately after ADD:

BEWARE that it is NOT possible to link different phpBB installations on same installation network, 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 the 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 may also deleted this user in phpBB) while the user has been deleted in WP, but his email/username still stored into WP database signups table.

How are users identified when you add/transfer existent user
integration of same username/email users

Problem: i have WordPress users and I have phpbb users, they have different usernames but the same email addresses.


user A into phpBB with email C
user B into WP with email C

user A into phpBB come to try to login WP: NOT added can’t login WP side.

If you use the transfer process of WP users into phpBB:

user A Same above.
user B transferred into phpBB, B now can login into both phpBB and WP.
You’ll have two users into phpBB with same email, which is possible as option into phpBB.

You can also merge posts/users into one user in this way:

Change email to the user B in WP.
Login with the phpBB user A into WP, that will be added, as no same email found.
Now delete user B in WP, and retain posts assigning to A.

Result: an unique user, with all his posts on both phpBB and WP.

NOTE: This is just to give an idea on how to resolve common problems about an integration with pre existent users in phpBB that may have same email. But there are several more possibilities: in phpBB ACP there are many options to manage users and posts, and combining these and from the above, you should get the way to resolve any possible scenario.

Based on this topic: How are users identified? (when adding/transfer existent users)


WPD – w3all
WordPress Dropbox integration

WPD w3all WordPress plugin for Dropbox, to display and manage shared Dropbox user’s files into WordPress user’s pages.

Display shared Dropbox files, into WordPress user’s pages.
Choose between Full Dropbox App or Folder App.
Ajax images gallery.
Choose which WP groups can use the Dropbox in WordPress.
Limit files in sharing to retrieve and display in WordPress.
Data cache.
Template embed into any WordPress with an easy how to included.
Users can manage their files within WordPress, delete/create folders, link, unlink files and folders, upload and create/link files and folders.

Any other feature on request.

The Dropbox plugin has been installed also here at axew3.com, and activated for an user named axew3:

Display into WordPress, images from Dropbox, by coping the link of it on WordPress Dropbox user page, and by clicking on WP button
Add Media -> Insert from Url and just paste the URL.

w3tasks dropbox wordpress integration
w3tasks sample logo

Or files just adding pure URL:

Ask for it at https://plugins.w3tasks.com/wp/

If you like to test the user files manager, which is feature available for each user on his own WordPress Dropbox page, please register into this site, or at plugins.w3tasks.com, and send a request by using the contact page.