Conflict with Gravity Forms

Hi,

This is a conflict with the Titan Framework that we use for managing plugin options. However, this bug should have been fixed in a prior version. Could you please confirm which version of Awesome Support you’re using?

Fresh installs from the plugin repo, 3.2.9

If @bfintal is around: have you heard of conflicts between TF and Gravity Forms?

In case anyone is still trying to resolve this, the file in question that is causing trouble is: ~/wp-content/plugins/awesome-support/vendor/gambitph/titan-framework/lib/class-option-color.php

As a workaround, in this file, I’ve changed the code found around 76, which should be:

jQuery(document).ready(function($) {
	"use strict";
	$('.tf-colorpicker').wpColorPicker();
});

to:

jQuery(document).ready(function($) {
	if ($('.tf-colorpicker').length) {
		"use strict";
		$('.tf-colorpicker').wpColorPicker();
	};
});

I’m unable to replicate this issue with AS 3.2.9 and Gravity Forms 1.9.6.

But thanks anyway! Bare in mind that every time there’s a plugin update the edit will be gone…

I was also having this problem and can confirm that dornstudio’s fix above works perfectly.
I would recommend that the authors of this fine plugin merge their suggestion into the core plugin.

Jack

I had same issue however code mentioned above didn’t work for me! So, I went to the Titan-Framework page over at GitHub and found the working update:

	/**
	 * Load the javascript to init the colorpicker
	 *
	 * @since 1.9
	 *
	 * @return void
	 */
	public function startColorPicker() {
		?>
		<script>
		jQuery(document).ready(function() {
			'use strict';
			if ( typeof jQuery.fn.wpColorPicker !== 'undefined' ) {
				jQuery('.tf-colorpicker').wpColorPicker();
			}
		});
		</script>
		<?php
	}

You guys may want to look at updating the version of Titan-Framework you are using in the plugin, it’s outdated!