MiXX Collection and PostIcon Updated for CS 2007

It's about time. I've been holding off on upgrading to CS2007 because I would lose my PostIcons! :)

Thanks,

Dan

Eric, works great for new posts, but I think I screwed something up: when fudgeing with the previous version I already had some content in the blogs/PostIcons folder.  I wanted to regenerate fresh posticon images, so I purged the PostIcon folder.

So there are still images in the database that have some posticon content in the extended properties, but they no longer work because I deleted the posticon subfolders and images.

Ideas on how I can recreate the images without having to open and republish each blog entry one by one?

Thanks again!

Doug

Heh.  You didn't have to wipe them out as I used the same format.

But yes, there's a way to do all.  Look at the documentation (/Configs/MiXX.PostIcon.txt) and you can see the options for the <MiXX:PostIcon /> server control.

There's an attribute "ParseRealtime".  Read the warning about this first.

But after you set it to True, go view your blog's homepage - the thumbnails will be re-generated all in realtime.  Then all you have to do is go paging.  I set my blog at 50 posts per page and paged through all of mine (three pages) to generate the posticons here.

Make sure to set it back to False when done.  It's hell on the AppPool.

Count me in with a succussful implementation of the 2007 version!

http://keithtaylorfamily.com/

Thanks again for all your help.

I'm not sure why, but I can't find anywhere to change the trust level in the web.config file... Could someone point me in the right direction?

Ignore that above. I chose the wrong installation.

It's under the <system.web> node.

http://msdn2.microsoft.com/en-us/library/tkscy493.aspx

You don't have to enter all of that information they have there, only what I put in the readme file.

But by default, CS 2007 is set top "medium".  Try searching for just that keywork.

I'm having trouble changing the height of the icon without stretching it. Any ideas?

Hey Gerren:

The height/width is set in two places.  Once in the ~/Configs/MiXX.PostIcon.config.  Make sure you set this to the actual size you want stored on disk.  

And it is set (more-so "displayed" in the size you want) in the document you entered the <MiXX:PostIcon runat="server" /> control.

If you are just changing the latter, then most likely it will look funny as the default size stored in the config file is different then your server control sizes.

This is very awesome!

One thing that was causing me a bit of grief until I figured it out, is that the editor was stripping out the domain for the image url.  So rather than http://mydomain.com/photos/test.jpg it was now /photos/test.jpg.  The PostIcon wouldn't generate for urls w/o the domain (either img tags or posticon bbcode).  When I added the domain back to the url for the [posticon] tag, it worked.

I'd love to be able to have it automatically generate posticons from the first img tag in the post, but if it's stripping out the domain, then I'll have to use the bbcode option w/ the entire url which takes some effort to find if using an attachment.

I remember there was a way to force the editor to not strip out the domain, but I kind of like it the way it is.

If the PostIcon could work off of relative urls, that would rock!

Thanks David!

It's the TinyMCE editor that is stripping it out.  And yes, I've thought about making PostIcon support these modified paths.

But actually, TinyMCE only strips out the domain if the domain matches the current website (something I've never agreed in their logic).  If you have another URL (i.e., put a WWW in front of your domain) that should work/let MCE ignore it.

Let us know!

Adjusting how TinyMCE deals with the url is fairly straightforward.

http://wiki.moxiecode.com/index.php/TinyMCE:FAQ

I do have a case where using the relative url is nice though.  That is when working on site redesigns where the new site is being developed under a different (temporary) path.  With the use of relative urls, this allows for content to be added to the site and later switched to it's permanent path w/o having to change the paths in the content.

While we were testing your AWESOME control out, we noticed that on some pages you might need to specify that the "Post" object makes reference to <%# WeblogControlUtility.Instance().GetCurrentWeblogPost(this) %>

Did I mention that this control is awesome, because it is.

Thank you.

@pregamepouncy: Thank ya. Yeah, that would help a bit by grabbing from the Context.  Thanks for the tip!

Will the postIcon work in CS 2.1 as well?