Redux Framework & Font Awesome Conflict with Salient theme

I am currently in the process of developing a site using the Salient theme (version 8.0.15) by ThemeNectar brought on ThemeForest – https://themeforest.net/item/salient-responsive-multipurpose-theme/4363266 with a child theme.

When activating the Ultimate Member plugin, I noticed the Salient Theme Options Panel messed up. Salient uses the Redux Framework for it’s theme options.

The Options Panel CSS is fine as I am using a child theme and followed these instructions from the theme support team – https://themenectar.ticksy.com/ticket/962692/

Ultimate Member loads it’s unique copy of the Redux Framework before anything else, which then cripples the Salient Theme Options Panel as not all Redux Fields .js files are loaded, for example the typography field is not loaded as a result.

After looking into the Ultimate Member code, I managed to find a fix by modifying the file um-admin-init.php which is located in ultimate-member/admin/um-admin-init.php

The fix involves taking all the code between lines 14 to line 19 and wrapping them in a unique function placed under the top <?php tag and before class UM_Admin_API.

This is what my custom function looks like and I can confirm it has fixed the issues with the Salient Theme Options Panel (apart from the Salient crown logo appearing in the Ultimate Member Settings Panel, which isn’t really a big deal).

function load_um_redux(){
		if ( !class_exists( 'ReduxFramework' ) && file_exists( um_path . 'admin/core/lib/ReduxFramework/ReduxCore/framework.php' ) ) {
			require_once( um_path . 'admin/core/lib/ReduxFramework/ReduxCore/framework.php' );
		}
		if ( !isset( $redux_demo ) && file_exists( um_path . 'admin/core/um-admin-redux.php' ) ) {
			require_once( um_path . 'admin/core/um-admin-redux.php' );
		}
}
add_action( 'after_setup_theme', 'load_um_redux', 10 );

The question I have, is it possible for Ultimate Member to receive an update to prevent this bug from appearing, as I am going to have to modify the code of this file every time Ultimate Member is updated. Not sure if my fix code is the correct way of doing it, but it’s resolved the issue. There may be a more elegant way of coding it.

Also another issue I have noticed is Ultimate Member includes it’s own version of the web font – Font Awesome. This conflicted with the Salient theme too. Ultimate Member overrides Salient’s Font Awesome files with an older version of the font and as a result, the old Google+ and Instagram icons appear instead of the new icons which are included with Salient’s version of Font Awesome, which is newer than what is included in Ultimate Member.