If you're not familiar with these languages, WordPress specific API, debugging and how our code is structured we strongly suggest you to hire us to do the work for you.
Please also note that modifying any plugin's source code will automatically cancel your support license since it will compromise our ability to generate the source code from the corresponding plugin's design.
We list all customization options and methods in our customization page. We suggest you watch the customization videos we provide on plugin pages to get used to NextGen customization module we use in our plugins. The NextGen customization module offers ability to modify frontend pages from plugin settings without modifying template files. In the future, we will add more functionality to this module but in its current state it's very powerful.
If you need plugin specific step by step instruction please check your plugin's documentation first. We provide detailed instructions specific to your plugin there under Customization section.
Customization steps in generic terms
All of our plugin pages can be customized by modifying HTML section of layout files. Please follow the steps below:
- Create "emd_templates" directory under your theme's directory.
- Copy the layout files that you want to customize into "emd_templates" directory which you created in step 1 from PLUGIN-ROOT/layouts directory
- Modify the file based on your needs
The layout files you added in the "emd_templates" has always precedence over the plugin's layout files. If the customized files get deleted, the layouts which came with your plugin are displayed. We recommend that you create a child theme if you'd like to minimize the risk of accidental deleting of the "emd_templates" directory because of theme updates.
The following layout file types can be customized:
- Single view page
- Archive view page
- Taxonomy view page
- Search form result page
- Standard list page
- Integration page
- Org chart record and tooltip layout page