Blog posts by Maria Sognefors

Set up a user friendly Edit Mode before the training

Tue, 23 Apr 2013 13:48:52 GMT

EPiServer is, as you probably already know a very flexible system. There is plenty to do to adapt the tool for both visitors and editors. I am so often surprised with that so few do anything about the editor interface.

This blog post is translated with Google Translate. Read the post in Swedish here

I think one reason is that it is so easy to change so that nobody does. The developers do not see it as a problem that there are fields with strange names or tabs that can not benefit from. It does not matter that there are many folders in File Manager, for they are, after all, not be used. But from my perspective, one can not be more wrong. It is exactly this that matters.

A person who has never seen EPiServer has no idea that these things are easy to change and think it must be so. The field where an editor to write his text named Main Body does not think it is logical for that to which to write their body. This creates two problems, and the risk is that the person think that the system is not user friendly and boring. The second problem is that it makes it unnecessarily difficult for a person to learn the system.

My advice to you is that already in the requirement specifications of the website to ensure that all names and field right from the start. There is no reason to delay it. I get so often hear, that we take it later. The problem is that "later" rarely comes. It is simply not done. Even if you do not do it right so it MUST be done before the training of editors. It is often when the editors meet the system the first time and you know how they say, FIRST IMPRESSION LAST.

To simplify for you as a specifier / clients I have made a list of things that need to be examined in EPiServer before training so that editor mode is as easy as possible to learn and understand. If you do not know how things should be done, bring the list to your provider and go through it together. Most of the points concerning EPiServer 6 and earlier, but it's good to go through the list even for EPiServer 7.

Name and help texts on field

All fields in templates may have their own names and help texts. These are often quite technical names and help texts are often lacking. There should be good clear name that makes it easy to understand what each field should contain. This can be done in XML files, so that it is possible to have the editor interface in multiple languages, if desired. Making decisions about which language you should have prior training. Change preferably not on the default name from EPiServer, then this will affect the user documentation to come.

Order in the field

Put the fields in a logical order, so that it becomes easy to fill a page with content. Determine if certain fields should be mandatory or not. Also make sure that it is logical to understand why some fields located on a particular tab. Generally speaking, it may be appropriate to place fields such as page is built, top down simply.

Flaps position, name and any permissions

Determine the order in which tabs to show and which names they should have. Put any rights if not all to see all the tabs.

Settings in the editor field

As the new editor, it is perfectly possible to have different settings on different editor field in the same template. The preamble field would not normally allow the same opportunities as a body field. It would certainly not have as great a field. All this can be customized. Making decisions about size, buttons and design in each field. See attached example from another customer. Please read an old blog post about it here.

Permission to templates / templates available and name

When creating a new page, often appear all templates in a list. Which to be displayed can be controlled in various ways and by those that will be available for a certain template, but also by permission. It needs to be fixed so that editors do not think they can create all kinds of pages. Also give all templates logical names and help texts. Sort them in a logical order in the places where they are more in the same list.

Structure and permissions in the file manager

About EPiServer file manager is used, there should be a finished structure with permissions on the folders. There must be a logical way to find files and know where to invest. Failure to do this from the beginning, the file manager will be like a haystack that it is impossible to find anything in. It is important to determine the starting points to use, and structure them so that the correct starting point is displayed first.

Folder structure for block

If you use EPiServer 7, we also need a folder structure of and access rights to the block.

Folders in the form handler

It is quite common that there are lots of forms and hence a need to put them in different folders that you should find. Create these folders before training, we learn editors to find right from the start.

Permissions in tree structure

The various permissions that different groups will have, should be established before the training. It will be silly if a person has the right to do things during the course, but do not have it then. The danger is that it leads to becoming confused by too many things during the course and then when you come back you become frustrated because you can not do things that made during the course. You often think you make a mistake, though, this is actually the system that has limitations.

Clear up the tree structure

The tree should be as clean as possible, with as much "real" data as possible. Remove whatever tests and other devices and control up to any systemic side is a little hidden for editors. The tree should as far as possible reflect the structure you see on the website, it is most logical for the editor.

Multi language / Globalization

In many solutions the language support enabled, though it is not supposed to work in multiple languages. Should the site be only in one language, this function should be disabled.

Workflows

Should workflows used? If not then hide this tab.

Client Component for Excel is not needed in EPiServer CMS 6

Thu, 03 Nov 2011 20:31:00 GMT

Did you know that you don’t need to install client component in EPiServer CMS 6 to be able to export form data to Excel. I didn’t and I found out the hard way.

I have many times in various training facilitys installed the client components that you need in EPiServer CMS 5 to upload files using drag and drop, spell checking and the ability to export form data to Excel.

This blog post is translated with Google Translate. Read the post in Swedish here

As many times as I have done it, I have been asked how to do to install them. The problem with installing components are usually not to find the button to press but is much more likely that you do not have the right to install things on your computer, that you have security settings that you can not download from the Internet or the like.

