I think it would be great, especially for use in transformations, for us to be able to configure fields on a Document Type or Custom Table that return single/multiple documents/table rows. These will be lazy loaded.

One way that this could be implemented is to create a custom field type that is not created as a field in the database table, but is used for storing the information of how to load the data for the property. This field would have at least the following configuration options:

1. IsMultiple? - Yes/No to indicate whether or not this field is for a single item or a list of items

2. PropertyType - Document/Custom Table/Custom Query

3. Document/Custom Table - If 2 is Document or Custom Table then indicate which DocumentType or Custom Table to use

4. Query - The query used to retrieve the data for the field. This query can have macros that access properties of the current item. For example: Select ##ALL## from CUSTOM_MYTABLE WHERE CUSTOM_MYTABLE.MyForeignKey = {%ThisPrimaryKey%}

With this field we would now know how to access the data when macros are being resolved. Here is an example:

{% foreach (mytable in mytablefield) { print(mytable.mytableproperty); } %}

OR

{% mytablefield.ApplyTransformation("MyTable.Transformations.CustomTransformation") %}

The addition of this feature would unlock an immense amount of functionality.

Users can currently upload their own Avatar, but the only constraints that we can put on them is their width/height or maxsidesize. This is fine for when their Avatar is being displayed in their profile, but really bad when displaying it in a list or activity feed. On Facebook, they auto-generate a cropped square thumbnail from your full Profile photo. By default, they shrink it and crop it square from the center, cutting off the parts of the longest side that don't fit. They also let you edit the thumbnail by moving the original photo around so you can position the part you want to be in the square. You can also choose to make it just fit in the square and it will fill any parts of the square left empty with white.

After several days of tinkering with a custom control based upon the direct uploader, I was able to make this work in Document types by adding a field for the thumbnail and hiding it in the form while using my custom form control on the main photo field to auto-generate the thumbnail and save it in the thumbnail field (a process that is way too difficult for developers and should be simplified in a future release). This actually works great, but when I went to do it with the Avatars, I couldn't think of a way to make it work well.

This should be in Kentico.

Hi, I'm talking about yellow message bar, which show at the top of the page sometimes when you edit something in cmsdesk and at the same time view at the site. It says something like: This is a preview mode of document {DocName}. Close the preview mode.

I know it only shows for authorized users, but during development it bugging me when it push layout down. To avoid this behavior you can add following style to it (I assume that this bar have id="m"):
#m {
position:absolute;
top:0;
left:0;
z-index:500; /* you may want to show it on top of everything */
}

Or you can just add this in style attribute (which is probably the best).

It doesn't cost me anything to add this style to my stylesheet, but it would be wonderful if you can fix this in future releases.
Hope for your cooperation. Thanks!

When using the 'Redirect invalid case URLs to their correct versions' to either 'use lower case' or 'use upper case', it would be logical for all future documents created to use this setting to determine what case the document alias should be.

We find it a pain that we have to manually change the case of the document alias to match the desired output, even after the setting has been used in the CMSSiteManager.

It's potentially harmful for SEO to have lots of 301 redirects, which is the case if you just leave the document alias with the default case.

Thanks,
James

Currently, the favicon is required to be on the file system in ~/favicon.ico. If multiple sites exist, they all are forced to use that one. (See the forum thread http://devnet.kentico.com/Forums.aspx?forumid=20&threadid=23459 for the details.)

There is a way to replace it with a <link> tag in the Master Page Head, but that doesn't work if a ~/favicon.ico also exists, because the system adds its own <link> tag at the end of the generated <head>.

We suggest the system should only add the automatic <link> tag to ~/favicon.ico if an appropriate link tag isn't already in the Master page->Head box. Right now it will duplicate the favicon <link> tag and place it's automatic tag last in the <head> so it overwrites the custom one placed there by the web developer.

OR, better yet, let this be set directly in the Site Manager Settings either which path to use for a favicon, or even one more better yet, letting you upload the favicon directly via the Site Manager interface. Of course, all of these settings would be able to be set/uploaded at the global and site levels.