Am getting "PAGE NOT FOUND" messages galore due to the module using, in my case, the CONTENT TYPE where the modal is triggered as the base URL for "twitter_bootstrap_modal_loading.gif" instead of using the site's base url. here's what it looks like:

Type	page not found
Date	Wednesday 12th February 2014
Location	http://BASE_URL/CONTENT_TYPE/sites/all/modules/contrib/dev/twitter_bootstrap_modal/twitter_bootstrap_modal_loading.gif

BTW: I am stuck at 7x-3.2 at the moment because the latest release BROKE all modal usability.

CommentFileSizeAuthor
#3 2195665-4-subfolder-path.patch1.88 KBbatje

Comments

hatuhay’s picture

hatuhay commented

I rather prefer to solve "BROKE all modal usability" than returning to a previous version.
Please extend on this one.

liza’s picture

liza commented

apologies, but "broke all modal usability" isn't quite accurate; and i am kicking myself for not having taken better notes about this --because it also involved JQuery Ajax Load.

i upgraded to the new versions of TBM and JQuery Ajax Load and all the modals i had set up with them just stopped working. and it seems that one of these also messed up AJAX function in some of my forms. once i reverted back to TBM 3.2 and JQAL 1.1, all my TBM modals worked again.

again, sorry for not having more detailed info. i just went back to what worked instead of firing up devel and trying to debug. just let me know what info to get you to recreate the bug.

batje’s picture

batje commented
Version: 7.x-3.2 » 7.x-3.x-dev
Status: Active » Needs review
StatusFileSize
new 2195665-4-subfolder-path.patch1.88 KB

This patch fixed the issue with the .gif not loading for me.

bverc’s picture

bverc commented
Status: Needs review » Reviewed & tested by the community

Patch works as expected.