Showing posts with label New Post Editor. Show all posts
Showing posts with label New Post Editor. Show all posts

Thursday, February 2, 2012

Incorrect Orientation Of Photos Uploaded In Post Editor

We see occasional reports of problems with photo orientation, from various blog owners posting in Blogger Help Forum: Something Is Broken.
Why are my photos displayed horizontal, when they should be vertical?
Presumably, if someone's photo was taken with her standing, the blog owner does not want the photo showing her lying on her side.

Modern cameras store meta data with each photo, recording information about how the photo was taken.

This information is called "Exchangeable Image File format", or EXIF, data. Along with the information about date / time / exposure ("aperture" / "F stop" / "shutter speed"), some cameras store whether the photo was taken, with the camera held horizontal or vertical.

Some cameras store the "horizontal" / "vertical" information - then, the Blogger post editor "Upload image" wizard picks up on the orientation, and re orients the photo, depending upon it having been taken "horizontal" or "vertical". If the photo was intentionally rotated, the blog owner does not want the photo rotated again.

There are several possible resolutions for this problem.
  • Use a different camera. Some cameras do not contribute to this problem.
  • Per the comment below, see if the camera has a setting to disable autorotation.
  • Use a photo editor such as IrfanView, and strip out the EXIF data, before uploading. Without the EXIF data, the "Add image" wizard won't reorient the photos.
  • Use a photo editor such as IrfanView, and rotate the photo again, before uploading.
  • Log in to http://www.picasaweb.com, using your Blogger username and password. Find the album, then the picture, that is rotated and open it. Edit the picture - rotate the image, then save it.

Saturday, April 17, 2010

Making Jump Break Work For Blogs With Older Templates

The new Blogger solution for auto summarised posts, also known as "Read More" or "Jump Break", is becoming increasingly popular in Blogger blogs, for several reasons.
  • Auto Pagination resulted in display segmentation, caused by the perceived need to publish hundreds of posts on the main page.
  • Desire to display a dynamic index of posts as the main page.
  • Desire to simply make the main page and / or archive retrieval displays smaller.

The "Jump Break" feature itself is reasonably easy to use, when you are using the New Post Editor, and with blogs that use a template released after Jump Break was released - apparently in September 2009. If your blog was created before then, you may need to add a critical bit of code to the post template.

The simplest way to add the necessary code would be to refresh the post template.

If you have customised your post template, this won't be a good idea. If you want to keep the current post template, and add the critical bit of code, you're going to have to edit the template HTML, and you're going to have to Expand Widget Templates when you edit the HTML.

Instruction from Blogger, in Creating 'After the jump' summaries is pretty simple
After backing up your template, then click the Expand Widget Templates checkbox, and scan your HTML for the following snippet:
<data:post.body/>
Once you've located that code, paste the following snippet directly below it:
<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if >
After you've pasted in the code, click Save and then you're done!

It's possible that such simple instruction may be slightly misleading.

Here's the snippet in question, as seen in the template in my newest test blog, "Chuck's Jump Break Test", with surrounding code to provide a contextual reference.
<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"' expr:title='data:post.title'><data:post.jumpText/></a>
</div>
</b:if>


<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

If you read the above instructions literally, Blogger would have us take an older template
<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

Add the recommended snippet to produce
<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if>

<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

I suspect that the update may be much more correctly installed as
<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if>


<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

Or possibly, you may even want the full, original snippet
<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"' expr:title='data:post.title'><data:post.jumpText/></a>
</div>
</b:if>


<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

So, what is "expr:title='data:post.title'"? Look at my demonstration, hover the mouse cursor over "Read more »", and see.

If you just added the Jump Break to your blog after following the instructions from Blogger, and you followed their instructions literally, you may be observing odd details. It's possible that reports of post / sidebar alignment problems, and odd problems with photos and jump break, may be related to this confusion. You may do well to modify their instructions, when you update your template.

>> Top

Tuesday, March 30, 2010

Spell Check And Video Upload Now Available In New Post Editor

One point of contention, repeatedly echoed in Blogger Help Forum: Something Is Broken, is
Bring back spell checker!
and
Where is the video upload icon in new post editor?
I've been explaining these omissions for a while, and sometimes feel like Sisyphus as I do so.

Well recently, I learned that this may be history sometime soon. If you are able to use Draft (Blue) Blogger, you can now enjoy both spell check and video upload, and new post editor, together. Just remember that the Draft features are only seen if you use the dashboard. If you use the "New Post" link in the navbar, you will get the features of Production (Orange) Blogger - either classic post editor with old photo capabilities, or new post editor without spell check / video upload.

