Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
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.
Comment | File | Size | Author |
---|---|---|---|
#3 | boxes-1561196-q-path-ajax-issues-homepage-2.patch | 2.38 KB | arpieb |
#1 | boxes-1561196-q-path-ajax-issues-homepage-1.patch | 2.46 KB | tirdadc |
Comments
Comment #1
tirdadc CreditAttribution: tirdadc commentedComment #2
tirdadc CreditAttribution: tirdadc commentedComment #3
arpieb CreditAttribution: arpieb commentedThe 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...?)
Comment #4
mrfelton CreditAttribution: mrfelton commentedSame problem here on D6. I tried directly backporting this patch, but it didn't fix the issue.
Comment #4.0
mrfelton CreditAttribution: mrfelton commentedblah
Comment #6
hefox CreditAttribution: hefox commented