Ajax requests are made on the wrong theme

Yes, I am having the same issue. The View seems to not know it is in admin.

Here is a quick patch to use the admin_theme for ajax views.

I'm working in a site with admin & front themes. When the widget loaded the view, the layout is broken because the ajax request loaded js/css from the front theme. Surfing the web I found this post http://www.duckzland.com/content/drupal-7-force-ajax-use-admin-theme and the first option works for me.

I added this chunk of code in .module file:

function entityreference_view_widget_admin_paths() {
  $paths = array(
    'entityreference_view_widget/*' => TRUE,
  );
  return $paths;
}

Thanks for spotting this, I committed the approach suggested by jonastg.

I know this has been closed with the committed patches but now I am having problem using entity reference view widget in an entityform because it is now returning the response with js and css of the admin theme (seven in my case) and it's breaks the front end theme because entityform was not using admin path and the entity view reference widget now thinks that it always invoked inside an admin path.

Looking and reading in the link provided in #3 it seem's that solution 2 is the more correct way for this problem and it is also the suggestion here -> https://api.drupal.org/api/drupal/includes!ajax.inc/function/ajax_base_p...

anyone having same issue with me now?

Same happens to me. I use adaptive theme for front, the widget only loads the admin theme.In my case the view is for authenticated users to select the nodes not just the admins, so its kind of important to sustain the front end look. Great module btw, totally loving it :)

So mark this as needs work, feel free to post a patch, in the meantime you could still use the hook_admin_paths_alter(), See https://api.drupal.org/api/drupal/modules%21system%21system.api.php/func...

You should checkout the latest dev version, it should be fixed (the 2.x branch).

Hey been testing the latest dev, works fine with the front end theme .... but the exposed filters in the view are not working...throws an AJAX HTTP error occurred (they were working good before in alpha3).... Should i open a new issue???

EDIT: If there is one exposed filter the ajax error occurs once and after dismissing it the ajax works. If there are multiple exposed filters the error persists and exposed filter vakues are not submitted.

I'm using the beta1 on two different sites and the exposed filters are working.

Yeah...seems the issue was not due to exposed filters but because of exposed form autosubmit.
Unchecked the autosubmit now it works great.

Am using a user view with the state and city exposed.
I've selected a few users in the modal and closed it. Now, without saving the node form if i open the modal again the exposed filters stop working.

@Dhamub you're right, it wasn't working anymore, apparently because the js workaround we have wasn't triggered anymore on click because of the ajax behavior added to the add more button, this workaround is here due IMO to a views bug, See #1809958: Views with exposed filter (ajax enabled) inside modal window (ctools), in the meantime I updated our js workaround to react on "mousedown" instead of "click", See f92ba1e

Installed the latest dev..and still the Ajax error 200 appears when using an exposed filter.
I'm using the Omega 3.1 theme, and it seems it can't find the responsive style sheet of the theme.

Hi, I just tested the latest 2.x dev version with omega 3.1 and omega 4.2 with the node_admin_theme variable set to 0 (Meaning node add form on front). and everything worked as expected.

This problem is still exist.
Tested with bootstrap subtheme as main theme and seven as admin theme where admin theme is set for creating and editing node pages.

@nithinkolekar

Try increase max_input_vars = 2000 (by default 1000)
It helped me with on admin theme Seven (non bootstrap theme) and Bootstrap -as base theme.

(https://www.drupal.org/node/2156371#comment-10634956)

OR

Try module
https://www.drupal.org/project/themekey

Added rule
If drupal:path = system/ajax (for example)
to use Admin theme.

I could help.

There still seems to be something up with this.

I have a template preprocess function in my default theme (the theme used for the node field in question) after adding values to my entity reference field it doesn't run the code, however when you next load the form it does.

I think this is related: #2534874: Does not update the $form_state variable when a selection is made.

When you click the add another button it does some ajax and loads the view modal, which is potentially in a different theme. Then when you submit the modal, ajax replaces elements in the original form (which again, may not be in the same theme).

The problem seems to lie in having the ajax submission of the views form replacing elements in a different form.