Internet Explorer 10 compatibility issues

A place for discussion about skinning and design. Before posting questions here you should review the documentation about creating skins.

This thread is closed to new posts. You must sign in to post in the forums.

7/3/2013 12:04:36 AM

Sandy@HH

Total Posts 53

View Posts

Internet Explorer 10 compatibility issues

We are using mojoPortal with artisteer31-mellowyellow for our intranet. I have noticed some issues with administrative functions. When I toggle in and out of compatibility view, I can bypass the errors. I have mojoPortal running on 2 different servers and upgraded one to .NET Framework 4.5 which fixed these errors. However, in the Shared Files feature, when toggling in compatibility view, the drag and drop feature disappears. I am concerned that when we go live, there will be some viewing issues depending on whether the user has their IE set in compatibility view or not. Do you think this might be related to the skin we are using? I have tested your demo site and don't experience this issue.

7/3/2013 12:26:58 PM

Joe Audette

Total Posts 18439

View Posts

Re: Internet Explorer 10 compatibility issues

Hi Sandy,

That skin was made with Artisteer 3.1 before IE 10 was born so it could very well have some issues.

The first thing to do is make sure you have applied the Important Skin Changes especially enabling the the jquery migrate plugin but also any other things since your previous version of mojoPortal (I'm assuming you upgraded since the drag and drop file stuff is in the latest version).

Other things you could consider doing:

1. Purchase Artisteer and then get the .artx file for that skin from the ArtisteerFiles.zip on our codeplex download page, then you could re-export the design using Artisteer 4.1 which should be more compatible with IE 10

2. Maybe try one of the newer Artisteer skins that ship with the latest version of mojoPortal, you can copy them from the /Data/skins folder to to /Data/Sites/[SiteID]/skins to make them available in the site (Where SiteID is usually 1 unless using a multi site installation).

3. If all else fails you can force IE to use compatibility mode by adding a meta setting in the layout.master file as in these examples:

The first one forces IE to use IE 8 compatibility and the second one forces IE 9 compatibility, so you don't have to depend on the user doing it.

However drag and drop depends on html 5 techniques and only works in modern browsers such as IE 10 so the first 2 options are the best bet in my opinion.

Hope that helps,

Joe

7/5/2013 7:28:09 AM

Sandy@HH

Total Posts 53

View Posts

Re: Internet Explorer 10 compatibility issues

Hi Joe,

Thanks for the information and your suggested options. In another post of mine you advised me to do the Important Skin Changes which did fix the drag and drop feature.

I think I'll try a newer skin first which I'm fairly sure I have installed as I have the latest version of mojoPortal. I remember looking through them all but we liked the look of mellow-yellow. I'll have another look at the others again.

Thanks,
Sandy

7/7/2013 6:22:21 AM

Sandy@HH

Total Posts 53

View Posts

Re: Internet Explorer 10 compatibility issues

Another question please Joe. If I go the path of using Artisteer 4 to create a new design, will it integrate with the pages and content I have already created? From what I can see, when you export the design as HTML, it creates HTML pages. That confuses me. I don't see any HTML pages in my current folder structure.

Thanks,
Sandy

7/7/2013 6:30:13 AM

Joe Audette

Total Posts 18439

View Posts

Re: Internet Explorer 10 compatibility issues

In older versions of Artisteer it was necessary to export as html and then do manual steps to create a mojoPortal skin. But now with the latest Artisteer 4.1 we have a free skin exporter plugin for Artisteer that can directly export a mojoPortal skin. So you would no longer export as html, you would export directly as a mojoPortal skin.

Hope that helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.