Modern browsers usually have lots of security warnings before you must download and install anything, which means you often have to answer quite a few questions before you come all the way. This means that the actual installation is not completely obvious.

Since EPiServer CMS 6 came, I got a new computer and have therefore installed the components again. I thought that I then do a little blog post with an accompanying guide on how to do in order to refer to the future. I can not brag about being a technical genius, but I'm not completely lost. How, I wore my time so I was unable to install all components.

There were no problems with the advanced file upload, but I could not get the link to Excel. I think I turned off all types of security settings that were possible to turn off, but nothing made me successful. In EPiServer CMS 6, I use not the editor-property that requires spellcheck using Word, so I didn’t care about that. I only managed to get a green check mark on the bottom option, see the picture below.

After tried this too long, I contacted one of my former colleagues at EPiServer. One who occasionally come to my rescue when my own knowledge does not reach anymore. The result of that conversation was that in EPiServer CMS 6 is not needed any component to export data from forms to Excel. In CMS 6 it is solved i with JavaScript instead to be able to support multiple browsers.

Spontaneously, I was pissed of that response when I had struggled long to get it installed. I wanted to have a green check! I was also pissed that the interface and manuals still makes me think I need to install this item, which I do not need. After I calmed down I realize is good for me and all other editors. Now we will not have to install it, plus we can export from any Web browser, which is really good.

Now it was just up to me to spread knowledge about this. Hope it saved you some time!

TinyMCE vs EPiServer Editor

Thu, 26 Aug 2010 11:55:29 GMT

Once you install EPiServer CMS 6 is the new editor, TinyMCE (open source) as standard. However, it is entirely possible to still choose the old editor. Having now been working in the new editor a while, I would like to share with you the pros and cons of the new editor from the editor's daily work.

This blog post is translated with Google Translate. Read the post in Swedish here »

Benefits of Tiny

Not dependent on a particular browser

One of the biggest advantages is that you do not rely on Internet Explorer to edit pages. Now you can edit pages in EPiServer CMS as well with Firefox, Safari or Chrome. There is a tremendous lift.

Greater possibilities for adjustment of the various fields

How many of us have not been angry that the old editor, could exist only in one size? How tired we have not been clicking of us apart and when we come together because we want to add / remove a button in the editor all fields on lots of templates?

With the new Tiny, this is only a memory. It is possible to customize each Editor box, so you choose which buttons you have and how large it should be. You can also point to a custom CSS for each box, so it really is a WYSIWYG-esteem. This can also be saved as a global setting so that you can use the same field in multiple templates. This is totally awesome and saves a lot of time. For example, look like below.

Spellcheck

Correct spelling of the old editor had a lot to be desired when it was linked to MS Word. There was particular not to add new words, but to do it in Word. In the new there is no spell at all and one can consider how it can be an advantage. The discovery of the correct spelling was missing was a dyslexic person I look for alternatives. The solution for me was to switch to Firefox. It has a built-in spell check function and it is possible to download the plug-ins for all possible languages. It gives me little red, bumpy dash in just as I am used to.

With Firefox, I have some other limitations, such as drag and drop files into the file manager, so now I work often with multiple browsers at once.

Adding media directly in the editor

I can put media such as Flash and various types of formats. You can easily and smoothly without inserting directly from the file manager.

Resize where I work

The Tiny, you get a little slider in the lower right corner as you can pull in order to reduce or enlarge the box, which you are currently working in. It is a killer feature. The old maximize function, but is also known as Full Screen.

More Buttons

In this editor is it possible to use a lot more buttons. Some of the buttons has been requested before it has been raised, inter alia, to incorporate the symbolic and becomes wet. There are many more to choose from and you can choose where to be and in how many rows and create separation between the keys. It is also still entirely possible to build custom buttons with custom functionality.

Disadvantages of Tiny

Right Click Menu is gone

The built-in right click menu that I used very frequently is not there. This means that I must move the mouse and click on the buttons above, instead. It works of course, but it is hard to teach an old dog ...

Custom format in a list, common formats in another

In the old editor, we had a convenient list of the formats that we wanted our editors to choose from. We could have as many heading levels as we wanted, and that we could add a custom number format that we are baptized with the desired name. This feature is in TINY but we also get a list of heading levels and another for the custom format. The names that appear in the list of custom names are the technical names has been used for encoding, and that we see all formats even if there is a table format or aspect ratio. Not quite neat and hard to explain to one who is not too familiar with what goes on behind.

Paste unformatted is cumbersome

In the old editor I paste unformatted text with a simple right click. Now I select a button, which opens a dialogue which I will paste in. I think unnecessarily lengthy. However, I have not really clear to me how that works, too often when I'm lazy and just choosing CTRL + V it will be great, but not always. I wonder how the idea is that you should use the various options to paste?

Can not edit the image directly from the page

