What should I do if the DIY module is deleted in the frontend of Discuz X but cannot be deleted in the 'Module Management' in the backend?

Today I redone the homepage. First, delete all the "original DIY modules" in the front desk, and then create new ones. But after I finished, I went to the backend to see, damn, a lot of the deleted "original DIY modules" were in the "backend." -Portal-Module Management" still exists, but the "Page" column is marked as "Not filled in", and there is no button to delete it. What's going on and what to do?

Ha, there just happened to be an official post today about this. The original text is as follows:

Today I saw many people saying that they had clearly deleted a certain DIY module in the front desk, but it was in the background "portal - But it still existed in "Module Management", was marked as "not filled in", and could not be deleted. So I tried it out of boredom and tried it in various orders.
It turns out the reason is incredibly simple. . . . . .
This is simply because when deleting a module, it is not "delete the module first and then delete the frame in which the module is nested", but "directly delete the frame in which the module is nested". Directly delete the frame in which the module is nested. The module is no longer in the foreground, but the background has not received an instruction to delete the module.
The "Module" menu is blue, and the "Framework" menu is red. Delete the blue first and then the red to ensure there are no problems.
If you want to be lazy and delete "module" and "framework" at the same time, you will have to pay the price.
Any time you are lazy you will pay a higher price.

If a problem has already occurred, then...
1. Go to the pre_common_block table in the database and delete the redundant modules in "Portal-Module Management".
2. Go to the pre_common_diy_data table in the database and delete the redundant pages in "Portal-Page Management".

Database, frontend, and, new