In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-03 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/02 Report--
Solve the problem of errors in batch generation of Imperial cms7.0 data updates? This problem may be often seen in our daily study or work. I hope you can gain a lot from this question. The following is the reference content that the editor brings to you, let's take a look at it!
What if there is an error in batch generation of Imperial cms7.0 data updates?
Today's upgraded Imperial cms7.0 made a strange error in generating pages.
Table 'table prefix _ ecms_news_data_' doesn't exist...
Obviously this is a hint that the table does not exist, but the table name is wrong, it is missing _ 1, and the correct table name should be the table prefix _ ecms_data_1
The latter _ 1 is set according to the stb field in the main table. After looking at the records in the main table phome_ecms_news, it is normal for his stb field to be 1.
However, it is found that there is no wrong ID in the main table. In my case, the ID is 118, but there is no ID in the main table.
Later, it was found that the generation mechanism of Imperial cms7.0 should first read the index table such as phome_ecms_news_index, because there is still 118th ID in this table.
If there is no existence in the main table, the contents of the stb field will not be read, and the problems mentioned above will arise.
How to solve it?
At the bottom of the data update of Imperial cms7.0, there is a function of cleaning up excess data.
See the prompt "Table'* .phome _ ecms_' doesn't exist.update * * _ ecms_ set havehtml=1 where id='' limit 1" in the picture.
It seems that Imperial cms officials also expected this to happen.
So I cleaned it up again, and the result was not so smooth and didn't work.
The cause of the failure that we already know should be solved by ourselves. The solution is to clean up the excess information in the index table.
I use a sql to solve the problem.
Delete from `phome_ecms_news_ index` where id not in (select id from phome_ecms_news)
Imperial cms background executes this sql statement
And then generate it. It's done.
Thank you for reading! After reading the above, do you have a general understanding of solving the problem of errors in batch generation of Imperial cms7.0 data updates? I hope the content of the article will be helpful to all of you. If you want to know more about the relevant articles, you are welcome to follow the industry information channel.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.