Problem with using Views Ajax for PAGER in the block

I added a file (ajax_view.js) in module_dir — the same problem..
And what did you mean when you wrote "he is now corrected with this error"? I need to update the module views or what?

In the file/sites/all/modules/views/js/ajax_view.js Drupal.Views.Ajax.handleErrors add function from the file/sites/all/modules/views/js/ajax.js (at the bottom somewhere).

What and where exactly do i need to add this function?) It would be better if you show me file)
For example, i add: Drupal.Views.Ajax.handleErrors(); at the very bottom of the file. Is it correct?

So, the error in alert is: "parsererror" :) now what?))

Карен, спасибо огромное! Помогло :) жаль только системный модуль затрагивается..

I had similar symptoms. Though the button would work on the second click. A 302 redirect was being called by Secure Pages module... which then threw an error and caused views to call the non-existent function.

The ajax path being used by views was not properly whitelisted in Secure Pages configuration. Adding "views/ajax*" to the whitelist section resolved the issue for me. Hope this helps someone.

i had the same issue but the above solution fixed my issue Thank you kratkar

Steps i have followed
1) Added the function Drupal.Views.Ajax.handleErrors to /modules/view/js/ajax_view.js
/**
* Display error in a more fashion way
*/
Drupal.Views.Ajax.handleErrors = function (xhr, path) {
var error_text = '';

if ((xhr.status == 500 && xhr.responseText) || xhr.status == 200) {
error_text = xhr.responseText;

// Replace all < and > by < and >
error_text = error_text.replace("/&(lt|gt);/g", function (m, p) {
return (p == "lt")? "<" : ">";
});

// Now, replace all html tags by empty spaces
error_text = error_text.replace(/<("[^"]*"|'[^']*'|[^'">])*>/gi,"");

// Fix end lines
error_text = error_text.replace(/[\n]+\s+/g,"\n");
}
else if (xhr.status == 500) {
error_text = xhr.status + ': ' + Drupal.t("Internal server error. Please see server or PHP logs for error information.");
}
else {
error_text = xhr.status + ': ' + xhr.statusText;
}

alert(Drupal.t("An error occurred at @path.\n\nError Description: @error", {'@path': path, '@error': error_text}));
}

2) Changed the below line in /includes/common.js inside the function drupal_to_js
return '"'. str_replace(array("\r", "\n", "<", ">", "&"),
array('\r', '\n', '\x3c', '\x3e', '\x26'),
addslashes($var)) .'"';

to

$replace_pairs = array(
// ", \ and U+0000 - U+001F must be escaped according to RFC 4627.
'\\' => '\u005c',
'"' => '\u0022',
"\x00" => '\u0000',
"\x01" => '\u0001',
"\x02" => '\u0002',
"\x03" => '\u0003',
"\x04" => '\u0004',
"\x05" => '\u0005',
"\x06" => '\u0006',
"\x07" => '\u0007',
"\x08" => '\u0008',
"\x09" => '\u0009',
"\x0a" => '\u000a',
"\x0b" => '\u000b',
"\x0c" => '\u000c',
"\x0d" => '\u000d',
"\x0e" => '\u000e',
"\x0f" => '\u000f',
"\x10" => '\u0010',
"\x11" => '\u0011',
"\x12" => '\u0012',
"\x13" => '\u0013',
"\x14" => '\u0014',
"\x15" => '\u0015',
"\x16" => '\u0016',
"\x17" => '\u0017',
"\x18" => '\u0018',
"\x19" => '\u0019',
"\x1a" => '\u001a',
"\x1b" => '\u001b',
"\x1c" => '\u001c',
"\x1d" => '\u001d',
"\x1e" => '\u001e',
"\x1f" => '\u001f',
// Prevent browsers from interpreting these as as special.
"'" => '\u0027',
'<' => '\u003c',
'>' => '\u003e',
'&' => '\u0026',
// Prevent browsers from interpreting the solidus as special and
// non-compliant JSON parsers from interpreting // as a comment.
'/' => '\u002f',
// While these are allowed unescaped according to ECMA-262, section
// 15.12.2, they cause problems in some JSON parser.
"\xe2\x80\xa8" => '\u2028', // U+2028, Line Separator.
"\xe2\x80\xa9" => '\u2029', // U+2029, Paragraph Separator.
);

return '"'. strtr($var, $replace_pairs) .'"';

thanks @jp_rajanfor - I had the same issue with views 6.x-2.12 and your solution fixed it. Can you submit a patch or shall I?

Works for me, aside from the fact that core still doesn't contain the patch mentioned in #1086098: D6 JSON is total garbage - Create RFC 4627 compliant HTML safe JSON which is a related to the issue, but can't be part of this issue's resolution really.

Marking this as critical since it exists in a stable release of views 6.x-3.0 and it breaks the normal operation of the ajax pager.

The last submitted patch, ajax.error_.handle.patch, failed testing.