Dynamic Templates, And Improved "Follow by Email"

We see some concern about providing email subscriptions, from blog owners in Blogger Help Forum: Get Help with an Issue.

How do I provide email subscriptions for my blog? Neither Follow by Email or Subscription Links works, for email!

The blog in question is using a dynamic template. In some cases, even "Subscription Links" does not provide a "Subscribe by Email" option - and it appears that the blog owner is really out of luck.

The "Subscribe by Email" gadget does not work, with dynamic templates - and some dynamic templates don't support the "Subscription Links" gadget with "Subscribe by Email" added.

Add "Subscription Links" to a blog with a dynamic template - for some blogs.

In some cases, you may not even want to use "Subscription Links". You can, however, use a LinkList gadget, to do the same thing - and to make an improved "Subscription Links" gadget.

In this case, add "Subscribe by Email" as a linklist gadget.

Just add the "Subscription Link Code", in a linklist gadget. Here is the code, from the FeedBurner Publicize dashboard page, for my blog, Chucks Musings.

The "Subscription Management" page, and "Subscription Link Code".



Add the link caption as "New Site Name", and the link code as "New Site URL".

<a href="https://feedburner.google.com/fb/a/mailverify?uri=ChucksMusings&loc=en_US">Subscribe to Chucks Musings by Email</a>

The "Subscription Link Code" caption, and link.



Just add a new LinkList gadget.

• New Site Name: Subscribe to Chucks Musings by Email
• New Site URL: https://feedburner.google.com/fb/a/mailverify?uri=ChucksMusings&loc=en_US

Copy into a LinkList.



Click "Add Link" - then "Save" - and finally, "Save arrangement".

And we have a new sidebar accessory.

And if you click on the link, you get the FeedBurner "Email Subscription Request" verification form.



So, either add "Subscription Links" - or make a custom LinkList accessory. One, or the other, will give you "Subscribe by Email", in a dynamic template.

---

Some #Blogger blogs, which use a dynamic template, won't display "Subscribe by Email" as an added option, in "Subscription Links". Or, in some cases, you may actually want a more robust "Subscribe by Email" - or "Subscribe" menu.

In this case, add a LinkList gadget - and add the subscription form as a FeedBurner hosted form, using "Subscription Link Code".

Read More

Atom Vs RSS - Choose One, Using FeedBurner

Occasionally, we see a blog owner in Blogger Help Forum: Learn More About Blogger, asking about newsfeed formats.

Which is better, for my readers - Atom or RSS? How do I choose, what to provide, in my blog?

The competing newsfeed formats - Atom and RSS - have been a part of Internet life, for many years. Both formats have their devotees - and this is why there are two formats.

Both formats have their own advantages - and disadvantages.

You can change the URL of a FeedBurner source feed, to select Atom or RSS feed formats, from your blog.

You can use FeedBurner, or edit the blog template, to select a feed format.

Use the FeedBurner "Edit Feed Details" wizard, if you redirect your blog feed to FeedBurner.

If you don't use FeedBurner, you can edit the blog template, and manually change feed URLs. Note this will involve editing the post template, to change some links in the blog. This is not a recommended solution.

You may choose from 5 blog posts feed URLs, provided by this blog. You can do the same, with your blog.

• Atom (classic): http://blogging.nitecruzr.net/atom.xml
• RSS (classic): http://blogging.nitecruzr.net/rss.xml
• Atom (autodiscovery default, new): http://blogging.nitecruzr.net/feeds/posts/default
• Atom (new): http://blogging.nitecruzr.net/feeds/posts/default?alt=atom
• RSS (new): http://blogging.nitecruzr.net/feeds/posts/default?alt=rss

Do you really want to select Atom or RSS this way?

FeedBurner has two services, that let you mix and match Atom vs RSS.

• SmartFeed dynamically serves the right choice - Atom vs RSS.
• Convert Format Burner lets you statically select one format, or another.

Using either service, FeedBurner selects the desired feed format for you - regardless which Original Feed URL you provide, in "Edit Feed Details". Just give FeedBurner the default feed URL for your blog " ... /feeds/posts/default" - and let FeedBurner do the work, depending upon the service that you select.

You activate either service from the FeedBurner dashboard "Optimize" tab. Note that you should choose only one service, for each FeedBurner feed provided.

Important: We recommend not using this service if you use SmartFeed. SmartFeed will override any Convert Format settings in order to make your feed compatible with all feed readers, whether they support Atom, RSS, or both.

"SmartFeed" selects the best format, dynamically.

For the best experience by all readers, SmartFeed will automatically provide the feed format favoured by any feed reader used - as each reader views your feed.

Translates your feed on-the-fly into a format (RSS or Atom) compatible with your visitors' feed reader application.

Enable SmartFeed - and let FeedBurner choose the best format, for each different feed reader being used.



"Convert Format Burner" lets you choose the format - and version.

If the choice of feed format (Atom, RSS) - and even choice of format version (Atom 0.3, Atom 1.0, RSS 1.0, RSS 2.0) - matters to you, you can use Convert Format Burner, and select a specific format and version.

Nine flavors of RSS and now two formats of Atom ... who has time to keep track of it all? FeedBurner does! Let us convert your feed to any of the format choices listed below.

Enable Convert Format Burner - and you choose what feed format and version gets served, to all feed readers.



You can have multiple feeds, and multiple FeedBurner outputs.

If you have conflicting requirements, you can always setup multiple different FeedBurner feeds - and use different feed service options, for different feeds. You can then provide each feed in a consistent display, using the "BrowserFriendly" service.

---

If you want to serve the right newsfeed format from a #Blogger blog, you can either tweak the code in the blog template - or you can use a #FeedBurner feed, and activate the "SmartFeed" or "Format Burner" service. Using FeedBurner is a simpler choice, than the template editor.

Read More

FeedBurner Feed Redirection, And "BrowserFriendly"

