I started copying across elements in the hope of picking up what broke it. Using the default clean theme and no plugins I connected it to the old DB. Then I copied across my old wp-config.php and it broke! I have rebuilt the site (added the plugins theme and child theme one by one) off the new install and it all works on 7.3.
![]() ![]()
I have in the V 2.3 the same problem but after the update everything is fine last friday come the problem i run the command php bin/magento setup:upgradeUpdating modules:Schema creation/updates:Notice: Undefined index: customerentity in /./././vendor/magento/framework/Setup/Declaration/Schema/Db/SchemaBuilder.php on line 152The Table customerentity is in my Database but with a prefix. Our old Dev install the Database with prefix.Strange was 10 minutes before i get this problem a make a complete new testsystem when i run the command on the test instance there is working.i find in a diff i file what is different the file was from fishpig wordpress integration in the wordpress theme. On the next morning i copy the file in the testsystem in now there is the same error. But the file is only a template file from wordpress, after ther error i delete the file but the error is stay further.Have somebody the same problem?
$query = ' INSERT INTO posts(title,content) VALUES('$title',$content')';Not a solution to your question, but another problem you have.Never build an SQL query by concatenating strings. Sooner or later, you will do it with user inputs, and this opens door to a vulnerability named 'SQL injection', it is dangerous for your database and error prone.A single quote in a name and your program crash. If a user input a name like 'Brian O'Conner' can crash your app, it is an SQL injection vulnerability, and the crash is the least of the problems, a malicious user input and it is promoted to SQL commands with all credentials. When answering a question please:.
![]()
Read the question carefully. Understand that English isn't everyone's first language so be lenient of badspelling and grammar. If a question is poorly phrased then either ask for clarification, ignore it, oredit the question and fix the problem. Insults are not welcome. Don't tell someone to read the manual. Chances are they have and don't get it.Provide an answer or move on to the next question.Let's work to help developers, not make them feel stupid.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |