Hi, I don't know if this is my own fault or not, but in IE7 I get a javascript error on Line 1 char 1 Object expected. The functions are not executed (but the initial output is ok).
In FF everything works fine.

Thanks for such a lovely module!

Comments

lance.gliser’s picture

lance.gliser commented

There are more errors than the original post listed.
Here's another:

Line: 144
Char: 3
Error: Expected identifier, string or number
Code: 0
URL www.example.com/admin/content/nodeadmin

Looking into it now.
[Edit] After debugging, it seems this error is irrelevant.

lance.gliser’s picture

lance.gliser commented

It appears IE is breaking when trying function filterNodes()

  data = {
    ajax: 'query',
    filterText: $('input#filterText').val(), 
    filterType: $('select#filterType').val(), 
    filterUser: $('input#filterUser').val(),
    optionLimit: $('input#optionLimit').val(),
    optionOffset: nodeadminState.optionOffset,
    optionSortField: nodeadminState.optionSortField,
    optionSortDirection: nodeadminState.optionSortDirection,
  };

Please note that IE does not support ending the last line of a JSON object with a comma. While it's still not working, removing the last comma removed one error.

  data = {
    ...
    optionSortDirection: nodeadminState.optionSortDirection
  };
lance.gliser’s picture

lance.gliser commented
Status: Fixed » Active

In function updateTable() on line 73:

pageResults = 'Go to result: ';

Adding the 'var' declaration to this line solves the second issue.

var pageResults = 'Go to result: ';

After fixing the two problems above, my copy works in IE7.
And thank you, Joe. This module is a wonderful solution to access problems I've fought with.

lance.gliser’s picture

lance.gliser commented
Status: Active » Needs review
arithmetric’s picture

arithmetric commented
Status: Needs review » Fixed

Hi Lance,

Thanks for your work on this issue. I applied your fixes, did some testing, found and fixed a few more issues -- but now the Content Administration page works for me with IE 7.

I guess compatibility with the Microsoft browser warrants a new beta release! Let me know if you notice any problems with the beta 2 release.

Thanks,
Joe

Status: Active » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.