Some blog owners and readers ask about blog feed displays, in Blogger Help Forum: Get Help with an Issue.

I clicked on this text at the bottom of the blog page:

Subscribe to: Posts (Atom)

and I got a screen full of gibberish.

This is a known oddity, in Chrome.

The Chrome browser, unlike Firefox or Internet Explorer, lacks a built in newsfeed reader.

If you, the blog owner, want to see a useful display of blog content, when you click on "Subscribe to: Posts (Atom)", you can do that. Just add a Chrome extension, such as "RSS Subscription Extension (by Google)".

With the right extension added to Chrome, you will see blog content - instead of a screen full of gibberish. But what about your readers?

Give your readers a consistent and useful newsfeed display page.

If you want your readers to see useful content - plus a toolbar that helps them subscribe, using email or a feed reader, you can setup a FeedBurner feed, and add the BrowserFriendly service.

Just activate BrowserFriendly, from the FeedBurner Optimize page. Then, select the BrowserFriendly options that interest you.

You can choose from a number of popular feed readers to support, or add your own.



If you have Email Subscriptions added, your readers will have a selection for that, in the BrowserFriendly display.

NOTE: Because you use FeedBurner Email Subscriptions, a link to subscribe via email will automatically appear with your subscription selections.

You can add the original blog feed, to BrowserFriendly.

For more consistent reader statistics and subscriptions, you can make sure that the BrowserFriendly display uses the original posts newsfeed.

If you have configured your web server to redirect from your old feed to your new one, you should tell subscribers to use your old, redirected address so that the redirect can work its magic and subscribers always use that address, but FeedBurner tracks 100% of your traffic. FeedBurner will always show that address to potential subscribers instead of the FeedBurner feed address in BrowserFriendly.

Click on "Use your redirected feed URL on your BrowserFriendly landing page", to open the "BrowserFriendly" Redirected Feed URL setting wizard.



Copy the "Original Feed" URL from "Edit Feed Details" into the "Redirected Feed URL".

BrowserFriendly gives all readers, ignoring the browser, a good subscription page.

Whether your readers use Chrome, Firefox, or Edge / Internet Explorer, you can have them using the FeedBurner BrowserFriendly newsfeed display, and subscription wizard. All of your readers will have a more consistent access to your blog feeds and subscription options - and you'll have a happier reader community.

Complementing BrowserFriendly, you may wish to look at SmartFeed and Format Burner, to provide the right feed format. And if any of these ideas create conflicting needs, you can use multiple FeedBurner feeds.

---

With a #Blogger blog that uses email / newsfeed subscriptions to attract and encourage readers, you can provide a more consistent subscription display for your reader community, by using #FeedBurner and the BrowserFriendly service.

Read More

Avoid Use Of FeedBurner "Password Protector"

Some Google products contain features that have limited usefulness, when applied to Blogger blogs.

FeedBurner has a feature, "Password Protector", which may be useful, to newsfeed readers that support HTTP authentication. Within FeedBurner, we have the "Email Subscriptions" service - which does not support feed authentication.

Your readers will be required to use newsreader or aggregator software that supports authentication to view your feed.

Some Google, and non Google, services will have a problem, with a FeedBurner protected feed.

Newsfeeds, published by Blogger blogs, are supposed to be publicly accessible.

A blog with designated readers will not produce a newsfeed. Blogger does not support authenticated newsfeeds.

To use Password Protector, look on the FeedBurner dashboard, under the Publicize tab, for "Password Protector". Enter a Username and a Password, and hit "Activate". But don't do this, without knowing the downsides.

Password Protector uses a single username / password combination. All blog readers will use the same username.

FeedBurner warns us of possible problems, caused by this service.

Important: This service prevents our Email Subscriptions service from delivering email updates from your feed, and it will also password protect your feed's content when redisplayed using our Headline Animator graphic. This graphic itself becomes password protected, which is undesirable if you wish to use it to promote your site/feed. Therefore, we recommend not using Headline Animator or Email Subscriptions, and this Password Protector service, with the same feed.

From what I can see, Blogger Reading List may ignore the authentication requirement. People may use Reading List, and view the blog feed, redirected through FeedBurner - even if not authorized.

We know, however, that email subscriptions will not work, with a protected feed. Looking at an HTTP trace of the feed from my test blog http://techdict.nitecruzr.net, we see a symptom of the problem, with this option.

http://techdict.nitecruzr.net/feeds/posts/default

http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://techdict.nitecruzr.net/feeds/posts/default&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO

Sending request:

GET /feeds/posts/default HTTP/1.1
Host: techdict.nitecruzr.net
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7834.70.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.28.121

• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:

HTTP/1.1·302·Found(CR)(LF)
ETag:·W/"32e869db-18a9-4ccf-8ad9-dbded29f2b25"(CR)(LF)
Date:·Wed,·27·Apr·2016·15:04:06·GMT(CR)(LF)
Content-Type:·text/html(CR)(LF)
Server:·blogger-renderd(CR)(LF)
Expires:·Wed,·27·Apr·2016·15:04:07·GMT(CR)(LF)

Cache-Control:·public,·must-revalidate,·proxy-revalidate,·max-age=1(CR)(LF)
X-Content-Type-Options:·nosniff(CR)(LF)
X-XSS-Protection:·1;·mode=block(CR)(LF)
Location:·http://feeds.feedburner.com/ChucksTechWorld(CR)(LF)

This appears to be just a redirected blog posts newsfeed, targeting a FeedBurner published feed.

Here, we see a normal redirected blog posts feed.

But what happens, when we try to open the feed?

http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://feeds.feedburner.com/ChucksTechWorld&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=TXT

Sending request:

GET /ChucksTechWorld HTTP/1.1 HTTP/1.1

Host: feeds.feedburner.com
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7834.70.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 172.217.0.14

• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:

HTTP/1.1·401·Unauthorized(CR)(LF)

WWW-Authenticate:·BASIC·realm="FeedBurner·feed·ChucksTechWorld"(CR)(LF)

