Hi,

To use the mojoPortal Skin Exporter for Artisteer, you must have Artisteer 4 installed on your computer. Once you have it installed, all you need to do is double-click the Skin Exporter plugin you downloaded from the mojoPortal site and it will be installed into Artisteer.

All of that is done on your computer, not on your server.

HTH,
Joe D.

Artisteer is certainly not the only way to skin. Other options are:

• Use a delivered mojoPortal skin, and optionally tweak it to look like you want.
• Use one of the skins created under the mojoPortal HTML 5 skins initiative (or use it as a starting point for your own changes).
• Develop a skin from scratch (this is the most work, and only recommended if you are very good with CSS and have a lot of time).
• Pay a third party to develop a skin for you. Joe D.'s company i7MEDIA has expert designers on staff.

Whether you decide to use Artisteer or not, I highly recommend you upgrade your mojoPortal installation to the latest code line. There have been a lot of changes to the layout rendered by mojoPortal since 2.3.5.5.

Jamie

Neither Artisteer 4 skins nor the mojoPortal html 5 skins are compatible with older versions of mojoPortal.

If your 3.5 hosting is medium trust hosting you should also read the section at the bottom of the article Understanding the theme.skin file

I don't recommend setting CombineCss to false. If you do that the browser will cache it and we have no control over caching in that case.

In newer versions of mojoPortal one should leave those settings alone and after editing css just go to Administration > Advanced Tools > Design Tools > Cache Tool and click the button to reset the skin guid.

For older versions you can use the settings Jamie mentioned except for the CombineCss setting. I do not recommend ever setting that to false.

If MinifyCss is false I can usually figure out pretty easily from style.config which file a particular css rule is coming from.

Best,

Joe

We don't ship a user.config file because we don't want to overwrite it during upgrades. We ship a file named user.config.sample in the root of the web that can be re-named to user.config. In fact if mojoPortal is installed by the web platform installer it automatically renames this file and puts the database connection string there.

If you do manually rename the file then you need to copy your database connection string from web.config into user.config

​user.config can override settings from the <appSettings section of web.config, that is the only thing it can do, no other parts of web.config can be added to user.config.

Hope that helps,

Joe

modifications to user.config are not automatically detected, so whenever you edit it you need to then touch web.config, ie type a space in it and save.