Often you find that a picture is too large only when you insert it into the page and possibly also previewed. Then it was smooth that I could directly from the page edit screen and save it as a new image. I have not managed to make it in the new, but I have to open File Manager and edit the picture from there and then link it into the page.

More choice in most dialogues

Most dialogues opening contains a lot more choices. There can be many occasions to be good, especially if you are a relatively sophisticated editor. But if you are not so advanced it makes the system cumbersome and difficult to master. Purely pedagogically, I think it is extremely difficult to teach others what they should focus on, and not.

Table Management

Sure, I've had a lot opinions about table handling in EPiServer editor over the years, but I think it still is better than the one in the new. I am perhaps a bit tough because I can already EPiServer's so good. You can do the same things, but I think it is more cumbersome in TINY, and there is definitely more difficult to explain to someone not completely familiar with making a html table works.

Which editor should I choose?

Although there are a lot of disadvantages and deterioration of the New editor, so I think after all that the advantages outweigh the disadvantages. Are you new in EPiServer CMS I definitely think that you should use Tiny. Have you worked for a long time in the old and perhaps also some custom plug-ins to the, I think that you should remain in it until the next release comes from EPiServer. Hopefully, most of the drawbacks when away.

This is my very personal views and some of them might be due to a lack of knowledge about how it's supposed to. Know that a lot of functionality became priority to be given in the first iteration. Just keeping my fingers crossed that it will be a priority in the next.

Irritated at Page Files in EPiServer CMS?

Tue, 17 Aug 2010 22:18:06 GMT

Do you as so many others going mad because you always get asked if you are going to create a new folder when you open the file manager in EPiServer CMS? You should know that you are not alone, but it's actually very easy to change.

This Blog post is translated with Google Translate. If you understand Swedish, please read the post here.

First some facts about the file manager and shell-side with the directory, Global Files, and Documents. There are folders that you probably recognize even in your solution. The set is made with these default directories in the file manager is designed to show examples that you can work with different folders in EPiServer CMS. You should see them as a great example, and absolutely no need to use. The idea is that you should adapt this for each installation so you may as efficiently as possible working with files on the site.

How should you choose to work?

Page Files - This is a folder that is linked to a specific page. The advantage of this is that the management of hand even when their penetration of the folder. As if you eg put rights on the page, then the same rights that apply to the folder. If you delete a page, you can simply delete the folder belonging to the side. The disadvantage of working with the page directory is that you store the files which are only available for that page. For example, to have the same image at 10 pages, you need to upload and store the image 10 times. In general, it is quite rare that the benefits of this outweigh the disadvantages, but they are. It is common to combine this with a different folder structure.

Documents - is an example of a public folder structure where EPiServer version of the files is enabled. This means that an editor can handle multiple versions of the same document / file in File Manager. Through integration with MS Office, you can edit documents directly from the file manager and save it as a new version. This kind of folder is also common to store documents in if you are using EPiServer templates for Work Rooms.

Global Files - was originally an example of a public folder structure where versioning was not activated. I saw that it was changed in my recent installation of CMS 6th Maybe it was a mistake or that the purpose is to show some examples that I did not know about. The benefits of not have versioning enabled, the folder structure is reflected exactly the same on the server. This means that I can create folders and move up and move files in Windows and it is reflected then in EPiServer file manager. Very useful in building a website or move from an old to new. One can not Windows keep moving around images that are linked to pages for which links are broken. Are you doing it in EPiServer file manager updated the pages that the files are on automatic.

The management of the various folders in the file is episerver.config (CMS 6) or web.config (CMS 5). Maybe not a file that anyone should be wasting in but I want this just to show how with a little cutting and pasting may not have to ask if I want to create a folder every time I open the file manager. The file is a part for the Virtual Path Provider. Where are all the folders that are handled by the system, regardless of whether they are visible to editors or not. Below is an extract from the file episerver.config.

The different folders are loaded in the order they are listed in this file and the editor is thus automatically in the folder that is listed first. If you then do not want you to always end up in the page's directory (the one with Virtual Name = "Page Files") and will ask if you should create a folder, you should simply ensure that the folder is not located at the top of the list of all available folders. A small easily select, CTRL + X and Ctrl + W removes a huge distractions.
My file looks like below instead and editors will get to the folder Images every time they open the file manager instead. Because I have also renamed Global Files to Images and aims to which store images without versioning. In the Documents folder should I put on my site frequently updated documents.

Be careful not to rename and change settings on the folders that you have had for a long time without having full control of what you do. Changes you the wrong way, all links to images and files to be broken.

Do you trust this?

Since I do not really have as good an eye on technology but just a little hobby is interested in what goes on behind the shell of course I can not swear if it is technically legal to do so here, but it solves my problem. I have only tested it all on the latest version of CMS 6, but I would guess that it works the same in the 5th and probably the later versions of the number 4. Read more about Virtual Path Provider, http://world.episerver.com/Documentation/Items/Tech-Notes/EPiServer-CMS-6/EPiServer-CMS-60/Virtual-Path-Providers/