Wordpress Template Editor PluginWorpress Template Editor Plugin
The example template filename is stored in the "template-sample" folder of the plugin. "Editor Templates" is open code work. Following persons have added to this plugin. fix: tpl_custom tag output invalid optional element. new: multi lingual suppport. fixed: template Tag "tpl_custom" does not store entry information when Tpl_custom is set to the pending state. bugfix Warning Error.
Multi-site multisite supports. modify Betabox sslug. Supports the "default" option.
Collaboration with the developers
It is very widespread that designers adapt and expand upon extant plug-ins to their own needs, which is one of the great benefits of using open code programs. Often they do this by making their changes directly to the plugin, which causes a flaw in system integrity and becomes a form of maintainance.
Hacking a plugin to make your changes creates a scenario where, to perform an update, you have to go through a tedious procedure of comparing your release manual with the cannonical and then synchronizing it in both ways. The first thing you need to do before trying anything else is to post a notice to the plugin programmer, telling him what kind of changes you need, and offering to work with him to integrate them into the kernel plugin.
What's great about this approach is that everyone who uses the plugin benefits from your work, and you've done something for the developers whose work you've profited from. However, the developers may not like the concept, or it doesn't fit his visions for the plugin, so it doesn't always work.
If you just want to include some new features in your plugin, the simplest thing is to just delete or alter nothing that the plugin does. Then you can just create a plugin that will run next to the plugin you want to customize. However, if you need to alter or delete the plugin functions, there's a much better way to just hack it, and it's something you're already used to:ooks.
Like WordPress provides hook that allows plug-ins to adapt and expand them, plug-ins can themselves offer hook that allows other plug-ins to adapt them. So if you luck out, the plugin you want to expand was created by a programmer who knew enough and took care enough to incorporate user-defined hook that will allow you to expand your plugin.
When they do, your work is quite simple; all you have to do is create a plugin that will run alongside the plugin that you customize, and register recalls for the user-defined hook that the plugin provides. Unfortunately, most people have not yet learnt to include their own hook, so you can't always count on them.
Even without them, there are two more ways you can modify the plugin that are better than just chopping. In WordPress, the plugin you want to modify by enrolling core hook call-back features. Then, within your call-backs, you can call features from the other plugin that you need to restore the parts of their features you want and prevent the parts you don't need.
However, sometimes it's not perfect to bypass their hook, because their features aren't sufficiently robust to allow you to call single characters you need without also calling the things you don't want. However, even in this case, there is another way that you can use that is better than simply hacking all your changes into the plugin.
Too much work to substitute your own core hookbacks for your own would allow you to directly chop the plugin, but instead of making all your changes to it, just adding the customized ones you need, and then put the remainder of your features into a seperate plugin.
Then you can send a fix to the plugin creator and ask him to add the required customized hook to the next version of the plugin. When yes, then you can free upgrading to new versions and your customized plugin will run clean next to theirs. Even if they don't, you can still perform an update by inserting your customized hook into each new version later.