2.2.1

The latest release of Verified Profiles (2.2.1) that includes several bug fixes.

• Fixed a bug where language strings were not displayed properly.
• Fixed a bug where a php warning was returned when no locations were set.

This is a public release version that can be installed on live environments. Please report any problems you encounter by creating an issue on GitHub. Pull requests are also welcome.

2.2.0

The latest release of Verified Profiles (2.2.0) that includes brand new features requested by the community!

• Upload a custom image to use as your verified badge (from the new ACP module).
• Select which pages should display verification badges for users (from the new ACP module).

This is a public release version that can be installed on live environments. Please report any problems you encounter by creating an issue on GitHub. Pull requests are also welcome.

Note

The features added in this version were intended for a premium version of the extension called Verified Profiles Pro. However the premium version was never sold so the free version of Verified Profiles will continue to be developed with new features. Please considering sending a donation to help support future development of this extension. Thank you ❤️

2.1.0

The latest release of Verified Profiles (2.1.0) completely refactors most of the extension codebase bringing with it new features!

• Board administrators can verify individual users from the ACP (no change).
• Users can now hide their verification badge if they have permission to do so.
• Verification can be enabled for groups so all members are automatically verified.
• Verification is now displayed across the entire board (including the ACP, MCP and UCP).

This is a public release version that can be installed on live environments. Please report any problems you encounter by creating an issue on GitHub. Pull requests are also welcome.

Important

Version 2.1.0 has been repacked to address an issue during phpBB.com validation whereby new database changes were not added into a new, separate migration file and instead were merged into one single migration which may have caused issues for people updating the extension from 2.0.0 to 2.1.0.