The "HTTP Viewer" service does not support feed authentication (and only works with "HTTP:" protocol). And, we see the result.

It's possible that this feature will be useful, with feeds that are used outside Blogger (noting the Reading List ability). If you're publishing a Blogger blog, however, you're not likely to get any useful result.

---

Owners of #Blogger blogs, which use the FeedBurner "Password Protector" service, may find that the service delivers less protection - and some interference - other than the service name suggests. It would probably be best to avoid use of this service.

Read More

Blogger Magic - Check / Edit FeedBurner Feed Details

Whenever you have a problem with FeedBurner - or need to change details, the "Edit Feed Details" wizard is an essential tool.

It's a very simple display - just 3 data elements - but it's a pretty useful 3 elements, if you use FeedBurner with your blog..

The FeedBurner "Edit Feed Details" wizard is an essential tool, when researching a FeedBurner problem.

Start from the FeedBurner "My feeds" display - and select a feed in the list.

"Edit Feed Details" is at the top of the feed dashboard.

Start from the feed dashboard.

Click on "Edit Feed Details".

And there is the "Edit Feed Details" display.



Here, you can view, and edit:

• Feed Title.
• Original Feed URL.
• FeedBurner Feed URL.

Feed Title.

You can change the feed title here - or in the service settings.

Optimize - Title/Description Burner lets you change to title used in the feed itself. Publicize - Email Subscriptions - Email Branding lets you change the title used in the email based feed service.

You may want to check the blog title, also.

Original Feed URL.

If you change the URL of your blog, or want to use a different blog, you can use the FeedBurner Feed URL ("Original Feed") to make the change transparent, to everybody who Follows your blog using a FeedBurner service. The original feed URL may change - but the FeedBurner Feed URL does not have to change.

FeedBurner Feed URL.

Besides changing the title, you can change the feed URL ("Feed Address"), if you need.

Simple changes / powerful results.

These are simple changes - that can have powerful results.

---

Any #Blogger blog owner who uses #FeedBurner to distribute / modify content of a newsfeed, or an email subscription, needs to know and use the "Edit Feed Details" dashboard wizard. The ability to change the feed title, the blog feed URL, and / or the FeedBurner feed URL, at will, makes this a useful wizard.

https://productforums.google.com/d/topic/blogger/oUYseDHCerU/discussion

Read More

Blogger Magic - FeedBurner Email For Your Blog

Some people who will enjoy your blog may prefer to follow it using their email.

It's not difficult to setup email delivery of the comments or posts - from various source selections. FeedBurner offers a wide assortment of delivery options, for the many sources.

Blogger offers the "Subscribe by Email" gadget and service, which delivers the posts newsfeed. That's one feed possibility - and you can have many more, with very little work.

Using the many options provided by FeedBurner, combined with the many feed possibilities, you can produce a generous set of email subscription options.

1. Setup a FeedBurner feed.
2. Activate the "Subscribe by Email" service, for the feed.
3. Add a FeedBurner form, to the blog.

Setup a FeedBurner feed.

To add a standard blog posts subscription, add a "Subscribe by Email" gadget (for blogs with non dynamic Blogger templates) - or a "Subscription Links" gadget (for all blogs, including those with dynamic templates).

The standard blog posts subscription is not the only possibility. You can setup a FeedBurner feed for any blog published feed - including various label based feeds.

Start with the URL of any blog native feed.

Give the feed an Address and a Title.

The feed is setup. Proceed to the dashboard, to Activate the feed.



Activate the "Subscribe by Email" service, for the feed.

Activate "Email Subscriptions", for the FeedBurner feed that you setup.



From the FeedBurner dashboard Publicize - "Email Subscriptions" - "Subscription Management" page, Activate the "Email Subscriptions" service, for the feed.

The service is active - now check out other options.



With the "Email Subscriptions" service activated, look at the various formatting and distribution options available.

Add a FeedBurner form, to the blog.

You can use the form provided with "Subscribe by Email", if you are setting up the standard blog posts feed. For any other feed, you can use either form provided on the "Subscription Management" page, installed as an HTML / JavaScript gadget.

If you want to be fancy, you can make a fixed location ("floating") subscription icon.

Just use your imagination.

FeedBurner presents you with endless choices, for letting your readers enjoy your blog from their Email inboxes. Think about what will look good on your blog - and what will interest your readers.

---

Not all #Blogger blog owners know how easy it is to use #FeedBurner email delivery, to provide your readers the option to view your blog - in many content options - using their email inboxes.

Read More

Add A Fixed Location "Subscribe" Button To Your Blog

To encourage email subscriptions, and other social connections, some blog owners provide gadget toolbars, with useful links.

Some blog owners would like to position their gadgets in fixed screen positions.

I want to have a subscribe button hover at the top of the page, while people read my blog.

This blog has a hovering AddThis toolbar, which provides selected social sharing options. And, it has a hovering "Top of Page" button.

Adding a custom subscription gadget, in a fixed screen location, is not complicated.

AddThis has a large library of social sharing gadgets, with their icons - but they don't have any email subscription selections. But you can add an icon based "subscribe" button, "hovering" at the top of the page.

An occasional request suggests using a popup window, containing a subscription form. We don't recommend using a popup window - but a subscription form, on a FeedBurner hosted page, will provide the same function.

1. Add FeedBurner "Subscribe by Email".
2. Add a "Subscribe by Email" FeedBurner hosted form, and a link.
3. Add a suitable icon, containing the FeedBurner subscription link.
4. Try It.

See below "Try It.", for the detailed procedure.

Add FeedBurner "Subscribe by Email".

Using the dashboard Layout page, and "Add a Gadget", add a "Subscribe by Email" gadget. This creates a blog posts FeedBurner hosted feed.

FeedBurner provides the "Subscribe by Email" gadget, with the choice to display either an on screen form - or a simple link to a FeedBurner hosted form page.

