www programming

The file
/wp-content/plugins/wp-w3all-phpbb-integration/views/wp_w3all_phpbb_unotifications_short.php
https://plugins.trac.wordpress.org/expo ... _short.php
at date of this post, has been updated to fix all remaining bugs and to add latest lacking
type.forum
type.disapprove_topic
type.disapprove_post
cases, that were the last remaining to be added.
You can download the file by clicking the link above and replace it into the /wp-content/plugins/wp-w3all-phpbb-integration/views/ folder if you do not want to wait until 2.6.9 release.

All default phpBB notifications types that can be expected to be retrieved:
type.post_in_queue
type.approve_post
type.pm
type.topic
type.group_request
type.approve_topic
type.quote
type.bookmark
type.post
type.admin_activate_user
type.group_request_approved
type.report_pm
type.report_post_closed
type.disapprove_post
type.disapprove_topic
type.forum

See phpBB user's notifications shortcode page
https://www.axew3.com/w3/2022/10/phpbb- ... wordpress/

the $w3all_phpbb_unotifications global var will be initialized as array into wp_w3all.php, so that when used count($w3all_phpbb_unotifications) to display notifications count, will be not necessary to check that the var is not empty.

Both hints into help page https://www.axew3.com/w3/2022/12/switch ... le-update/
and plugin admin page, were wrong where
Author in WP -> Global moderator in phpBB.

It is NOT this way by default.
It is
Author in WP -> Registered group in phpBB
and
Editor or Shop Manager in WP -> Global moderators group in phpBB

The subsequent is: what about if an user change Role based on some action due to memberships subscriptions or because promoted to another Role in WP, based on some code logic and not because an admin changed it manually on WP profile?
The code about this will be added on 2.6.9.
I also hope to find out the way at same, to release the new updated phpBB WordPress extension

The Roles/Groups switch about if a WP user changed Role due to to some plugin process and not due to an admin action, has been added.
It is necessary to read the related option hint into plugin admin, the help page, and the included default file inline hints to understand how to correctly use it.

The option that check for front-end registration plugins pages could be removed, since the new introduction of the filter: it will be an unique function that will go to replace several filters and hooks functions on next releases, making the integration code shorter and surely compatible into any scenario with any plugin.

2 (really) not useful functions have been removed.
The public static function ck_phpbb_user( $user_login = '', $user_email = '' ){
has been little improved, and will the unique used to get/check phpBB user's info.

Many other functions will be removed on next releases, and hooks/filters removed/substituted or improved on related functions. It is just a start.

The flow will be smooth, easy to understand, and not confused like it is (even if it is perfectly working right now). The integration plugin 2.6.9 come tested working fine into buddypress, memberpress, woocommerce, and should be quite ready to work fine with any other.

Fix: avoid wordpress user registration, if same email exist in phpBB ->
Front end plugins pages: for example memberpress plugin -> memberships registration/subscription page, was bypassing the check.

It is anyway intended that when the integration start, all users have been paired, so that these kind of problems are impossible to happen.

Anyway, may someone forget that may exists some disabled user's emails or some other specific case.