You could get around this by creating your own renamed copies of those functions.
- Create a module.
- Copy the content of each affected plugin's twigextensions folder to your module's twigextensions folder.
- Adjust the namespaces in these files to match your module
- Rename the functions / filters in these files to something unique.
- Load these twigextensions in your module's main file (
use statement plus
- You can now use the filters in twig by referencing the unique name you gave them.
If you haven't worked with modules before, you can use pluginfactory.io to scaffold a module that includes lots of example code, including all the required code to set up a twig extension.
To improve on this further, instead of a straight up copying of the twig extensions, refactor them to call the public functions in the original plugin files. This will ensure it's much less likely to break things when the plugin gets updated later.