Add a "Subscribe by Email" FeedBurner hosted form, and a link.

Once a "Subscribe by Email" gadget has been added, get the gadget link from the FeedBurner dashboard, at Publicize - "Email Subscriptions" - "Subscription Management" - "Preview Subscription Link…".

Start from the dashboard, at Publicize - "Email Subscriptions" - "Subscription Management".

The "Preview Subscription Link…" window contains the code, that we need.



Add a suitable icon, containing the FeedBurner subscription link.

Choose an attractive icon to contain the FeedBurner supplied link. Add an HTML gadget using "Add a Gadget", containing the icon with the link to the FeedBurner form - and displayed in a fixed location.


Try It.

I added a button, and a new subscription, to my test blog, "Chucks Tech World".

See the icon, in the top right margin?

See how the new icon floats?

See how it floats from the top - and from the right?



Start with an icon, uploaded:

<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiH-R3uaQFsSkF7azHhm7XAnONPpN0QRrpZ0hhW9S0Y5AqdP3Ar3iopGgFViycf75jvJ-tcpRgd_sSJsGrdb-qHCRsJtyMcq_1dQ7RfZnlhbEveDjdAYj16U6TrBivx0ym6VfzLJwQtT9Fk/s1600/Subscribe+Icon.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiH-R3uaQFsSkF7azHhm7XAnONPpN0QRrpZ0hhW9S0Y5AqdP3Ar3iopGgFViycf75jvJ-tcpRgd_sSJsGrdb-qHCRsJtyMcq_1dQ7RfZnlhbEveDjdAYj16U6TrBivx0ym6VfzLJwQtT9Fk/s320/Subscribe+Icon.png" /></a>

Here's the FeedBurner Subscription Link:

<a href="https://feedburner.google.com/fb/a/mailverify?uri=ChucksTechWorld&loc=en_US">Subscribe to Chucks Tech World by Email</a>

Here's the Floating Top Of Page Button:

<a style="display:scroll;position:fixed;bottom:20px;right:60px;" href="#" title="Top"><img border="0" height="60" width="60" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEik2HLf375pL7ukmgwXSv3ti2luCRyGVIsZEL5d6FGjrsfaN_HYL8vy8Jr1BNRzB6cRoLeBP_JSX5r6FX8l7tjV5fkOdQU3ISmbtwLORtbbwnHACD1QWmEPawWFylh4lCixVTPGc2tpaRhA/s320/Up+Arrow+4.jpg" /></a>

And put them all together:

<a style="display:scroll;position:fixed;top:40px;right:60px;" href="https://feedburner.google.com/fb/a/mailverify?uri=ChucksTechWorld&loc=en_US" title="Subscribe by Email" target="_blank"><img border="0" height="60" width="60" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiH-R3uaQFsSkF7azHhm7XAnONPpN0QRrpZ0hhW9S0Y5AqdP3Ar3iopGgFViycf75jvJ-tcpRgd_sSJsGrdb-qHCRsJtyMcq_1dQ7RfZnlhbEveDjdAYj16U6TrBivx0ym6VfzLJwQtT9Fk/s320/Subscribe+Icon.png" /></a>

And that's it.

I now have a hovering subscription icon, in my test blog. Given a collection of icons, carefully arranged, you can have a hovering toolbar - to maybe complement a social media button toolbar.

---

Some #Blogger blog owners would like a hovering button or toolbar, to provide an email subscription form. This is an accessory that is not difficult to add.

Read More

Dynamic Templates, And "Follow by Email"

We see occasional concern about providing email subscriptions, from blog owners in Blogger Help Forum: Get Help with an Issue.

How do I provide email subscriptions for my blog? Follow by Email does not work!

The blog in question is using a dynamic template - and it appears that the blog owner is out of luck.

The "Subscribe by Email" gadget does not work, with dynamic templates.

Add "Subscription Links" to a blog with a dynamic template.

For email subscriptions, and a blog with a dynamic template, you use the "Subscription Links" gadget. Here is my blog, Chucks Musings.

Use "Subscription Links" with a blog that has a dynamic template.



When you add "Follow by Email" to a blog with a non dynamic template, it sets up the "Email Subscriptions" service, in FeedBurner. "Subscription Links" is a collection of various subscription services - and won't activate "Email Subscriptions".

You may need to activate "Email Subscriptions".

You will probably need to activate the "Email Subscriptions" service, to use "Subscription Links" instead of "Follow by Email".



To use "Subscribe by Email" as a selection in "Subscription Links", be sure that the "Email Subscriptions" service is activated, from the FeedBurner dashboard.

Alternately, add "Subscribe by Email" in a linklist gadget.

Sometimes, you may not want to use "Subscription Links". So, just add the "Subscription Link Code", in a linklist gadget.

Here, we have a new sidebar accessory.

And when you click on the link, you get the familiar FeedBurner "Email Subscription Request" verification form.



So, either add "Subscription Links" - or make a custom LinkList accessory. One, or the other, will give you "Subscribe by Email", in a dynamic template.

---

Owners of #Blogger blogs, wishing to provide email subscriptions, find that "Follow by Email" won't work with a dynamic template. Fortunately, "Subscription Links" will provide email subscription - though the necessary FeedBurner service has to be activated.

https://productforums.google.com/forum/#!category-topic/blogger/lsAVQuj_FOw

Read More

Correct Your Post, After Using MS Word

Sometimes, advice provided in Blogger Help Forum: Get Help with an Issue, comes too late.

Telling people to avoid use of MS Word, for composing posts, is one example of "too late". But maybe this delinquency can be repaired.

Blogger provides the the page / post editor "Remove formatting" tool ("Tx"), for removing unwanted formatting.

When you've just published your post - and can't figure out why the formatting is all whacky - or maybe you can't get the post successfully passed through a FeedBurner feed - the most obvious way to correct the post is to use Notepad, or a similar text editor.

But that's a pain, and it's rather complicated. Maybe there's an easier solution.

