For some reason it seems to work in Chrome, but not in Firefox, Safari and Opera. I’m using a MacBook…
I also use Simple Fields on the regular “Pages” post type and it works there. Very strange.
I, too, am stuck with ‘Adding…’, if I use Firefox (which I prefer to do). It works fine in Chrome, just like DogHustler.
I’m also on a Mac (using Mountain Lion).
If the author needs any more info, I’m happy to provide it.
Thanks,
Chris
Does any of you have access to firebug or web inspector and can check what the “console” says when you click Add?
Hi Pär,
Sure thing. Here is the output from Firebug’s Console.
Sorry the formatting isn’t ideal, here:
10:43:44.051 Use of getUserData() or setUserData() is deprecated. Use WeakMap or element.dataset instead. requestNotifier.js:64
10:43:45.755 Use of getPreventDefault() is deprecated. Use defaultPrevented instead. load-scripts.php:4
10:43:46.875 “init simple_fields_file_field” scripts.js:22
10:43:47.191 Use of Mutation Events is deprecated. Use MutationObserver instead. script.js:19
10:43:48.497 Use of getUserData() or setUserData() is deprecated. Use WeakMap or element.dataset instead. requestNotifier.js:64
10:43:57.109 Use of getUserData() or setUserData() is deprecated. Use WeakMap or element.dataset instead. requestNotifier.js:64
10:43:57.141 SyntaxError: unmatched ) in regular expression load-scripts.php:4
Do let me know if you need any more information. Thanks for looking into this. 🙂
I have found out part of the problem. If I deactivate TinyMCE Advanced the plugin works again so there seems to be a conflict between these two plugins.
I use the textarea field type and I think that TinyMCE tries to change the tool bar for these (as the are HTML enabled). For some reason this no longer works. But if the problem is in Simple Fields or TinyMCE, I don’t know.
//Dan
Ahhh. Good call, DogHustler.
I’m also using TinyMCE Advanced on my site and can confirm that, when I deactivate TinyMCE Advanced, the “adding” function in Simple Fields works perfectly, in Firefox.
I have a variation of this problem too.
I’m using WP 3.9 (multi-site)
If I try and add a repeatable field set to any page, post or custom post type, it gets stuck on the ‘adding’ message. If I then ‘update’ the page then the new set is there.
This happens with Chrome, Firefox and IE (all on win7)
I’m sure it’s something to do with the new TinyMCE editor that ships with WP 3.9 but it’s a problem that definitely needs addressing.
Just wanted to throw in my two cents:
1. I don’t have TinyMCE Advanced plugin and I am still getting this problem.
2. I tried installing TinyMCE Advanced and then disabled it, just to see if that works, but no luck.
3. I can confirm cokeyblokey’s observation that if we click on update or save draft etc., then the new set of fields is added.
And this does needs addressing, or at least a workaround.
If you uncheck ‘Use HTML editor’ in the repeatable field options of Simple Fields then the fields get added as they should. Developers are working on a fix (as per another thread).
I’m having the same issue with adding a repeatable field. In my case the console stated there was an unexpected ; in or near jQuery.
The event function in scripts.js of the simple-fields plugin requests the field group (repeatable field) from the server using a XHR post request. The respons data has a very confusing line of code in it
if ( ( tinymce.DOM.hasClass( wrapper, 'tmce-active' ) || ! tinyMCEPreInit.qtInit.hasOwnProperty( edId ) ) &:&: ! init.wp_skip_init ) {
I asumed that the &:&: in the middle of the if statement was the culprit so I added replace('&:&:','&&') on line 415 in the simple-fields scripts.js which solved the problem.
(Because this forum editor converts any attempt of writing the entity name of ampersand into ampersands I have replaced the comma with a colon in the code above.)
Editing the plugin is of course not ideal but in my opinion better than editing WP core files.
I was not able to find the code that tscok mentioned, but the code on following thread fixed the issue for me:
http://wordpress.org/support/topic/error-in-wordpres-39?replies=1
So was this not fixed in the update? C’mon…
I hear ya! Let me know if the latest update fixes it.
I too am having the same problem…
Mac 10.9.2
Firefox – stuck at Adding…
Chrome – no problem
Safari – stuck at Adding…
…and I believe I have found the culprit. Within the TinyMCE Advanced settings under Advanced Options, there is a checkbox that reads: Stop removing the <p> and
tags when saving and show them in the HTML editor. When this is checked, the problem arises; uncheck it, it ceases.
I hope this helps…
Thanks!
