Hi,

I encounter the following message when I try to search for a font in the search box:


An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /OEcafe/?q=views/ajax&render=overlay
StatusText: OK
ResponseText: @import url("http://127.0.0.1/OEcafe/modules/system/system.base.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/system/system.menus.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/system/system.messages.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/system/system.theme.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/overlay/overlay-child.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/comment/comment.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/field/theme/field.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/node/node.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/search/search.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/modules/user/user.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/sites/all/modules/views/css/views.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/sites/all/modules/ctools/css/ctools.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/sites/all/modules/dhtml_menu/dhtml_menu.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/sites/all/modules/views_slideshow/views_slideshow.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/sites/all/modules/fontyourface/modules/fontyourface_ui/css/fontyourface_ui.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/themes/seven/reset.css?m4bbyh");
@import url("http://127.0.0.1/OEcafe/themes/seven/style.css?m4bbyh");

I thought this could be linked to #1376686: Error with Ajax enabled views in admin overlay for jQuery 1.7 and Views 3, but the proposed patch was already applied to my version of the file.

Thanks,

CommentFileSizeAuthor
#8 Drupal Overlay Error.txt3.69 KBBillM.Green

Comments

cy08’s picture

cy08 commented

I solved my problem using:

- #1376686: Error with Ajax enabled views in admin overlay for jQuery 1.7 and Views 3#13
in ajax_view.js, change:
url:ajax_path + querysetting,
to
url:ajax_path,

and

- #1373188: Font styles do not preview after first page in Views UI with AJAX#2
disable ajax in the font_your_face view.

sreynen’s picture

sreynen commented
Status: Active » Closed (cannot reproduce)

I can't reproduce this problem with the current versions of the related modules. Sounds like you resolved it in whatever versions you're using, so I'm closing this.

dkre’s picture

dkre commented
Version: 7.x-2.2 » 7.x-2.3

I'm having the same error on a clean install (modules/theme installed, no development started).

@font 7.x 2.3 (Local, UI, FontSquirrell)
Ctools 7.x 1.0
Jquery Update 7.x 2.2
Views 7.x 3.3

- #1376686: Error with Ajax enabled views in the admin overlay#13
in ajax_view.js, change:
url:ajax_path + querysetting,
to
url:ajax_path,

I couldn't find the above in Views 3.3.

This occurs with Jquery rolled back also.

sreynen’s picture

sreynen commented
Status: Closed (cannot reproduce) » Postponed (maintainer needs more info)

Please post the specific error you're seeing. Also, are you clicking anything between "enable" and the error appearing?

nirad’s picture

nirad commented

I get this error when using the administrative modal overlay. You can go directly to sitename/admin/appearance/fontyourface/browse/google_fonts_api (or whichever API) and you won't get the error.

BillM.Green’s picture

BillM.Green commented

I can confirm this with a brand new Drupal 7 installation. When using overlay the searching for fonts leads to AJAX-HTTP error 200. If i enter the address (www.example.com/?q=admin/appearance/fontyourface/browse/fontsquirrel) without overlay searching works fine without AJAX errors!

sreynen’s picture

sreynen commented

Please post the specific error, copied directly from the message you're seeing, not a general description of the error. This will save us time in tracking down the problem, and it's generally a good practice any time you're reporting errors.

BillM.Green’s picture

BillM.Green commented
StatusFileSize
new Drupal Overlay Error.txt3.69 KB

This is the specific error - attached as txt file.

chaloum’s picture

chaloum commented

Same issue

oddible’s picture

oddible commented

Same error, and yes going directly to admin/appearance/fontyourface/browse/google_fonts_api is a workaround. Not sure if the problem is the admin overlay (likely) or the lack of clean urls.

techcrafters’s picture

techcrafters commented

Had the same issue and can verify that enabling clean urls made the error disappear.

nithinkolekar’s picture

nithinkolekar commented

#11 worked with drupal core 7.31 and @font-your-face 7.x-2.8+0-dev.

kebz’s picture

kebz commented

I'm getting the same AJAX error message.

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /?q=views/ajax&render=overlay
StatusText: OK

The "workarounds" do work, but we shouldn't have to do these things:

  • Enabling "clean URLs" works
  • Going directly to "exampleSite.com/admin/appearance/fontyourface/browse/google_fonts_api" works too

.... However, this should be looked into and fixed by the developers.

Thanks in advance!

prairiedog’s picture

prairiedog commented

For what it's worth, we ran into the long AJAX error with the @fontyourface module (which is awesome, by the way). Simultaneously, we did have some problem turning on clean URLs. While we were fighting with that issue, we thought to go into the @fontyourface view (for Google Fonts, in this case) and turned OFF "Use AJAX" in the view itself. This vanquished the errors. At least we could page forward and search for the fonts we were after.

We'll circle back around once the clean URLs problem is fixed and turn AJAX back on, but thought others might benefit from this tip.

Cheers.

UPDATE: After resolving the clean URLs issue, we turned AJAX back on in the view. Everything works Ok. All FYI for anyone struggling with this.

neslee canil pinto’s picture

neslee canil pinto
he/him
Primary language English
commented
Status: Postponed (maintainer needs more info) » Closed (outdated)