Views Ajax fonction + Boost = error in IE

Error appears only when this option an ON:
"Cache html documents/pages"

For some reason, Boost is thinking it's html, when in fact its javascript. If you could apply this patch to Boost have it output watchdog error messages, that would be helpful. Let me know what the message is when you visit that link.

Sorry, but I dunno how to use .patch files on shared host X_X

Edit the module file, it's not that hard...

I'll be adding in debug functionality in the next release btw so if you can wait around for a little bit then this problem should be easier to solve. #617394: Verbose setting of 7 & 9 for debugging

Ok, I will wait. Thanks!

Ok, I will wait. Thanks!

Download http://drupal.org/node/621560
Enable verbose 9
Let me know whats up

Ok, I enable verbose 9, Views Ajax not working for IE...

when you hit views ajax, what does watchdog output for that url?

But where I can see this Watchdog?

admin/reports/dblog

Debug: _boost_ob_handler()
HTTP Info: 200 - text/html, text/javascript
Path: cache/normal/www.mysite.com/site/views/ajax_view_name=News1&view_display_id=block_1&view_args=&view_path=node&view_base_path=null&view_dom_id=1&pager_element=0&page=1.html
Content Container: node_page_default
Content Type:
ID:
Cache This: TRUE."

and

Debug: boost_cache_set_node_relationships()
7 of 7 given entries to the boost_cache_relationships table added or updated; 0 entries removed due to them being outdated.

k so the front page is returning the correct http content type: text/javascript. Which means the file should be saved with the correct extension, .json. Try the latest dev which should be available for download in the next 30 min; I've reworked some of the code surrounding this issue, so hopefully it got fixed in the process. If not this gives me something to work with; the view is a block type, not a page type.

Edit:
Dev is ready, give it a shot

no result:
Debug: _boost_ob_handler()
HTTP Info: 200 - text/html, text/javascript
Path: cache/normal/www.madfanboy.com/site/views/ajax_view_name=News1&view_display_id=block_1&view_args=&view_path=node&view_base_path=null&view_dom_id=1&pager_element=0&page=1.html
Content Container: node_page_default
Content Type:
ID:
Cache This: TRUE.

and

Debug: boost_cache_set_node_relationships()
7 of 7 given entries to the boost_cache_relationships table added or updated; 0 entries removed due to them being outdated.

delete this post please.

delete this post

Try turning off "Asynchronous Operation: output HTML, close connection, then store static file." If that doesn't work, using the latest dev, try this patch. Remember to flush the cache before testing.

Get 1.15 and set
Boost Tags: Only Set the header
Save
update rules from boost-rules and let me know if this fixes your issue.

Nope. Not fixed :(
Logs:

Debug: _boost_ob_handler()
HTTP Info: 200 - text/html, text/javascript
Path: cache/normal/www.madfanboy.com/site/views/ajax_view_name=News1&view_display_id=block_1&view_args=&view_path=node&view_base_path=null&view_dom_id=1&pager_element=0&page=1.html
Content Container: node_page_default
Content Type:
ID:
Cache This: TRUE.

Debug: boost_cache_set_node_relationships()
10 of 10 given entries to the boost_cache_relationships table added or updated; 0 entries removed due to them being outdated.

k its saving the javascript as html... but thats very strange since it's returning text/javascript as the last option; the one I use.

I wonder if I should do a !== FALSE in the if else block. Try this patch, let me know if it works.

Nope.

Debug: _boost_ob_handler()
HTTP Info: 200 - text/javascript. Using .
Path: cache/normal/www.madfanboy.com/site/views/ajax_view_name=News1&view_display_id=block_1&view_args=&view_path=node&view_base_path=null&view_dom_id=1&pager_element=0&page=1.html
Content Container: node_page_default
Content Type:
ID:
Cache This: TRUE.

Debug: boost_cache_set_node_relationships()
10 of 10 given entries to the boost_cache_relationships table added or updated; 0 entries removed due to them being outdated.

Your using a newer version of apache; one that might not serve .json files as text/javascript; due to apache not respecting the T=*** in the rewrite rule. Try this in your htaccess file

OLD:

NEW:

committed
Please Let me know if this doesn't fix the problem. You can grab the code in todays dev when it comes out in about an hour from now. Be sure to get the rules from boost-rules and try again.

nope. not fixed.

http://localhost/site/?q=views/ajax&view_name=News1&view_display_id=bloc...

Debug: _boost_ob_handler()
HTTP Info: 200 - text/html, text/javascript
Path: cache/normal/www.madfanboy.com/site/views/ajax_view_name=News1&view_display_id=block_1&view_args=&view_path=node&view_base_path=null&view_dom_id=1&pager_element=0&page=1.html
Content Container: node_page_default
Content Type:
ID:
Cache This: TRUE.

Can you put up a link so I can test the page in question? I need to see what the server is sending.

mikeytown2
Sorry but my site still active, now I add the views in the exception list. If I disable that, no one can navigate :(

But, I do all the test in my localhost (Wamp server for Win).

I need a way to reproduce the error somehow since I can't do it locally.

Ok. try now: www.madfanboy.com/site
Error only with Internet Explorer

Hmmm... now all works...
I use last version of boost (not dev), without any patch (exept for my other error)...

I'm trying the views pager at the bottom and it appears to be working. Turn on ajax in the view

yeah, ajax turned on, all works!

Going to mark this as fixed then.

after upgrading to the latest, i get this error in IE when clicking a quicktab containing a view.
quicktabs containing nodes and feeds are fine, it's just the view tab that generates this error.
"an error occurs at /views/ajax."

update: turning off "Asynchronous Operation" fixes the error.
(feel free to mark this fixed)
but don't i want "Asynchronous Operation" turned on?

Chadd try this patch.
#636704: Removed $ by mistake in boosted1/2.txt & boost-rules page
Also use the latest dev of quicktabs as that fixes the error your having most likely.

marking this as fixed, reopen if this didn't answer your question.