I’d like to announce that the IPBWI FAQ was translated from Anja Skrba into Croatian for free to help people from Former Yugoslav Republics: Serbia, Montenegro, Croatia, Slovenia, Macedonia, Bosnia and Herzegovina. This should make it more people some easier to get access to free SSO technology. Thank you Anja, for your great work! As I don’t speak a single word Croatian, please note that I can not give any guarantee or validation for the information within that translation.
Maximizing compatibility with third party plugins or themes is always a high priority aim for IPBWI for WordPress. Some plugins or themes may not be able to get compatible without help of their authors. Unfortunately, authors of WishList member are not willing to adjust a line in their code to make their plugin compatible with IPBWI for WordPress. From today you’ll find a conflicts page in help section which will list conflicts between IPBWI for WordPress and other plugins which are currently not able to get fixed until the respective plugin authors change their mind.
This is a big feature and maintanence update for IPBWI and a maintenance update for IPBWI for WordPress. Here’s a summary of the changelog:
- bug fixed with UTF-8 encoding
- recaptcha can be loaded with curl now, too (see updated config file)
- group class with new functions: getList, create, update, listMemberGroups
- member class with new function customFieldValue, major updated function updatePhoto (please care of the new parameters/requirements, see live examples and docs) and stripped updateAvatar function
- permission class with new function create.
- post class now respects post queue moderation settings on user group level (sets in function create “queued” to 1 when user is in a usergroup required to get all new posts moderated). Function getList was enhanced with to parameters supporting listing posts by member id and a option wether to show queued posts, too.
- improvements in class report
- loading IPBWI within IPB itself works again
This changelog includes most important changes. There are several other improvements in IPBWI. Some of the changes above are sponsored by taz.de
And finally, documentation has been updated.
There is a maintenance release out for both, IPBWI and IPBWI for WordPress. These include fixes and enhancements in registration and editing functions.
There are several bugfixes and new features in IPBWI 3.4.1:
- New Functions: $ipbwi->report->getList and $ipbwi->report->create to get lists of user reports and create new reports. These functions were sponsored by taz.de, a leading German Newspaper.
- Bug fixed: IPBWI forgot to set cookie upon login. Big thanks to Marcel for reporting the bug and sending a fix, too.
Bugfixes in IPBWI for WordPress 3.4.1:
- time in forum comments on WP differs 1 hour from forum time – fixed. Please note you may update WordPress\wp-content\themes\%your-theme%\ipbwi\comments\comment.php manually.
- New Settings Option: You now have a choice wether IPBWI for WordPress imports existing WP users who made a comment to IP.board. See IPBWI’s Admin Panel for a more detailed description.
IPBWI v3.4.0 and IPBWI for WordPress v3.4.0 are out now. These updates bring compatibility to IP.board 3.4.0. Here’s the changelog:
- compatibility with IP.board v 3.4.x
- support for the new IP.board rich text editor. A live demo can be seen below this news post when logged in or in IPBWI’s live examples.
- compatibility with IP.gallery 5.x
- updated live examples for friends management and forum lists
- small issue when loading WordPress widgets in IP.board fixed
- dropped support for PHP 5.2 for IPBWI for WordPress since this 3.4 release of IPBWI for WordPress. If you are still using PHP 5.2, I strongly recommend updating your system.
IPBWI and IPBWI for WordPress 3.3.x are currently not compatible with Invision Power Board release 3.4 beta. When using IPBWI, please don’t update to Invision Power Board 3.4 until IPBWI and IPBWI for WordPress v3.4 are released.
Seems that current release of IPBWI works in most cases. You can try it out in your development environment and report me all bugs you’ll find. I’ll fix them until beginn of december.
Invision Power announced that there will be a new Single Sign On Interface in IP.board 3.4.
My Statement: IPBWI brings a stable, flexible and easy to use SSO solution since years, well documented, opensource and with support on business level.
IPS Connect will provide the same. But there are three differences:
- IPBWI actually IS made for 100% IP.board integration, it is modularized and can be extended by me as service or by your own very easy. IPS Connect actually will provide SSO only.
- IPBWI still provides SSO…and 92 other great functions, too
- IPS Connect will allow Master/Slave State for SSO Connections, which means IP.board will be able to be the slave within the site network. I’ve no access to the source of IPS Connect as it isn’t released yet, but I’m sure that this isn’t a feature of IPS Connect itself, it’s a new feature of IP.board’s member database management – which will give new opportunities to IPBWI, too. That’s great and I’ll love Invision Power for that :)
I was a bit shocked how many people did not know that IPBWI exists when I’ve read their comments on the news linked above – IPS Connect actually will provide about 1% of the feature set of IPBWI. Not such a big news from Invision Power, I think.
The new final release allows loading WordPress widgets in IP.board – it works now stable and flawless. Additionally, there are tons of bugs fixed. Don’t wait and try out the new Major Release of IPBWI for WordPress!