I'm coming across three issues.
1) The social bookmarking option in a child portal uses the wrong url for the images. The path is like "www.domain.com/childportal/desktopmodules/blog..." when it should be "www.domain.com/desktopmodules/blog..." It shouldn't be including the child portal in the url, it should go to the application root, otherwise it can't find the images in a child portal and you end up with a row of X's instead.
2) In IE7, the images used for "edit" "trackback" "print" "location" etc. in the footer are cut off. I've added padding of 7px to the bottom of the classes there and also set the background image alignment to "top left" instead of "center left" and that corrected the issue. This happens in almost every skin used unless the text size is at least the same height as the background icon, unless the padding is added to the appropriate blog css classes. So, there is a work around for that problem, but not everyone using DNN is going to be able to figure that out on their own unless they are pretty familiar with DNN's style sheets and css styling in general.
3) Again, another IE7 issue. Yeah, yeah, I know, we all know IE has major issues with everything, but darn it 80% of the people out there are using it to browse the web. About the only group I know of that use Firefox 100% exclusively and won't use IE of any version are librarians. The other browsers are still insignificantly used. But I digress with the various browser useage stats. The width settings of 99% placed on the input text boxes generally cause the end of the input box to be cut off as you can see in the image below. If you have your skin set to display at say 1230px this isn't really a problem as things get stretched wide enough. But, anything much narrower and then ends are cut off and pretty much looks like there is some error or problem rendering the page even though they still function fine. Also, this generally is a problem if the modules are not all kept in the same content pane. Visually, and for organization, quicker access and effeciency, I place the view blog in the contentpane and the search blog and blog archives modules in the leftpane, rightpane, or one in each if the skin is wide enough. And, that adds to the problem as it narrows the the content areas for each of the blog modules. It would be helpful to have those inline width settings moved to the style sheet, or at least add an exclusive blog module text input class of some kind, so those width settings can be overridden to get a proper display in ALL scenarios, not just the default stacking off all the modules in one content pane on a wide enough page.
