Thread

In my case, many of my templates use segment-based switches to decide which content to show. I’ll just make “preview” templates…  That’ll make things easier from a status control standpoint, anyway.

I’d be interesteed in the thought process behind going this route rather than allowing us to create a preview template on a per-weblog basis, to replace the view entry page at the end of publication, though.

Yes, in some cases it may serve you best to make a separate template just for this if you do not already have a template designed to work as a standard single entry template (i.e. a weblog entries tag that gets its information dynamically from the URL).  But you’ll notice (after setting it up) that you do indeed have a Live Look link on the view entry page after publishing as well.  This is basically what this is, though I wouldn’t use the word ‘preview’ because the entry has to exist in the database for this feature to work.

Yes, in some cases it may serve you best to make a separate template just for this if you do not already have a template designed to work as a standard single entry template (i.e. a weblog entries tag that gets its information dynamically from the URL).  But you’ll notice (after setting it up) that you do indeed have a Live Look link on the view entry page after publishing as well.  This is basically what this is, though I wouldn’t use the word ‘preview’ because the entry has to exist in the database for this feature to work.

Right, I’ve just always wanted to be able to customize the view entry page to lay out the post correctly. Mostly because my boss doesn’t quite understand the concept of contextual presentation. If it doesn’t look right on the view entry page, it must not look right on the rest of the site, either. 😊

I’m also not trying to beat you up on the issue, I’m perfectly happy with the way Live Look was implemented for the moment, and my sites upgraded to 1.6.1 with no issues whatsoever. Mitch over at Solspace can tell you, I’m just always going “but what if…”

my favourite: Made current_time available for use in conditionals. this is gold for my calendar!

but! still no pagination for gallery categories :( can I use this opportunity to ask about the difficulty of implementing this feature? It’s hard for me to understand why pagination is everywhere BUT the gallery categories…

my favourite: Made current_time available for use in conditionals. this is gold for my calendar!

but! still no pagination for gallery categories :( can I use this opportunity to ask about the difficulty of implementing this feature? It’s hard for me to understand why pagination is everywhere BUT the gallery categories…

I paginate my gallery categories....

Wow, can I just say - “Live Look” - thank you, thank you, thank you.

Quite the update fellas, especially for a third decimal version.

my favourite: Made current_time available for use in conditionals. this is gold for my calendar!

but! still no pagination for gallery categories :( can I use this opportunity to ask about the difficulty of implementing this feature? It’s hard for me to understand why pagination is everywhere BUT the gallery categories…

I paginate my gallery categories....

lisa, would you mind sharing how you did that? as you can see my category list desperately needs one 😊

lisa, would you mind sharing how you did that? as you can see my category list desperately needs one 😊

Bobh, I have a question for you - how did you do your thumbnails?

Make a new post in how-to, I’ll post my code there. =)

Make a new post in how-to, I’ll post my code there. =)

thanks, looking forward to it!

oldgoldblack, I’ll PM you to avoid a total hijack of this thread.

It’s not even Christmas yet!  I think this is my favorite update ever.  I’m so excited to try out Live Look.  I didn’t get even a quarter of the way down the list.  Amazing.  Thank you!

EE 1.6.1 really has some great additions and upgrade went smooth as ever. Thanks a lot!

But may I suggest updating the build forum more frequently? I did run into the RSS problem which did cost some time until I found the new build (that addresses the bug) by accident only.

-Markus