Julian_Kingman

Thank you @brand-rocket, I can’t believe it was something so simple! Adding my nickname brought back the editor.

Awesome, thanks!

Update: The meta fields seem to be the problem. No matter what kind I add, it causes the error. I wrote a workaround in my own plugin for now:

//check if they have meta fields
    if(!get_post_meta($post_id, 'original')){
      $sources = array('eBook', 'article', 'blog post', 'book', 'video', 'audio');
      add_post_meta($post_id, 'original', $sources[rand(0,5)]);
    }
    if(!get_post_meta($post_id, 'assigned_user')){
      add_post_meta($post_id, 'assigned_user', rand(1,7));
    }

hooked into save_post

• This reply was modified 8 years, 4 months ago by Julian_Kingman.

Huh, nevermind, your fix seemed to work….

I’m also having this issue.

I identified the problem, I posted about it on github:
https://github.com/fooplugins/foogallery-custom-attachment-fields/issues/1

It is indeed a bug, please fix!

Thanks! For some reason I thought it was part of the same plugin

Sorry, ignore the JS error, that was because of BWP minify.

Sure, here’s a link: https://dl.dropboxusercontent.com/u/35961575/q2w3-fixed-widget.zip

Sorry for the delay.

I gave the developer the code, so hopefully we’ll see it in an update for the plugin soon.

I’d also like to see a stop point, such as the ID of an element, that the widget shouldn’t go below. I wrote to the developer to see if he’ll take the code, if I write it.

Same problem with same error as Brainstorm IT, I network deactivated and activated on each install separately and now it’s working.

Does the plugin rely on .htaccess for anything? A windows server doesn’t have an .htaccess file.

Yep, it worked, thanks for the awesome responsive support! I really appreciate that.

Sidenote: I saw you had an answer to another person that involved installing the development version, so I tried that, but still no luck ??
I deactivated the plugin and was able to make my sidebars, so now I activated it again.