Like an over edited post - or a victim of too much switching between Compose and HTML modes - the "Remove formatting" tool ("Tx") might save you, here.

Select everything in the page / post.

And use the editor "Remove formatting" tool ("Tx").


As in the previous example, you may have to spend a few hours adding essential formatting back. But with MS Word meta formatting, aren't you better off getting rid of all of that, at once?

---

Some #Blogger blog owners publish posts full of junk meta formatting, courtesy of MS Word - then look for a quick solution. Copying out then back, using Notepad / WordPad, or a similar text editor is the most obvious solution - but it's a painfully complicated one.

Maybe this is another case when the page / post editor "Remove formatting" tool can save the day.

Read More

BlogLovin Has Problems With Some Blog Feeds

We see occasional reports, in Blogger Help Forum: Get Help with an Issue, from Blogger blog owners who want to share their blogs using BlogLovin.

Why can't I claim my blog?

BlogLovin is somewhat monolithic. They use the blog feed, and a BlogLovin URL with embedded token, to process / validate blog claims - and their diagnostics, when a claim is a problem, are not always effective.

Some blog feeds can be validated, yet not be found by BlogLovin. And other feeds won't validate.

Blog owners have reported several common problems, when trying to claim their blog with BlogLovin.

• Start with the published blog URL.
• Empty / very short feeds.
• Redirected feeds, generally involving FeedBurner.
• Feeds containing GeoRSS datapoints.
• Feeds with content formatted in Microsoft Office.
• Positioning the claim verification link / token.

Start with the published blog URL.

Even though BlogLovin uses the blog posts newsfeed for content source, when you claim your blog, you need to use the published URL. You do not specify the feed URL. BlogLovin finds the feed URL from the blog header - after you give it the published URL of the blog.

Feeds can be validated, using either the W3C Feed Validator, or the FeedValidator.org Feed Validator. You have to use the right W3C validator, though.

If the blog is published to a custom domain, the published URL - and the feed - will be most consistently accessible to BlogLovin when the domain is properly setup. Bogus DNS addressing, or poorly setup domains, will cause feed access issues - and BlogLovin won't process your claim.

Empty / very short feeds.

An empty or very short feed just does not contain enough material, for BlogLovin to reliably claim a blog.

It's best to let your blog mature slightly, before trying to use it with BlogLovin. Half a dozen good posts are better than just one or two, when claiming a blog.

Redirected feeds, generally involving FeedBurner.

A FeedBurner redirected feed looks completely different from a native Blogger feed. If you're going to use a Blogger blog in BlogLovin, it's best to use a non redirected version of the feed for your blog.

Feeds containing GeoRSS datapoints.

A feed from a blog that includes a GeoRSS datapoint will fail validation.

GeoRSS will disrupt BlogLovin, and cause problems with FeedBurner. If you want to use either service, you have to edit any post using GeoRSS, and remove the GeoLocation element.

Feeds with content formatted in Microsoft Office.

A Microsoft Office formatted blog will produce a validated feed - yet BlogLovin and FeedBurner will both have problems, when using the feed.

We've been dealing with Microsoft Office generated problems, in various Blogger features, for years. BlogLovin is one more service where Microsoft Office formatted posts just don't work.

Both the W3C and FeedValidator.org feed validators are generally used, to diagnose non claimable blogs.

But neither is 100% useful, when there's a problem. Some blogs with valid feeds still can't be claimed.





Use the right validator.

You do need to use the right W3C validator, when checking the feed for your blog. Some BlogLovin diagnostic instructions may mention the wrong validator.

W3C provides 2 validator services.

This is for HTML / XML Markup Validation:

http://validator.w3.org/

This is for Feed Validation:

https://validator.w3.org/feed/

If you use the Markup Validator, with a blog feed, you're going to see a lot of irrelevant errors. You have to use the Feed Validator.

Use a properly coded template.

Some blogs cannot be claimed, because BlogLovin cannot detect a feed. If your blog lacks the necessary header records in the template, your blog cannot be claimed.

This problem is not caused by BlogLovin. This is a problem caused by you, using a custom template that lacks the necessary template content.

BlogLovin does have a good Help contact page, though.



Positioning the claim verification link / token.

BlogLovin suggests publishing a new post, with the claim link / token at the top of the post - or alone. I found that the link, added to an HTML gadget, and positioned in the sidebar, works - and makes more sense than cluttering the blog posts newsfeed with a gratuitous post containing a claim link.

Proper positioning of the claim link - whether in a post or the sidebar - is also essential to the success of the claim process.

As last resort, contact BlogLovin Support for help.

If you just can't get your blog claimed, you can contact BlogLovin Support - or you can read the BlogLovin Help database.

---

Some #Blogger blog owners use BlogLovin as a social sharing platform. Unfortunately, not every blog owner can successfully claim their blog, in BlogLovin, immediately.

BlogLovin has several possible problems with Blogger blogs - and not all problems are well known.

Read More

Follow By Email, And Read More Solutions

Some blog owners use email, to distribute blog content - and like the post summarisation technique, Jump Break.

We see occasional hopeful questions, in Blogger Help Forum: Learn More About Blogger, about Jump Break, in emailed post content.

How do I use Jump Break, in my posts email subscriptions?

This is one need that probably won't be solved, precisely as requested.

Jump Break is simple enough, to add to the blog - one post at a time. To work, from an index page, it needs 2 components.

• A summarised post segment, with the "Jump Break" token, <!--more-->, in the index page display.
• A post, with the "more" anchor embedded.

The "Read More" target URL is easy enough to pass, and to use, in email.

Here's the "Read more" URL, from a previous post.

http://blogging.nitecruzr.net/2016/01/dear-followers-of-this-blog.html#more

The Jump Break token isn't easily interpreted, outside the Blogger environment.

The "Read more" URL is easy to pass, in email distributed blog feed. The "Jump Break" token, unfortunately, is not properly interpreted. Email displays can't handle control strings, such as

