Asgaros Forum v1.10.1: Roles & Performance Improvements
Quote from Asgaros on September 17, 2018, 11:42 pmI am happy to announce version 1.10.1 of the Asgaros Forum plugin for WordPress. This release comes with a couple of improvements in the role-system and increases performance.
New Role: Forum Administrator
A new Forum Administrator role will be available which allows you to give more permissions to your most-trustworthy members. Forum Administrators have access to the entire forum configuration in the backend without the need to give them administrator-privileges for your complete WordPress site. Additionally, in the front-end Forum Administrators have access to the normal moderation-tools as well.
Other Role Improvements
- The forum role is now shown in the backend user-overview for each user.
- Moderatos can now also ban bothersome users.
- It is now possible to ban certain users directly from the front-end via their profiles.
- Users can no longer be moderators and banned at the same time. The current role of a user is now managed via a single drop-down in an users backend-profile to avoid misunderstandings.
Performance Improvements
In this update big changes were made to the unread-logic and the activity-feed. Those changes will result in a big performance increase for forums which consist of thousands of topics or posts.
Other Changes
- Fixed rare PHP-error in rewrite-logic when a global post-object is not set
- Fixed broken links in posts pointing to other forum topics at the same site
- Fixed wrong default values for dates in database
- Minor design changes
- Other performance improvements and code optimizations
Version 1.10.1 of Asgaros Forum will be available in the next 24 hours via the WordPress Updater!
Note: Some custom-code which you have implemented to your themes functions.php file might not work anymore because of important changes to a couple of functions. Please check the existing answers in this topic for possible solutions or dont hesitate to ask for further support! 🙂
I am happy to announce version 1.10.1 of the Asgaros Forum plugin for WordPress. This release comes with a couple of improvements in the role-system and increases performance.
New Role: Forum Administrator
A new Forum Administrator role will be available which allows you to give more permissions to your most-trustworthy members. Forum Administrators have access to the entire forum configuration in the backend without the need to give them administrator-privileges for your complete WordPress site. Additionally, in the front-end Forum Administrators have access to the normal moderation-tools as well.
Other Role Improvements
- The forum role is now shown in the backend user-overview for each user.
- Moderatos can now also ban bothersome users.
- It is now possible to ban certain users directly from the front-end via their profiles.
- Users can no longer be moderators and banned at the same time. The current role of a user is now managed via a single drop-down in an users backend-profile to avoid misunderstandings.
Performance Improvements
In this update big changes were made to the unread-logic and the activity-feed. Those changes will result in a big performance increase for forums which consist of thousands of topics or posts.
Other Changes
- Fixed rare PHP-error in rewrite-logic when a global post-object is not set
- Fixed broken links in posts pointing to other forum topics at the same site
- Fixed wrong default values for dates in database
- Minor design changes
- Other performance improvements and code optimizations
Version 1.10.1 of Asgaros Forum will be available in the next 24 hours via the WordPress Updater!
Note: Some custom-code which you have implemented to your themes functions.php file might not work anymore because of important changes to a couple of functions. Please check the existing answers in this topic for possible solutions or dont hesitate to ask for further support! 🙂
Quote from Gespanne on September 18, 2018, 12:18 am“In this update big changes were made to the unread-logic and the activity-feed. Those changes will result in a big performance increase for forums which consist of thousands of topics or posts.”
Thanks from sidecar.com!
“In this update big changes were made to the unread-logic and the activity-feed. Those changes will result in a big performance increase for forums which consist of thousands of topics or posts.”
Thanks from sidecar.com!
Quote from Magic Mike on September 18, 2018, 9:39 amGreat, however after the update to v1.10.1 I experience a fatal error in regards to permissions.
Live system: https://www.fiff.pl/forumPlease have a look at the atached screenshot. Any hint, what I did wrong / how to fix this?
Kind regards,
Magic
Great, however after the update to v1.10.1 I experience a fatal error in regards to permissions.
Live system: https://www.fiff.pl/forum
Please have a look at the atached screenshot. Any hint, what I did wrong / how to fix this?
Kind regards,
Magic
Quote from imchivaa on September 18, 2018, 11:27 amafter the update,
It shows this warning:
Warning: array_keys() expects parameter 1 to be array, string given in /srv/users/serverpilot/apps/z-guideline-toolkit/public/wp-content/plugins/asgaros-forum/includes/forum-unread.php on line 91
Warning: implode(): Invalid arguments passed in /srv/users/serverpilot/apps/z-guideline-toolkit/public/wp-content/plugins/asgaros-forum/includes/forum-unread.php on line 91
after the update,
It shows this warning:
Warning: array_keys() expects parameter 1 to be array, string given in /srv/users/serverpilot/apps/z-guideline-toolkit/public/wp-content/plugins/asgaros-forum/includes/forum-unread.php on line 91
Warning: implode(): Invalid arguments passed in /srv/users/serverpilot/apps/z-guideline-toolkit/public/wp-content/plugins/asgaros-forum/includes/forum-unread.php on line 91
Quote from Asgaros on September 18, 2018, 11:35 amHello @magic-mike
This is caused by some custom-forum-modification inside your themes functions.php file. I made some changes to the permission logic so you have adjusted your code a little bit.
At first you have to register the following object:
global $asgarosforum;Instead of:
AsgarosForumPermissions::isModerator(123);Please use the following function-call:
$asgarosforum->permissions->isModerator(123);If you are not sure about the changes please post your custom-code here so I can adjust it.
Hello @magic-mike
This is caused by some custom-forum-modification inside your themes functions.php file. I made some changes to the permission logic so you have adjusted your code a little bit.
At first you have to register the following object:
global $asgarosforum;
Instead of:
AsgarosForumPermissions::isModerator(123);
Please use the following function-call:
$asgarosforum->permissions->isModerator(123);
If you are not sure about the changes please post your custom-code here so I can adjust it.
Quote from Asgaros on September 18, 2018, 11:41 amHello @imchivaa
At which forum-page does this error happens? Does it occur only for logged-in users or when you visit the forum as a guest?
Please try to use the “Mark all read” button in the overview to get rid of some of the cookies/cached values. Maybe something was stored wrong internally. If its gone after it, please let me know. If this error occurs again after it, please also let me know and tell me what steps you have done so I can try to reproduce it.
Hello @imchivaa
At which forum-page does this error happens? Does it occur only for logged-in users or when you visit the forum as a guest?
Please try to use the “Mark all read” button in the overview to get rid of some of the cookies/cached values. Maybe something was stored wrong internally. If its gone after it, please let me know. If this error occurs again after it, please also let me know and tell me what steps you have done so I can try to reproduce it.
Quote from imchivaa on September 18, 2018, 11:45 amCurrently the forum can only access by logged in users.
It happened on the main landing page of the forum.
Tried clearing cache as well as open it in incognito mode. Same result.
No steps to reproduce, i updated the plugin and visited the site, the error displayed on the landing page of the forum.
Currently the forum can only access by logged in users.
It happened on the main landing page of the forum.
Tried clearing cache as well as open it in incognito mode. Same result.
No steps to reproduce, i updated the plugin and visited the site, the error displayed on the landing page of the forum.
Quote from Asgaros on September 18, 2018, 12:20 pmHello @imchivaa
Usually I dont like to ask this question but is it possible that you can send me an e-mail containing your website-link and some login-information so that I can have a look into it and debug it directly at your website? Unfortunately I cannot reproduce this error on my development-installation or other installations. Maybe its one of those bugs which only occurs on some special conditions.
If this is fine for you, please contact me at administrator (at) asgaros.de
Hello @imchivaa
Usually I dont like to ask this question but is it possible that you can send me an e-mail containing your website-link and some login-information so that I can have a look into it and debug it directly at your website? Unfortunately I cannot reproduce this error on my development-installation or other installations. Maybe its one of those bugs which only occurs on some special conditions.
If this is fine for you, please contact me at administrator (at) asgaros.de
Quote from imchivaa on September 18, 2018, 12:24 pmCurrently i disable the warning by having this in wp-config:
ini_set(‘display_errors’,’Off’);
ini_set(‘error_reporting’, E_ALL );
define(‘WP_DEBUG’, true);
define( ‘WP_DEBUG_LOG’, true );
define(‘WP_DEBUG_DISPLAY’, false);running php 7.
Maybe php warnings are disabled in hosting level or wordpress level. If forum login still required, i can provide one.
Currently i disable the warning by having this in wp-config:
ini_set(‘display_errors’,’Off’);
ini_set(‘error_reporting’, E_ALL );
define(‘WP_DEBUG’, true);
define( ‘WP_DEBUG_LOG’, true );
define(‘WP_DEBUG_DISPLAY’, false);
running php 7.
Maybe php warnings are disabled in hosting level or wordpress level. If forum login still required, i can provide one.
Quote from Asgaros on September 18, 2018, 12:37 pmDisable warnings/notices on production-system is always a good idea to prevent data-exposure. But this warning should still not occur at all.
I also use the latest version of PHP and all debug-outputs enabled on my developing-environments without any luck in reproducing this. Lets see if we get reports for this problem from other users as well.
Disable warnings/notices on production-system is always a good idea to prevent data-exposure. But this warning should still not occur at all.
I also use the latest version of PHP and all debug-outputs enabled on my developing-environments without any luck in reproducing this. Lets see if we get reports for this problem from other users as well.