>> Top

Sunday, November 1, 2009

The New Post Editor And Read More

One problem which we seem to see, pretty consistently, in Blogger Help Forum, is where the posts and a sidebar end up in one long column, with one above the other.

Reports like
My posts have vanished!
and
My sidebar (my archives, my Followers, my profile gadget, ...) have dropped to the bottom of the page!
are seen a lot in the forum. Generally, it's caused by trying to put too much in one place.

Recently, though, a few bloggers report the dropped sidebar symptom, after they try the new post editor, and the Blogger "Read More" option (called by Blogger, "Jump Break").

The "Read More" feature in Blogger blogs has been a long needed option.

Before the new post editor, Blogger, and at least 2 other bloggers, had their own competing, and mutually incompatible, procedures for making your blog show, and execute, a "Read More" link. All 3, to my knowledge, had drawbacks. One of the most obvious was that each different version was added by editing the post HTML, and the HTML was complex, and messy.

The "Jump Break" option, in the new post editor, is easy to add.
  1. Add a New Post, or edit an existing post, in Compose mode.
  2. Position the cursor after the words that you want to be always shown.
  3. Hit the "Jump Break" button, in the editor toolbar.
  4. The jump break is inserted into the post editor window.
  5. When you publish the post, you'll see the words that you want to be shown, followed by the link "Read More".
  6. What could be simpler?



(Update 2010/04/17): It's possible that the above instructions from Blogger, if you follow their complete instructions and add Jump Break to an older template, may be slightly misleading. Read their instructions, then read mine, please.


In rare cases, the "Jump Break" button in the toolbar may not work. If you have that problem, go into the "Edit HTML" mode, and insert
<!-- more -->
right where you need your jump break.

For all the simplicity in adding this (either in Compose or "Edit HTML" mode), it's not producing simple results.

There appear to be at least two scenarios where a blog, with one or more posts published with jump breaks, would have a dropped posts or sidebar section.
  1. When the blog displays more than 10 posts in main page view, each post with a jump break, the 11th post will cause this problem.
  2. If the jump break is inserted into the middle of a section of text with formatting implemented using a "<div> ... </div>", a "<div>" section broken by a jump break will cause this problem.


The workarounds to prevent these scenarios are obvious.
  1. Reduce your main page size.
  2. Don't add jump breaks in the middle of "<div> ... </div>" sections.



One possible cause of code containing lots of "<div> ... </div>", a "<div>" would be content composed in Microsoft Word, or another external word processor / desktop layout program. Another, as noted above, may be slightly misleading instructions.

Also, watch out for the third party gadget "Related Posts" LinkWithin. You need this gadget ahead of the "Read More" break (you want your readers to see it without having to display the entire post), but be careful and don't put the "Read More" break in the middle of the LinkWithin code!



But those workarounds may not be popular, or easy to implement.
  1. Some bloggers like to publish blogs with 15, 20, or more posts in the main page.
  2. Blogger who like this new, shiny feature may not be aware of when their posts include "<div> ... </div>" sections. How can they avoid breaking a section that they can't see?



(Update 2010/02/22): This week, we are seeing an incompatibility problem between the new Auto Pagination feature, and the older "Read More" variants. This is resulting in greatly reduced main page and archives page height. It appears that the proper solution is to replace all old "Read More" variants with the new "Jump Break" solution.


>> Top

Friday, July 25, 2008

The Post Editor And HTML Special Characters

Most web pages that you will view on the Internet are written in HTML.

HTML, or Hypertext Markup Language, was designed long ago to enhance simple text, giving it ability to display more than simple letters, numbers, special characters, etc. What you're looking at is mostly simple text. Here, on the other hand, is an example of bold text. And here, italicised text. And here, red text. Are you interested yet?

Here's how I coded the above paragraph in HTML:

Most web pages that you will view on the Internet are written in HTML.<br /><br />HTML, or Hypertext Markup Language, was designed long ago to enhance simple text, giving it characteristics beyond simple letters, numbers, special characters, etc. What you're looking at is mostly simple text. Here, on the other hand, is an example of <span style="font-weight:bold;">bold text</span>. And here, <span style="font-style:italic;">italicised text</span>. And here, <span style="color:rgb(255,0,0);" >red text</span>. Interested yet?


The above paragraph was translated, from the introductory paragraph at the top, by Postable, a web based utility.