<!--more-->

or

<a·name='more'></a>

But you can use an alternate "Read More" feature.

If the blog can use FeedBurner Email Distribution, however, you can get FeedBurner to format a post summary. A post summary uses a truncated "teaser" post, truncated before the post is distributed - instead of Jump Break, interpreted when the post is viewed.

There are 2 possible ways to use "Read More", instead of "Jump Break".

You have 2 possible solutions here.

1. Setup a FeedBurner feed, based on the feed summary.
2. Setup a FeedBurner feed, based on the full feed - and use the Summary Burner option.

I setup 2 test feeds, from this blog.

1. The Real Blogger Status - Summary Option 1.
2. The Real Blogger Status - Summary Option 2.

You may click on either or both - and examine / compare the results. The first is based on the summary posts newsfeed, as coming from this blog, and simply redistributed by FeedBurner - and the second is based on the full posts newsfeed, as coming from this blog, and summarised then redistributed by FeedBurner.

You may subscribe to either, or both, feeds - and see what you get, in your Inbox.

1. Subscribe to The Real Blogger Status - Summary Option 1 by Email.
2. Subscribe to The Real Blogger Status - Summary Option 2 by Email.

Both "Read More" solutions are easy enough to setup, using FeedBurner.

Setting both feeds up was rather simple.

1. The "Feed Summary" solution is simply a standard FeedBurner Email Distribution, sourced from "/feeds/posts/summary".
2. The "Summary Burner" option is simply a standard FeedBurner Email Distribution, sourced from "/feeds/posts/full" - and "Summary Burner" activated, with a "teaser" of 400 characters.

Activate Summary Burner from the Optimize tab.



You activate the "Summary Burner" service, from the dashboard Optimize tab. If necessary, setup a second FeedBurner feed.

Option 2 (Summary Burner) lets you adjust the "teaser", and the caption. That's the only choices - and the only challenge.



If you compare the two options, you'll notice that Option 1 is simply a fixed "teaser" of 400 characters - and that Option 2 gives you an adjustable "teaser", plus a caption of your choice. With both options, the link to the full post is in the post title.

So, it's a toss up. I'd probably go with option 2, which is more adjustable - but it's your choice, for your blog. It takes less than a minute, to change from one to the other.

Read More

FeedBurner, And Blogs Unwisely Deleted Or Renamed

Some blog owners delete or rename a blog, without proper planning - and later regret their action.

Some spammers track blog name availability - particularly with blog names that contain "English" (and some non English) language words. If a spammer discovers that a given blog name has recently become available, he will publish a stub blog to that name - and later, add spammy content.

Why is a spammer interested in recently available names?

A previously unavailable name, now available, has residual value - because it previously had content, and presumably, readers.

If a valuable blog name is made available by the owner, a spammer will take it.

If a blog owner just abandoned a valuable blog name, by deleting or renaming the blog, a spammer is going to make good use of it.

The unwary blog owner will soon get complaints, from former subscribers.

Shortly, the unwary blog owner will see that his blog, recently deleted or renamed, has been re published and is now full of spam. His former readers are now asking why he is filling up their blog feeds with spam. And he has lost control of the blog, that once was his.

Unfortunately, by the time the republished blog name is discovered, the spammer has taken legal control - and is now the rightful owner. And, short of deleting the blog as a TOS violation, Blogger will recognise the spammers right to own a blog that was legally obtained, using a spammer version of "Create blog".

If the unwary blog owner is you, you may be able to correct your mistake.

If a deleted or renamed blog used FeedBurner to distribute a blog feed, it's possible that the remaining readers are subscribed to the FeedBurner feed. This is where you - the formerly unwary blog owner - can correct your mistake.

A hacker / spammer, who now (legally) has control of an abandoned blog, may not have control of the FeedBurner feed, that is feeding from the blog. If you can regain control of the FeedBurner feed, you can redirect it to a different blog.

1. Setup a stub blog, with one or more posts explaining your mistake.
2. Edit the FeedBurner feed, to point to the feed from the stub blog.
3. Publish a post or two, as an apology to your former subscribers.

Setup a stub blog, with one or more posts explaining your mistake.

You cannot do what you should have done originally - publish a stub blog to the abandoned blog name. You can, however, publish a stub blog to any other available and suitable name.

Then add a post, explaining what you did - and why the people reading the new blog (your new stub blog) are (or just previously were) seeing spam, in their bloglists and Reading List.

Edit the FeedBurner feed, to point to the feed from the stub blog.

With a new blog publishing an active feed, edit the FeedBurner feed that is currently re publishing the feed from the spammer owned blog. Change the FeedBurner feed, using "Edit Feed Details", to re publish the feed from your new stub blog.

The current FeedBurner feed, for
The Real Blogger Status, is
http://feeds.feedburner.com /Nitecruzr-Blogging



To change the feed source URL, simply edit the "Original Feed" setting - then click "Save Feed Details".

Publish a post or two, as an apology to your former subscribers.

With your FeedBurner feed now re publishing your new stub blog, publish a post or two explaining what you did. Hopefully, given a couple posts from your (reclaimed) feed that do not contain spam, your former readers may read one of your new posts, and be enlightened.

And the spammer will be none the wiser - until the people who are paying him report that his former spam channel has stopped producing traffic to their website.

---

FeedBurner Feeds, After Deletion / Renaming Of Blogs
FeedBurner Feeds, After Unwise Blog Delete / Rename
FeedBurner, After Blog Unwisely Deleted / Renamed

If you unwisely delete or rename a #Blogger blog, the name that was once yours will have some value to a spammer. If a spammer takes the abandoned blog name, publishes his own spammy content, and distributes it to you former readers, you will be powerless to do anything.

If you are using a FeedBurner feed to distribute the blog feed, however, you can edit the FeedBurner feed, and cancel the spammers channel.

Read More

Confusion About The Post Feed Redirect Feature

