Brent Wilson

Hello,

Sorry for the slow turnaround here!

Are you still seeing this with our latest version of Solid Performance, version 1.4.0 that was just released? If so, I will be happy to dig in more here to get you a solution!

Regards,
Brent Wilson
WordPress Support Technician

Hello John,

Glad you reached out here!

I have let our developers know about these deprecated messages but rest assured that these will not cause anything to break on your site.

If you are seeing these on your front end please be sure that you have disabled define(‘WP_DEBUG_DISPLAY’, false); in your wp-config.php file. This will prevent these types of messages from showing on the front end of your site.

Sincerely,

Brent Wilson
WordPress Support Technician

Hello,

Glad you reached out here!

A missing database table can usually be resolved by disabling the plugin and then reenabling it. If you go through this process and you are still seeing the error, please reach out here, and we will dig in!

Hello,

Glad you reached out here!

Running into a critical error is something that WordPress can definitely help you troubleshoot, and here is how:

To get closer to the root cause, enabling WordPress’ Debug Log is the first step. This will allow you to generate a log of the errors, which you can use to identify the issue. Here’s how you can do it:

1. Open your site’s wp-config.php file, which is located in the root directory of your WordPress installation. ?
2. Add the following code **above** the line. /* That's all, stop editing! Happy publishing. */:

// Enable WordPress Debug
define( 'WP_DEBUG', true );

// Tell WordPress to log everything to /wp-content/debug.log
define( 'WP_DEBUG_LOG', true );

// Hide general PHP errors
@ini_set('display_errors', 0);

// Turn off the display of error messages on your site
define( 'WP_DEBUG_DISPLAY', false );

This will instruct WordPress to create a file called debug.log in the /wp-content/ directory. This file will capture detailed information about any errors occurring on your site.

Once you’ve added the code and saved the file, you’ll need to reproduce the issue to ensure it gets logged. In your case, that would be recreating the “Something went wrong” message you are seeing on the Yoast dashboard.

After reproducing the issue:

• Locate the debug.log file in /wp-content/.
• Open the file and examine its contents. Try to identify any specific error messages or patterns that stand out.
• If you are stuck or need additional help, please attach the debug log with any findings in your next reply, and I will be happy to look!

This approach lets you become more comfortable maintaining your site and quickly isolate what’s happening. We are always here if you need additional help!

Hello,

Glad you reached out here and apologies for the slow turnaround.

The first thing that jumps out to me is that you are using two Security plugins, which is never recommended. Both plugins seem to attach themselves to the same parts of WordPress, which can easily cause conflicts. If AIOS is disabled and Solid Security is left enabled, does the issue persist?

Another area to look at is your .htaccess file or nginx.conf file. Is the IP address that you whitelisted listed within these files, depending on your web server choice?

I’d love to hear more about why you are using AIOS along side Solid Security, as maybe we can help get you squared away to only using Solid Security with a future update!

Sincerely,

Brent Wilson
WordPress Support Technician

Hello,

I just wanted to follow up here with you and let you know that we have made changes to our Cloudflare configuration. If you are still having issues with purchasing, please let me know and I will escalate this to our team!

Hello,

Glad you reached out regarding this!

Our development team is looking into this and as soon as I have an update from our team I will update you here!

Hello,

Glad you reached out here and I am here to help!

When you say that every form on every website is being automatically subscribed, can you let me know more details on this so that we can reproduce this on our end?

For example, can you give us specific form(s) where this is happening? Any screenshots or screencasts you can provide would also be helpful! I have installed the latest version on a fresh WordPress install and just did a test with the wp-login forum but do not see this happening on my end.

We want to be able to reproduce this on our end and get a fix out as soon as possible.

Hello,

Glad you reached out here and sorry for the delay here!

No worries, we definitely understand how that can be frustrating to see features go missing and glad you were able to zero in on the issue!

Hello,

Glad you reached out here!

This is definitely an oversight on our part and something we will be fixing with our next release that is slated to come out soon! Solid Mail fully supports 6.6.2.

If you have any other questions don’t hesitate to reach back out. We are here and happy to help!

Hi @nlpro

Thanks for the information. I’ve added to the Bedrock discussion here: https://github.com/roots/wp-config/issues/5#issuecomment-1745657039

• This reply was modified 1 year, 5 months ago by Brent Wilson.

Thanks, changing it to 2.71 allowed the update to run and now running 2.7.1.

I am running:

[22:52][root@xxxxx plugins]# mysql –version
mysql Ver 15.1 Distrib 10.4.22-MariaDB, for Linux (x86_64) using readline 5.1

• This reply was modified 3 years, 2 months ago by Brent Wilson.

I am considering going and will do so.

After upgrading to 2.7.1 and confirming that the upgrade was successful and the files are 2.7.1, I still have the same issue:

[13-Jan-2022 22:47:48 UTC] PHP Fatal error:  Uncaught mysqli_sql_exception: Incorrect index name 'membership_category' in /home/nginx/domains/bamapolitics.com/public/wp-includes/wp-db.php:2056
Stack trace:
#0 /home/nginx/domains/bamapolitics.com/public/wp-includes/wp-db.php(2056): mysqli_query()
#1 /home/nginx/domains/bamapolitics.com/public/wp-includes/wp-db.php(1945): wpdb->_do_query()
#2 /home/nginx/domains/bamapolitics.com/public/wp-admin/includes/upgrade.php(3032): wpdb->query()
#3 /home/nginx/domains/bamapolitics.com/public/wp-content/plugins/paid-memberships-pro/includes/upgradecheck.php(389): dbDelta()
#4 /home/nginx/domains/bamapolitics.com/public/wp-content/plugins/paid-memberships-pro/includes/upgradecheck.php(277): pmpro_db_delta()
#5 /home/nginx/domains/bamapolitics.com/public/wp-content/plugins/paid-memberships-pro/paid-memberships-pro.php(126): pmpro_checkForUpgrades()
#6 /home/nginx/domains/bamapolitics.com/public/wp-settings.php(409): include_once('...')
#7 /home/nginx/domains/bamapolitics.com/wp-config.php(110): require_once('...')
#8 /home/nginx/domains/bamapolitics.com/public/wp-load.php(55): require_once('...')
#9 /home/nginx/domains/bamapolitics.com/public/wp-admin/admin.php(34): require_once('...')
#10 /home/nginx/domains/bamapolitics.com/public/wp-admin/index.php(10): require_once('...')
#11 {main}
  thrown in /home/nginx/domains/bamapolitics.com/public/wp-includes/wp-db.php on line 2056

I have downgraded successfully back to 2.6.7.

• This reply was modified 3 years, 2 months ago by Brent Wilson.

This is what I am trying to accomplish: https://stackoverflow.com/a/33571268/11552576