• Resolved tvejacques


    What I miss most in WordPress is a proper block management feature.

    Presently WordPress does not show the origin of a block, which means the plugin used for a particular plugin is not known. This is a problem if a site was developed by someone, and later to be modified by another developer, and problems arise due to plugin conflicts. It is also a problem within developer teams if documentation does not point to detailed purposes of plugins used.

    In List View block indicators presently show the hierarchy and nesting, but only the block type titles. It would really speed up development if next to the type of block, a label is added to indicate that this particular block is from the XYZ plugin suite.

    And even be better would be the ability to add a comment of the use case – like comments in code. One could then right there in Edit mode see both the origin and purpose of a particular block.

    This will also be very, very useful for troubleshooting. Presently if there is a plugin conflict related to blocks, it is a loooong path deactivate/activating plugins one by one, going back to Edit, going back to Plugins and looping this process trying to find the culprit.

    If the particular problem block shows its plugin origin, imagine the hundreds of hours developers will save annually trying to troubleshoot the culprit plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Better Block Management System required’ is closed to new replies.