The world of Blogger blogs contains a lot of confusing terminology.

Some Blogger features don't even have names. Some names, which I use, are terms which I made up on my own, years ago - simply because Blogger did not provide a name, at that time. One term, which Blogger did give us, still causes confusion. The term "Post Feed Redirect" seems to describe an option, in Blogger, to redirect the post feed to a different URL.

The Post Feed Redirect feature is used by some confused blog owners, improperly.

There are several specific cases, all too common.

• Change the URL of the feed. Redirecting the blog feed, to simply change the URL, causes the feed to redirect to non existent content - or a dead feed.
• Publishing the blog to a non BlogSpot URL. Custom domain publishing provides automatic redirection of the blog URL - and by extension, the blog feed URL. Adding a feed redirect causes an infinite loop.
• Randomly expose the blog to new audiences. Redirecting the blog feed to a random redirector causes the blog readers to report a hijacked Reading List - and later, to simply remove the blog, using a redirected feed, from the Reading List.

This redirection, contrary to the term "Post Feed", also affects the comments feeds and the labels feeds, relevant to the blog where the setting is used.

Besides the fact that the option in question affects all feeds in the blog, the biggest confusion is that using the option does not actually redirect the feed - it redirects the references to the feed. People use this option in the expectation that it will change the URL of the feed. This option does not change the URL of the feed - it changes the URL used by references to the feed.

To change the feed references, successfully, you must have the URL mentioned by the setting already published, in a separate effort.

• If you renamed the blog to a different BlogSpot URL, you can redirect the feed reference, from a stub blog, to the feed published under the new URL.
• If you used a different service, like FeedBurner, to create a reformatted feed replica, you can redirect the feed reference to the FeedBurner feed URL.
• In either case, the URL has to exist, from a separate effort.

If you are reading this post, look down the page, after the "Newer Post Home Older Post" links.

Subscribe to: Post Comments (Atom)

There is an example of the original feed reference. The purpose of the post feed redirect feature, long ago, was to let the blog owners generate a different feed for the blog - maybe a FeedBurner republished post feed - and force that link to reference the FeedBurner republished feed.

If you use that link, and subscribe to the feed from this blog, you should get a subscription offer, using the FeedBurner feed for this blog.

The Post Feed Redirect simply lets people setup and use an alternate feed URL, without having to update the code for all links which reference the post feed - such as that link.

That's it - pure and simple.

If you have - even unintentionally - misused the post feed redirect in your blog, it's easy to correct the mistake. Just understand why you should correct the mistake.

Read More

Google+ Circles Is Replacing Following / GFC

Those of you who have been Following this blog, in the past, may have recently noted a new gadget in the sidebar.

Just below the "Follow Me" gadget, you'll see "+Follow Me". The latter gadget looks similar to the former - but has some subtle differences. Some differences are visible, others not so visible. And some differences are not visible to the eye - but will still affect your access to this blog.

The Google+ Circles gadget, which on this blog is labeled "+Follow Me", appears similar to the Following / Google Friend Connect "Follow Me" gadget - but appearances can be very misleading.

The larger pictures are one obvious difference - but that's not the most significant difference. Some difference need to be discussed now, rather than later, for maximum benefit.

Blogger Followers lets your Followers Follow one specific blog.

Following / Google Friend Connect lets your acquaintances Follow a single blog. I have several blogs, and a different group of Followers for each blog. The Google+ Circles gadget shows everybody in all of your publicly visible circles, merged together. The merged concept may, or may not, be to your liking.

Google+ Collections now let you separate different content - so you can share one blog to one Collection, and specific people can Follow ("Circle") one Collection. I'm not convinced though that all of my Followers understand this distinction.

Blogger Followers let you use email and newsfeed subscriptions.

With Following / Google Friend Connect, your Followers can use email, or any number of newsfeed clients, to read the complete content of your blog - including each complete post, if you setup the blog feed that way. Google+ Circle members can read a snippet of any blog post intentionally Shared, in their stream - but will have to click on the link to the blog, in the snippet, to read the entire blog post. If you have read this far, that's what you have already done.

Following / Google Friend Connect works best for public blogs - and supports a reader audience of unlimited size. A Google+ Circle, likewise, supports a reader audience of unlimited size.

With a properly setup Google+ Circle, and a Blogger blog with a list of designated readers - and your readers properly accepting the emailed membership invitation, up to 99 of your designated readers can Follow your blog. As before, the limit for private blog distribution, as for any team blog, is still 99 members.

Anybody Following a blog, using the stream of any author of the blog, will see a snippet of each post Shared in their stream. To read the complete post, they will have to click on the link in the snippet. With a private blog, the reader will have to be a blog member, to read the complete post.

Many Blogger blogs have a lot of Followers, which will be missed.

Many publicly visible Blogger blogs have Following communities which vastly exceed my 4700 member population (my "Follow Me" gadget, as of April 2013) - and the possibility of losing those communities will not be willingly accepted by everybody. The integration of Following with the newsfeed subscription - and with the dashboard Reading List - is not automatic with Google+ Circles.

A blog with multiple authors (aka "team blog") will have either a Google+ Circles gadget for only one author - or multiple Circles gadgets, to fairly let people subscribe to the various authors Google+ streams. Neither solution will be exactly equal to the Following / GFC blog feed subscription - especially if the various team members are similar to me, and my range of interests.

Right now, it appears that a blog can have just one Circles gadget. How team membership blogs will use Google+ is another question to ask.

Many blog owners have multiple interests - and publish multiple blogs.

Similar to the team blog, we may wish to consider the multiple interests of each blog owner. I am one person, with a number of interests.

People who have intentionally subscribed to the newsfeed from this blog, and are specifically interested in my blog about Blogger blogs, may not be extremely interested in my blog about cooking - nor in my blog about jokes, pranks, and miscellaneous ramblings. Unfortunately, if you Follow my Google+ stream, you'll get a bit of each subject.

