What should I do if an error occurs during batch generation of data update in Empire cms7.0?
After today’s upgrade, Empire cms7.0 had a strange error when generating the page
Recommended to study "Empire cms tutorial"
Table 'Table prefix_ecms_news_data_' doesn't exist...
Obviously this is a prompt that the table does not exist, but the table name is Wrong, he is missing _1. The correct table name should be the table prefix _ecms_data_1. The _1 after
is set according to the stb field in the main table. I looked at the main table phome_ecms_news. It is normal that the stb field of the record is all 1
But I found that the ID of this error does not exist in the main table. In my case, the ID is 118, but there is no ID 118 in the main table.
Later I discovered that the generation mechanism of empire cms7.0 should first read the index table such as phome_ecms_news_index, because there is still an ID of 118 in this table.
If it does not exist in the main table, it will naturally not be read. When it comes to the content of the stb field, the problem mentioned above will appear.
How to solve it
After reading the data update of Empire cms7.0, there is a [ at the bottom Clean up excess data】Function
See the icon prompts "Table '*.phome_ecms_' doesn't exist...update ***_ecms_ set havehtml =1 where id='' limit 1”
It seems that the empire cms official also expected that such a situation might occur
So they cleaned it up, but the result was not always smooth. It didn't work...
We already know the cause of the failure, so let's solve it ourselves. The solution is to clean up the redundant information in the index table
I use A sql to solve
delete from `phome_ecms_news_index` where id not in(select id from phome_ecms_news)
The empire cms background executes this sql statement
and then generates it, it’s done.
The above is the detailed content of What should I do if an error occurs during batch generation of data updates in Imperial CMS 7.0?. For more information, please follow other related articles on the PHP Chinese website!