02/09/2026#23
Direct changes to plugin templates may work initially, but they make future updates difficult because modified files can be replaced.
Use the supported template override approach whenever you need structural customization. This keeps your changes separate from NexaBoard itself and makes it easier to compare custom templates when a new plugin version is released.
Keep overrides limited to files you actually need to change. Copying every template creates unnecessary maintenance work.
After updating NexaBoard, review overridden templates for compatibility with any new markup or functionality.
You need to log in to reply.