Author: devusrmk

Files List This tab is always present and cannot be closed, as it is the starting point of the Files Manager feature. Here, you can view all files and folders inside the WordPress root directory. From here, you can open files and folders, create files and folders, and upload ZIP files. Create File and Folder […]

Enabling Adminer By default, this feature is disabled as a legacy measure from when Adminer was considered a security risk. To make it bulletproof, we have disabled access by default. To enable it Accessing Adminer Once enabled you will see new tab it the left sidebar. About Adminer Database Manager inside WordPress With DevKit, you […]

Enable Debug Enabling WordPress debugging is crucial for identifying and resolving issues during development. With debugging enabled, WordPress logs errors, warnings, and notices, helping developers detect bugs, compatibility issues, and deprecated functions. To enable debug you would need to setup FPT or FPT plugin and locate wp-config.php and edit WordPress files. Or you can just […]

Error log is moved to separate page. They can be long and to improve performance we will load it only when you open error log page. To enhance the experience even further, we’ve added syntax highlighting, allowing you to visually distinguish content by color. You can access it from DevKit sidebar. Once you open the […]

The Users Manager feature in DevKit Pro provides an efficient way to manage user accounts on your WordPress site. By default, this feature is disabled and needs to be activated through the settings. Key Features Quick User Switch: Once enabled, a quick switch option appears in the top bar, allowing you to easily switch between […]

Salts are created using secret keys. Secret keys are located in two places: in the database and in the wp-config.php file. The secret key in the database is randomly generated and will be appended to the secret keys in wp-config.php. The secret keys in wp-config.php should be updated to strong, random keys to maximize security. […]

A common practice for debugging is to disable all plugins and then enable them one by one. Since the DevKit should not be the issue, we’ve made it invisible in the plugins list. This allows you to perform a bulk disable of other plugins without affecting the DevKit. Once enabled Devkit will be hidden