- This topic has 5 replies, 2 voices, and was last updated 6 years, 4 months ago by
.
-
Posts
-
Hello!
I just bought this for use in my organization, and I just want to say up front: very impressive! The basic functionality is very very useful. I do have a couple of questions, however:
1.) The WYSIWYG field type is broken for widgets. The field automatically opens to the ‘text’ tab, and it will not let me switch to the ‘visual’ tab. When I have the console open, I see a js error that originates in load-scripts.php (which I assume generates js dynamically). I can paste the error in here, if you need it, but it’s very long winded, and doesn’t look useful.
The field still ‘works’ (i.e. you can type text in, like a regular text box, and upload and insert media), but I think most of my end users would prefer the TinyMCE editor they’re used to.
2.) I’m planning on using your plugin on a number of different WordPress installs that my organization supports, each with their own distinct theme and whatnot, so I would rather write my common extensions as plugins, rather than functions/files in the theme folder. The ‘acfw_include_widgets’ filter works great for this; I already have it up and running, however I was wondering if there was an easy way to place the template files in the plugin folder, as opposed to the theme folder? If it’s not possible, I can figure something goofy out, but I’d very much prefer to do it natively.
Thanks much in advance for the help!
-DanHi Dan, regarding the JS error, I’ll look into it, though I have a feeling this may be a plugin conflict or a bug in ACF core. ACFW has almost no JS files, instead relying on ACF to provide a consistent experience.
As to your second point, this is the second time today someone has requested that feature so I’ll look into it some more later today. 🙂
I’m glad you like the plugin! I tried to make it as easy as possible 🙂
From what I can tell, this is a more general problem with WordPress—it doesn’t handle TinyMCE in widgets very well. You have to do some black magic, so when it’s instantiated, Wordpess’s JS sees it as unique. This post covers it, sort of: http://wordpress.stackexchange.com/questions/82670/why-cant-wp-editor-be-used-in-a-custom-widget
Thanks for looking into this!
Hi Daniel, I’ve just tested the WYSIWYG issue with ACFW and the latest version of ACF and I’m not seeing the JS error that you mentioned. I dug into ACF core to see if I could find a similar issue, but as it turns out, ACF doesn’t even use the
wp_editor()function to render TinyMCE due to the customizations in ACF.I would suggest disabling some plugins or checking your theme to see if there is anything causing a conflict. At this time, ACF + ACFW doesn’t cause any noticeable issues like you are describing on WP 4.2.2
Still working on that other thing. Should have something workable by the end of the week or sooner.
Hey! I didn’t forget about you! I’ve had a crazy couple of weeks and haven’t had time to sit down and knock this stuff out! If I don’t post another reply in a day or two feel free to bug me on Twitter or something 🙂
Well that didn’t take long! You can download a beta copy from the master branch on Github.
You can use the filter
acfw_custom_template_dirto add in a custom directory. This is placed before the default load order so you can still use the default behavior as well for other files.Just pass back a string path pointing to the directory where the files are located. This directory could technically be anywhere so feel free to place your templates within other plugins or maybe a separate folder in your theme 🙂
Let me know if it works!
- The topic ‘WYSIWYG and plugins’ is closed to new replies.