You can use Postable, other similar utilities, or Notepad, and convert your HTML to displayable text. When you compose a post, in "HTML" mode, there are several special characters, that you can't enter as simple text.

  • The quote symbol " which must be entered as "&quot;", or "&#34;".
  • The apostrophe ' which must be entered as "&apos;" (If you are reading this in Internet Explorer, you may not see this properly!), or "&#39;".
  • The ampersand & which must be entered as "&amp;", or "&#38;".
  • The less than sign < which must be entered as "&lt;", or "&#60;".
  • The greater than sign > which must be entered as "&gt;", or "&#62;".

When you display HTML code in your posts, you'll have to translate each of these characters as in the above examples - or using the corresponding ASCII numeric codes - if you want your code to be selectively readable as code, in a post.

If you want the entire post to display all special characters as code, you can use the Post Editor "Post settings" feature - Options - "Compose mode", and select "Interpret typed HTML". This lets you display a block of code without requiring special character translation, as above - though it prevents you from using formatting in the post, in HTML mode.

To display "&quot;", "&apos;", "&amp;", "&lt;", or "&gt;", you enter "&amp;quot;", "&amp;apos;", "&amp;amp;", "&amp;lt;", or "&amp;gt;", respectively.

I'll let you figure out how to display "&amp;quot;" "&amp;apos;", "&amp;amp;", "&amp;lt;", or "&amp;gt;".

Now that the post editor in New Blogger June/July 2008 is part of Production Blogger, you can, optionally, display HTML routinely, by a selection in the Post Editor "Post settings". Or, you can still enter special characters in HTML.

Friday, July 11, 2008

New Blogger June 2008 - Displaying HTML

For years, bloggers have complained about the inability / complexity of displaying HTML code in a blog post.

Being told to display "<" as "&lt;" and ">" as "&gt;" confuses many folks - it's not easy typing "&lt;" and "&gt;" - and it's still harder to type "&amp;lt;" and "&amp;gt;", which is how you display "&lt;" and "&gt;", respectively.

Don't ask me to go any deeper.

With the 2008 post editor, we have a new setting, under Post Options.
Interpret typed HTML.


The phrasing there is confusing, to me anyway. What it means, in effect, is that typing "<" will display "<" and ">" will display ">", without any work from us, with "Interpret typed HTML" selected for that post. No more having to type "&lt;" and "&gt;".

In other words, in a single post, you'll be able to copy and paste raw HTML and have it display as raw HTML - if you can make single posts without any HTML, like formatting or links.

This feature may hasten the elimination of the toolbar in "Edit HTML", and make that mode still less usable for composing content. And this should make the New Blogger June/July 2008 Post Editor more attractive, at least slightly so.

Thursday, June 26, 2008

New Blogger June 2008 - The Post Editor

So for the first major overhaul to Blogger since December 2006 (aka "New Blogger 2006"), the Blogger interface has been updated with lots of shiny features. Currently, the new features are visible only in Draft Blogger.

The first change you will notice when you edit your post. In "Compose" mode, you get a shiny new toolbar - similar to what you'll see in GooglePages. Almost the same buttons, almost in the same order. The two attachment buttons - for Photo and Video - have been combined into one labeled "Image", and moved to the left. Full Justification is gone. And spell check is gone (no major loss there IMHO). But most others are there, and in the same left to right order.

The major change that you will see is in "Edit HTML" mode. The toolbar there is gone.

And it's the same crappy small editing window. The one change that we've been waiting for - still somewhere in the distance.

In Blogger In Draft: New Feature: New Post Editor, we see
... there are a handful of other features from the current post editor that are on our to-do list for the new editor. If you rely on any of these, you may not want to use the new editor for everything just yet.


Yet, there are improvements.
  • The well known vertical spacing problem, caused by the "Convert line breaks" setting and use of "Edit HTML" mode, has been eliminated by a more robustly designed post editor, and a new setting which applies in "Edit HTML" mode. The new setting will be found in "Post Options", which makes it settable per post, rather than per blog. Line break sensitive objects in the blog, like lists, preformatted blocks, and scripts, won't be broken any more by extraneous line breaks.
  • The ability to display typed HTML, literally, as HTML, without having to labourously convert each "<" and ">" to "&lt;" and "&gt;", before publishing.
  • An improved picture insertion procedure, with each picture being inserted where the cursor is, rather than at the top of the post.


For a more comprehensive, and optimistic, evaluation, see Roberto's Testing Blogger-in-Draft: Post Editor - Compose Mode.

>> Top

Navigate» Become author for this Blog