Conflict with Advanced custom fields?

  • Resolved simonwimell

    (@simonwimell)


    3 years, 5 months ago

    Hi!

    I’m having issues with some custom gutenberg blocks, built with ACF, that can’t be previewed/edited because a console error that is caused by ProfilePress. There’s no error if I disable ProfilePress.

    Any ideas what’s causing this and how to fix it?

    See error below: 

    [Error] Error: No select2/compat/dropdownCss
D — select2.min.js:2:1371
s — select2.min.js:2:2716
(anonym funktion) — select2.min.js:2:1205
(anonym funktion) — select2.min.js:2:54080
e — select2.min.js:2:57186
d — select2.min.js:2:59365
(anonym funktion) — select2.min.js:2:68898
each — jquery.min.js:2:2981
(anonym funktion) — select2.min.js:2:68857
initialize — acf-input.min.js:3:11155
e — acf.min.js:1:16345
(anonym funktion) — acf.min.js:1:16474
(anonym funktion) — acf.min.js:1:16009
(anonym funktion) — acf.min.js:1:16009
(anonym funktion) — acf-input.min.js:3:8536
init — acf-input.min.js:4:2265
select2_init — input-v5.js:24
(anonym funktion) — input-v5.js:88
each — jquery.min.js:2:2981
(anonym funktion) — input-v5.js:87
(anonym funktion) — acf-input.min.js:3:30995
u — acf.min.js:1:15660
n — acf.min.js:1:14654
(anonym funktion) — acf.min.js:1:5065
(anonym funktion) — acf-input.min.js:1:4423
map
a — acf-input.min.js:1:4346
u — acf.min.js:1:15660
n — acf.min.js:1:14654
(anonym funktion) — acf.min.js:1:5065
(anonym funktion) — acf-input.min.js:1:4159
map
r — acf-input.min.js:1:4103
u — acf.min.js:1:15660
n — acf.min.js:1:14654
(anonym funktion) — acf.min.js:1:5065
s — acf-input.min.js:1:4029
u — acf.min.js:1:15660
n — acf.min.js:1:14654
(anonym funktion) — acf.min.js:1:5065
t — acf-pro-blocks.min.js:1:14308
t — acf-pro-blocks.min.js:1:15337
e — acf-pro-blocks.min.js:1:14016
t — acf-pro-blocks.min.js:1:14238
oj — react-dom.min.js:127:169
Aj — react-dom.min.js:160:451
Aj
unstable_runWithPriority — react.min.js:25:262
ab — react-dom.min.js:154:193
Te — react-dom.min.js:146:358
Te
(anonym funktion) — react-dom.min.js:61
unstable_runWithPriority — react.min.js:25:262
Pg — react-dom.min.js:61
ha — react-dom.min.js:60:454
Ja — react-dom.min.js:224:403
enqueueSetState — react-dom.min.js:214:412
(anonym funktion) — react.min.js:20:456
t — acf-pro-blocks.min.js:1:13203
e — acf-pro-blocks.min.js:1:13395
(anonym funktion) — acf-pro-blocks.min.js:1:15097
c — jquery.min.js:2:28300
fireWith — jquery.min.js:2:29041
(anonym funktion) — jquery.min.js:2:30941
(anonym funktion) — acf-pro-blocks.min.js:1:6242
c — jquery.min.js:2:28300
fireWith — jquery.min.js:2:29041
l — jquery.min.js:2:79812
(anonym funktion) — jquery.min.js:2:82256

	Me (react-dom.min.js:125)
	(anonym funktion) (react-dom.min.js:139)
	Wg (react-dom.min.js:67:244)
	oj (react-dom.min.js:127:257)
	Aj (react-dom.min.js:160:451)
	Aj
	unstable_runWithPriority (react.min.js:25:262)
	ab (react-dom.min.js:154:193)
	Te (react-dom.min.js:146:358)
	Te
	(anonym funktion) (react-dom.min.js:61)
	unstable_runWithPriority (react.min.js:25:262)
	Pg (react-dom.min.js:61)
	ha (react-dom.min.js:60:454)
	Ja (react-dom.min.js:224:403)
	enqueueSetState (react-dom.min.js:214:412)
	(anonym funktion) (react.min.js:20:456)
	t (acf-pro-blocks.min.js:1:13203)
	e (acf-pro-blocks.min.js:1:13395)
	(anonym funktion) (acf-pro-blocks.min.js:1:15097)
	c (jquery.min.js:2:28300)
	fireWith (jquery.min.js:2:29041)
	(anonym funktion) (jquery.min.js:2:30941)
	(anonym funktion) (acf-pro-blocks.min.js:1:6242)
	c (jquery.min.js:2:28300)
	fireWith (jquery.min.js:2:29041)
	l (jquery.min.js:2:79812)
	(anonym funktion) (jquery.min.js:2:82256)
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Collins Agbonghama

    (@collizo4sky)

    This looks like a conflict with our select2 javascript file.

    Add this code to your theme’s functions.php file to remove ours.

    add_action( 'wp_print_scripts', 'pp_deregister_javascript', 99 );
 
function pp_deregister_javascript() {
 wp_deregister_script( 'ppress-select2' );
}
    Michael

    (@mdahlke)

    @collizo4sky Are there plans to update the plugin to fix this issue? Or are we considering making all users that run into this conflict caused by the plugin adding this snippet of code to their theme’s functions.php file the fix?

    Plugin Author Collins Agbonghama

    (@collizo4sky)

    The code snippet fix is what we recommend as we require the select2 library for our own operations.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with Advanced custom fields?’ is closed to new replies.