Deprecated: Cannot use “parent” when current class scope has no parent

The error is gone but on upgrade there is some NF Maria DB migration errors. They go away when reloading so probably not a big deal. So different issue and temporary at that but including the errors just in case you wanted to check them out.

DESCRIBE IF;
NF_Database_Migrations_Forms->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_FormMeta->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_Fields->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_FieldMeta->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_Actions->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_ActionMeta->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_Objects->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_ObjectMeta->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_Relationships->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_Upgrades->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1 1064

DESCRIBE IF;
NF_Database_Migrations_Chunks->run()
Plugin: ninja-forms You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘IF’ at line 1

@jmcelhaney, appreciate the update and no longer having to see the error.

I confirm that the deprecated notice doesn’t display anymore after the 3.4.26 update. Thank you.

@dkomando

It looks like there’s a difference in how MariaDB and MySQL handle “IF NOT EXISTS”, which is a statement we use upon install/upgrade to determine if all of the correct database tables are in place for Ninja Forms to work.

Gotta love it when system architectures don’t speak the same language, right?

I’ve added a bug report for this, and our devs will need to look into it. Thanks for the error messages though. That should point them straight to the problem.