The DIY module is deleted at the DiscuzX foreground, but the module management in the background cannot be deleted. what should I do?

The DIY module is deleted at the DiscuzX foreground, but the module management in the background cannot be deleted. what should I do?

Redo the homepage today. delete all the "original DIY modules" at the front end and create a new one. after that, go to the back end, many deleted "original DIY modules" still exist in "background-portal-Module Management", but the "webpage" column is marked as "not filled, there are no buttons to delete. What is this and how to do it. Haha, today, an official post says this. The original article is as follows: Today, I saw many people say that they have already deleted a DIY module on the front-end. it still exists in "Portal-module management" in the background and is marked as "not filled ", and cannot be deleted. if you are bored, try it and try it in multiple sequence. It turns out that the cause is simply dying ...... This is only because when deleting a module, instead of "deleting the module first and then deleting the nested framework of the module", it is "directly deleting the framework of the nested module ". Directly delete the framework of the nested module. the module does not exist at the front end, but the backend does not receive the command to delete the module. The menu of "module" is blue, and the menu of "framework" is red. delete blue and then red to ensure that there is no problem. It is costly to delete "modules" and "frameworks" at the same time. At any time, laziness is costly. If the problem already exists, then ...... 1. delete unnecessary modules in "Portal-Module Management" from the database pre_common_block table. 2. delete unnecessary pages in portal-page management in the pre_common_diy_data table of the database.

Database, front-end, and, new