UPDATE: SharePoint 2010, IE 7, and JQuery Issues

This is an update to an earlier post about issues with the style library, IE 7, javascript, REST interface, and anonymous access (yea, it was a lot of stuff). Here is what we have learned:

  • If you have publishing turned on, you have to make double triple dog sure that your files are PUBLISHED when you push to test, uat, prod, whatever. If anything is in draft mode and you have anonymous access turned on user will get a login screen. We thought there was an issue with the Style Library and anonymous access but it was just files in draft mode causing the problem. You can check for draft files and publish them by using Site Actions > Manage Content and Structure
  • If you are using the REST interface with javascript it won’t work once you turn on anonymous access. You will have to redo your code or find a different solution-our programmer is busy right this second redoing all the beautiful code he wrote because we had no idea it didn’t flippin work when anonymous access was turned on 😦 We tried everything we could to make it work-we reached out to all the SharePoint pros at our company, on the web, even called SharePoint 911 (why is it whenever I call SharePoint 911 I have an issue that is impossible to fix??). So, in short, wanna use the REST interface? Don’t use javascript to query your lists, write a custom service instead.
  • I think the last issue was IE7 not liking Jquery. Our programmer had to rewrite his code a bit to make it play nice iwth IE 7-I’ll get him to tell me exactly what he did so I can let you guys know 😉

We are sooo close to launching the new ms.gov, just a few more days!!!! I designed this little guy over the New Years holiday (holiday? HA!).


3 thoughts on “UPDATE: SharePoint 2010, IE 7, and JQuery Issues

  1. It may be too late for this project, but SPServices works with anonymous access. (That may be another good selling point over the client object model.) You can query lists and oh so much more.

    Of course, the proof is always in the pudding. I can’t guarantee full functionality in every environment. I’ve seen some very wacky network topologies out there.


      • Thanks for the recommendation Marc. SPServices was the perfect solution in our case. The main difference is that REST uses LINQ, which to date doesn’t allow anonymous access, whereas SPServices uses Sharepoint’s web services, which can be configured to allow anonymous access for read-only operations. SPServices doesn’t seem as robust as REST and async operations are trickier, however. All we need to do now is find a clean way to prevent loading of init.js and core.css for anonymous uses.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s