Lucas James

Nice app. Definitely does not have all of the sourcebans features.
One important missing feature appears to be the ability to banning admins names. Anyone can see this even though sourcebans site/db is set to hide. There should be a setting on ipb to change this is that's the case. 
 
What is the member name lookup option for when using advanced search in bans? This would be nice if it actually worked and pulled the users steamid from their ipb profile to lookup. The "Save" button should also probably be changed to "Search" instead. 
 
Also importantly there is no sourcebans logs? This is really important for upper staff to manage and check what admins have done. I see no way to do this other than manually checking the database or using the original sourcebans website on the side.
Overall good plugin but could use some extra finishing touches. Hopefully some updates will come 🙂
Thanks

You need to edit the /etc/my.cnf file with following parameter under the [mysqld] section:
default-storage_engine=innodb
Save the file and restart MySQL/MariaDB.

The only WordPress SSO application in Marketplace that works; however it has not been updated to 4.6:
@stoo2000
 

The only WordPress SSO application in Marketplace that works; however it has not been updated to 4.6:
@stoo2000
 

The culprit here is the following parameter; in your .htaccess, php.ini and user.ini files:
session.save_path Change this:
session.save_path = "/var/cpanel/php/sessions/ea-php72"
To this:
session.save_path = "/tmp"
Save the files. Refresh the IPS upgrade error page and you're good to go.
This applies to PHP version 7.0 or 7.1 and so on...

You need to edit the /etc/my.cnf file with following parameter under the [mysqld] section:
default-storage_engine=innodb
Save the file and restart MySQL/MariaDB.

Create their account manually from AdminCP and then ask them to change their password. Response Code 4 shows that their registration Email/IP is blacklisted.

The culprit here is the following parameter; in your .htaccess, php.ini and user.ini files:
session.save_path Change this:
session.save_path = "/var/cpanel/php/sessions/ea-php72"
To this:
session.save_path = "/tmp"
Save the files. Refresh the IPS upgrade error page and you're good to go.
This applies to PHP version 7.0 or 7.1 and so on...

You need to edit the /etc/my.cnf file with following parameter under the [mysqld] section:
default-storage_engine=innodb
Save the file and restart MySQL/MariaDB.

You need to edit the /etc/my.cnf file with following parameter under the [mysqld] section:
default-storage_engine=innodb
Save the file and restart MySQL/MariaDB.

You need to edit the /etc/my.cnf file with following parameter under the [mysqld] section:
default-storage_engine=innodb
Save the file and restart MySQL/MariaDB.

Add the font-size attribute below the line-height in custom.css:
@media screen and (max-width: 767px) { .ipsType_normal.ipsType_richText { line-height: 1.6; font-size: 14px; } } You can adjust the size to 14px or 15px or whatever.

While doing the upgrade on a client's forums from IPS 4.4 to 4.5, I encountered following MySQL error:
For the benefit to all, here is an easy fix to alter the table row format:
Here is a quick video tutorial:
 

A very alarming situation. SendGrid has gone nose down from 10/10 to 0/10.
Trust Pilot Review: https://www.trustpilot.com/review/sendgrid.com
Would someone from IPS can elaborate why you guys are still providing SendGrid integration despite its poor service and ratings?
This is end of 2020, we need some good email provider(s) API integration to the IPS software, like AWS SES API etc.
Thanks

VPS are low-powered with limited/less resources. Instead, get a dedicated server with good specs at reasonable price Optimize the server security/speed for PHP, Nginx, PHP-FPM, MariaDB, etc Cloudflare Pro with optimized settings and WAF enabled Redis Web-API for outgoing Emails It isn't the issue with Cloudflare, so you're users will see the live updates without cache problem.
There's already a setting in IPS software to compensate that.

Add this to your theme's custom.css file:
/* Header Logo in IPS 4.5 */ #elSiteTitle, #elLogo { height: 80% !important; } Adjust the height % as per your requirement.

A very alarming situation. SendGrid has gone nose down from 10/10 to 0/10.
Trust Pilot Review: https://www.trustpilot.com/review/sendgrid.com
Would someone from IPS can elaborate why you guys are still providing SendGrid integration despite its poor service and ratings?
This is end of 2020, we need some good email provider(s) API integration to the IPS software, like AWS SES API etc.
Thanks

Add the font-size attribute below the line-height in custom.css:
@media screen and (max-width: 767px) { .ipsType_normal.ipsType_richText { line-height: 1.6; font-size: 14px; } } You can adjust the size to 14px or 15px or whatever.

If Redis is what IPS recommends, then why can't IPS let it be a recommendation, instead forcing clients to switch over? If Memcached is performing better than Redis for some users and they are comfortable with that (including myself as I host multiple servers and clients' IPS sites), or those clients who don't have Redis on their server due to their Host restrictions; then why to simply deprecate it?
My say: Please do NOT deprecate Memcached.

Add the font-size attribute below the line-height in custom.css:
@media screen and (max-width: 767px) { .ipsType_normal.ipsType_richText { line-height: 1.6; font-size: 14px; } } You can adjust the size to 14px or 15px or whatever.

Web API is faster than SMTP: https://sendgrid.com/blog/web-api-or-smtp-relay-how-should-you-send-your-mail/

Not using Amazon SES via SMTP on any client's forum. Some use PHP Mail, some custom SMTP, some Gmail/Gsuite SMTP, and some SendGrid API. So, out of all, Gsuite/Gmail SMTP and SendGrid API are the fastest without any forum-posting lags.

+1

If Redis is what IPS recommends, then why can't IPS let it be a recommendation, instead forcing clients to switch over? If Memcached is performing better than Redis for some users and they are comfortable with that (including myself as I host multiple servers and clients' IPS sites), or those clients who don't have Redis on their server due to their Host restrictions; then why to simply deprecate it?
My say: Please do NOT deprecate Memcached.