The problem was being caused by invalid code in the wp-config.php file, which then broke the WordPress plugins_url() function throughout BPS Pro code, all other plugins and themes and WordPress itself causing that function to see a folder path to the /plugins/ folder instead of the URL to the /plugins/ folder.
https://codex.wordpress.org/Editing_wp-config.php#Moving_wp-content_folder
This code was in your wp-config.php file and has been commented out.
define('WP_CONTENT_URL', '/wp-content');
The correct usage for this constant: WP_CONTENT_URL is you would enter the full URI|URL to your website’s wp-content directory and not a folder path.
Set WP_CONTENT_URL to the full URI of this directory (no trailing slash), e.g.
define( 'WP_CONTENT_URL', 'http://example/blog/wp-content' );
Your System Info page is now displaying this below, which is exactly correct for your website/server:
Server Type: LiteSpeed
Operating System: Linux
WP Filesystem API Method: direct
Server API: litespeed CGI Host Server Type
Apache Modules|Directives|Backward Compatibility(Yes|No)|IfModule(Yes|No): View Visual Test
mod_access_compat is Loaded|Order, Allow, Deny directives are supported|IfModule: Yes
mod_authz_core is Loaded|Order, Allow, Deny directives are supported|BC: Yes|IfModule: Yes
mod_authz_host is NOT Loaded
- This reply was modified 15 hours, 24 minutes ago by AITpro Admin.
- This reply was modified 15 hours, 22 minutes ago by AITpro Admin.
- This reply was modified 15 hours, 12 minutes ago by AITpro Admin.