Once you set a specific node or hook_menu path to be the homepage under Site Information, hitting that /{path} will redirect you to your base_path().

Not accounting for this in boxes.module results in strange behavior when adding or editing boxes on the homepage, namely a '301 Moved Permanently' message which leads to a second AJAX call that hangs.

example.com/gta_home?boxes_delta=box-680c13da --> 301 Moved Permanently
example.com/?boxes_delta=box-680c13da --> hangs

This patch fixes this issue.

CommentFileSizeAuthor
#3 boxes-1561196-q-path-ajax-issues-homepage-2.patch2.38 KBarpieb
#1 boxes-1561196-q-path-ajax-issues-homepage-1.patch2.46 KBtirdadc

Comments

tirdadc’s picture

tirdadc commented
StatusFileSize
new boxes-1561196-q-path-ajax-issues-homepage-1.patch2.46 KB
tirdadc’s picture

tirdadc commented
Status: Active » Needs review
arpieb’s picture

arpieb commented
StatusFileSize
new boxes-1561196-q-path-ajax-issues-homepage-2.patch2.38 KB

The above patch appears to work just fine in an installation where DOCROOT for the domain is the same as for the Drupal installation, but if Drupal is nested under a subdirectory the base_path() call generates an AJAX callback URL that can cause a 404 error depending on the site config.

The attached patch swaps the base_path() call out with the internal path <front>, and in the JS code replaces the call with an empty string. (Also, couldn't find anywhere in the code that getQ was being used on the browser end...?)

mrfelton’s picture

mrfelton commented

Same problem here on D6. I tried directly backporting this patch, but it didn't fix the issue.

mrfelton’s picture

mrfelton commented
Issue summary: View changes

blah

  • hefox committed 1a7544f on 7.x-1.x 
    Issue #1561196 by arpieb, tirdadc: fix for ['q'] path results in issues...
hefox’s picture

hefox commented
Version: 7.x-1.x-dev » 6.x-1.x-dev
Issue summary: View changes
Status: Needs review » Patch (to be ported)