Page 4 of 7

Re: 2.5.4 released, and coming 2.5.5 logs

Posted: Wed Feb 09, 2022 9:12 am
by axew3
phpBB WordPress common tasks extension 1.0.2 has been released, it just add users deletion in phpBB when users deleted into WordPress.

If you do not want to use this feature, and uninstall/reinstall the extension, you can leave in place 1.0.1 and follow with it
viewtopic.php?f=2&t=1670

The option do not need to be activated into the extension because the secure mechanism where it is wrapped, will only work if the WP_W3ALL plugin is installed into related and linked WP and the related option active into the Wp plugin admin page (the option self explain what it do)
It have no effect nor impact if not used/called.
It have no effect even if used/called improperly.
It require WP 2.5.5 that will be released presumably within today
Delete phpBB users when users deleted in WordPress
Note that before to activate this option, it is required to install the phpBB WordPress extension in phpBB.
If the phpBB WordPress extension is not installed in phpBB, this option will not affect.
Note that if this option is not active, users are deactivated in phpBB and not deleted, when deleted in WordPress (that is also a good antispam method).

Note that activating this, will not be possible to delete more than 50 users per time in WordPress (the delete action will refuse to follow, informing you to deactivate this option if you like to do so)

Code: Select all

== Changelog ==

= 2.5.5 =
*Release Date - 9 Feb, 2022*

* Fix: correctly remove all db options (famous 5/6 rows) when plugin uninstalled
* Fix: clean up function wp_w3all_phpbb_delete_user_signup() from not necessary code
* Add: no_avatars="1" param into shortcodes 'w3allastopics' and 'w3allastopicforumsids'. If the paramater is set and is set to 1, avatars will not display into the used shortcode, even if into the plugin admin, avatars settings have been set as active. Note that to update to this if using custom shortcodes files you have to substitute these files or this shortcode option will not affect
* Fix: 'w3allforumpost' shortcode to correctly display or not the attachment panel into rendered posts
* Add: option delete users in phpBB when deleted in WordPress. It require the 'phpBB WordPress integration extension' installed in phpBB to work as expected. It do not require to activate any option into the extension
* Note about delete users option: by default users deleted in WP are deactivated in phpBB, and it will continue to be the default behavior if option not active (and even if active: so that if the cURL will fail, and users not deleted in phpBB, users will be by the way deactivated in phpBB)
* See logs: https://www.axew3.com/w3/forums/viewtopic.php?p=5511#p5511
* phpBB extension: download and follow instructions if you wish to update to 1.0.2 (that only add the above mentioned feature about users deletion) here: https://www.axew3.com/w3/forums/viewtopic.php?f=2&t=1670
* Note: the phpBB extension will not anymore provided within the plugin. To make it more comfortable to be updated all will be ever into one single place: https://www.axew3.com/w3/forums/viewtopic.php?p=5509#p5509 
* Fix: more hints simplified (to be more clear, like about bruteforce behavior) into phpBB admin
* New: help install simplified, shortened and improved has bewen linked into plugin admin and the old marked as obsolete: https://www.axew3.com/w3/wordpress-phpbb-integration-install/
* More minor fixes and clean up
[EDITED]

Re: 2.5.4 released, and coming 2.5.5 logs

Posted: Wed Feb 09, 2022 9:33 am
by axew3
Delete phpBB users when users deleted in WordPress
Note that before to activate this option, it is required to install the phpBB WordPress extension in phpBB.
If the phpBB WordPress extension is not installed in phpBB, this option will not affect.
Note that if this option is not active, users are deactivated in phpBB and not deleted, when deleted in WordPress (that is also a good antispam method).

Note that activating this, will not be possible to delete more than 50 users per time in WordPress (the delete action will refuse to follow, informing you to deactivate this option if you like to do so)
It has been edited. It do not require to activate nothing about this into phpBB and:
By default users deleted in WP are deactivated in phpBB, and it will continue to be the default behavior if option not active (and even if active: so that if the cURL will fail, and user not deleted in phpBB, the user will be by the way deactivated in phpBB).

Like the plugin bruteforce countermeasure, it was not well explained. It was wrong the hint that say, that a warning will display when more than 4000 records stored.
It is not true, the easy (and secure) code routine, cleanup values, when they reach 4000 records, decreasing automatically the array of values.

[EDITED]

Re: 2.5.4 released, and coming 2.5.5 logs

Posted: Wed Feb 09, 2022 11:05 am
by madoma73
Hello,
with latest plugin version, I have now when I try to access some (but not all) wordpress pages a blank page with "Error: the provided email is associated with another account into our forum" whereas it is not the case !
and it is the same for all users

Re: 2.5.4 released, and coming 2.5.5 logs

Posted: Wed Feb 09, 2022 11:23 am
by axew3
did so you disabled the option:
Disable the check of the email existance in phpBB before it is updated in WordPress (front end plugins profile pages)
it will be modified to be
Disable check of the existence of the email in phpBB before it is updated in WordPress (front end plugins profile pages)
??

p.s the hint on plugin admin 2.5.5 has been rewritten like this:
disable_emailck.png
[EDITED]

Re: 2.5.4 released, and coming 2.5.5 logs

Posted: Wed Feb 09, 2022 1:22 pm
by madoma73
yes, it was all set...
but the weird thing is that issue has been solved by updating OTHERS plugins...

Re: 2.5.4 released, and coming 2.5.5 logs

Posted: Wed Feb 09, 2022 1:24 pm
by madoma73
I'm trying to optimize at maximum page load on Wordpress,
it appears the iframe js is viewed as hardcoded whereas it seems to have others ways, could you please consider using standard hooks like described below:
the recommended wp_enqueue_scripts() action hook (despite the name, it is used for enqueuing both scripts and styles) which is the proper one to use when enqueuing scripts and styles that are meant to appear on the front end. The standard functions that are used inside the hook to do an enqueuing are: wp_enqueue_style(), wp_add_inline_style(), wp_enqueue_script() & wp_add_inline_script().

Regards

Pierre