Some people may use Google+ Collections, to separate their different interests. It's possible that some Google+ Followers are now Following my RBS Collection.

Again, the Google+ Circles gadget appears to contain the total Followers for one person, for all interests of that one person. I have not yet found a tool that will allow me to analyse the interests of each of my Followers, and to accurately determine the specific areas of overlapping, between my own personal interests and theirs.

It will be impossible for many blog owners to keep an accurate Circle complement, and segregate each circle according to interest, so they may Share only relevant material with the specific members of each different Circle.

Integration of Blogger Follower, and Google+ Followers, requires compromise.

As the Google+ Circles gadget evolves, some significant improvements - and some compromises - will be required. Like the Internet, Blogger, and Google, are constantly evolving. This may require compromises by many Blogger blog owners.

We now have a rollup discussion, where each blog owner is asked to provide their thoughts about the above described issues - and possibly, others that concern you. Anybody who experienced the Blogger GUI upgrade of several years ago may, from experience, realise how much better off we may all be, with these issues discussed now - rather than later.

Read More

Control The Email Settings, Relevant To Your Blog

Some blog owners don't always think about the various email settings, which are part of their Blogger blogs, and the possible effects to their email - or somebody else's email.

There are several settings, where a blog owner may enter an email address.

• Email posts to
• Comment Moderation.
• Comment Notification Email.

These settings don't require acceptance by the recipient, making for some interesting possibilities for causing problems in other people's email, as well as one's own email.

There are several Blogger dashboard settings - related to post publication and to various commenting activities - with differing effect to one's own, or somebody else's, email.

• Settings - "Mobile and email" - "Email posts to" - aka "BlogSend" - generates a minimally formatted text copy of each post, when published, to up to 10 email addresses.
• Settings - "Posts and comments" - "Comment Moderation" generates a minimally formatted copy of each incoming comment, before the comment is published - and allows moderation of the comment, while reading the email message - when the recipient has the proper authority.
• Settings - "Mobile and email" - "Comment Notification Email" generates a minimally formatted copy of each incoming comment, before the comment is published or rejected.

Since none of these settings require acceptance by the recipient, there are various possibilities for causing interesting email delivery.

Unlike various subscription services which use email, such as a FeedBurner Email Subscription service, an email address added to any of these three settings requires no formal acceptance. If a blog administrator should add an email address, whether their own (primary or additional personal email address), a willing friend or relative, or an unknown victim's address, there is no initial email sent to the recipient

You (or somebody else) has added this email address as a recipient of "Email posts to" / "Comment Moderation" / "Comment Notification Email". Do you approve of this additional traffic source to your email service?

or a similarly worded notification / approval. Given a clueless or malicious blog owner, it's possible that one (or all) of these settings could be used to harass an unwitting third party, or to (unwittingly) confuse oneself.

The "Email posts to" feature, also known as "BlogSend", generates a minimally formatted text copy of each post, when published, to up to 10 email addresses. This setting has been used, in the past, to provide distribution of newly published posts for private blogs, as well as a simple distribution for posts from public blogs.

Since it's limited to 10 entries, BlogSend does not provide a suitable service for any blog with a reader population of any appreciable size. For a blog owner with any technical experience, FeedBurner Email Distribution is a much better solution for post distribution - when the blog in question is publicly accessible.

For distribution of a private blog to more than 10 readers, one may use Google+.

The "Comment Moderation" and "Comment Notification Email" settings, used together, can generate interesting duplication of email to one's own (or somebody else's) email service. If these settings are made without thinking, some interesting confusion can result. Email addresses can be added to each of these settings without consideration of the relationship or level of authority enjoyed by the owner of the email address, relative to the blog in question.

Comment Moderation Email is presumed to generally be a function performed by blog administrators - but email resulting from this setting will be sent to anybody addressed. A blog administrator / member - or other non administrator of the blog or an unwitting stranger - will receive email suggesting several options,

Publish
Delete
Mark as spam
Moderate comments for this blog.

If the recipient is not an actual blog administrator, the links in the email provide confusion, and no result.

Comment Notification Email might be generally addressed to blog members - but is not necessarily limited. Since notification of comments is sent separately from moderation, recipients of a notification can become confused when they fail to find the comment, mentioned in the notification, present on the blog.

A blog administrator, using either an email moderation message - or using the blog Comments wizard, may or may not decide to Publish - or to designate a comment as Spam - regardless of a notification message having been delivered to each designated recipient.

Comment notification email may look similar to comment moderation email, less the comment processing options - possibly causing more confusion. A blog owner, adding his own email address to both comment moderation and comment notification, may see the combination as unknown duplication. And blog owners may confuse the proper use of comment moderation and comment notification email.

A blog owner, transferring ownership of a given blog, may overlook updating of the email settings. A new blog owner, receiving a blog being transferred, may likewise overlook these settings, and may lack the associated email, until the omission is corrected.

Either the previous owner, or the new owner, may be confused temporarily - and may wonder why they are still getting email / not getting email, until they examine and correct the setting in question. Alternately, if someone's email address was added maliciously, by a blog owner intending to harass somebody, one can see interesting possibility for conflict.

Read More

Blogger Magic - Verifying A Blog Feed URL

It's a fairly simple matter to determine the newsfeed URL, for any given blog, by examining the blog template code.

Besides the base feed, a blog may publish an extensive array of additional feeds, which won't be listed directly in the blog template code. You may use any given feed, in networking your blog, with any Google or non Google service.

Starting with any feed URL, what do I do? I could just open my favourite feed reader, or social networking web site, and paste the URL in place. But what if the feed reader or web site wasn't working properly, or I misunderstood the instructions? What if I see

Invalid URL

or the like, what do I do?

The smart thing to do, before you setup a FeedBurner feed or any complementary non Blogger service, is to test the feed.

Many modern browsers (Firefox or Internet Explorer, for instance) will give you a formatted display, when you are loading a feed URL.

Read More