Some things may be strictly unsafe, but that means you can easily activate and turn off the user’s entire site theme. Of course, this is not a desirable situation. To solve this problem, please make sure that the PHP error report is turned on in the local environment. If an error or warning occurs, please do not ignore it! If possible, test the theme in the latest 2-3 PHP versions to maximize compatibility. In environments such as vagrant, this operation is relatively simple. In general, this is probably the stage that many people have followed, but it is worth mentioning again! 6. when creating unused code and file packaging topics, you can often add additional code or files to temporarily try and create anything. When complete, you may not need much code. In short, unused code in a topic is likely to be maliciously exploited to compromise the security of the topic. To prevent this from happening, you can run your own small code check before submitting the topic to the WordPress directory. This means searching the code carefully and ensuring that: Follow WordPress’ PHP coding standard. Unused code will be removed from the topic. All code can be understood by scanning. If there are unused codes or files, please delete them! Again, this is another simple trick that requires minimal effort. However, themes and ultimately have a huge impact on user security. Conclusion if you can create a security theme, you can help publish security products in the word press theme directory with a higher approval rate. Although you do not need to be a security expert, it is important to understand the basic steps that should be taken in the subject code. This post introduces the 6 common security errors and solutions found in WordPress topics. To summarize: Escape missing data. Improper use of functions. Misuse or no use of data prefixes at all. Skip queued scripts. Ignore PHP errors and warnings. Include unused code and files. Are there any other questions about creating security topics? Please consult in the comments section below! Image credit: henryhustaba
