Blogger Magic - Third Party Templates

There are millions of Blogger blog owners - and each owner has their own idea, how their blog should look.

Not every blog owner is willing to settle for using a Blogger supplied template. Some blog owners design their own templates - and others choose templates provided by non Blogger developers.

Some blog owners - even those with no technical background - choose third party supplied templates, and demand instructions in Blogger Help Forum: Learn More About Blogger. Not every blog owner can be supported, according to their personal level of need.

It's OK for you to install a new third party template, for your blog - though you should plan to do some extra work.

Third party templates should include some installation instructions.

A template publisher should provide instructions for uploading and installing their template. Installation procedures may vary, however.

• Easy install.
• Template restore.
• Template Edit HTML.

Easy install.

If the template publisher is honourable, using an install script, provided by the template publisher, can be the most reliable install procedure. A well written script can extract the template of your choice from the publishers library, copy it to your blog, and tweak the install to your satisfaction.

Giving control of your Blogger account, to an unknown third party, is not always the best idea, however.

Template restore.

If the template publisher provides a template as an XML file, and describes the template as "for Blogger", you can install the template from the dashboard. You will first download the template of your choice, to a local computer.

With a template downloaded locally, you use the Blogger "Backup / Restore" wizard, in the dashboard Template page.

Start with the dashboard Template page.

Hit the "Backup / Restore" button.

Hit the "Choose File" button.

Now, you have the file manager, provided with your computer. Select the file, containing the template just downloaded.



The "Backup / Restore" wizard is part of the Blogger dashboard. The template will be selected, using the file manager wizard on the computer being used.

Template Edit HTML.

This is the most universal procedure - if the template is provided as HTML. Just use the Blogger "Edit HTML" wizard, in the dashboard Template page.

The simplest install uses "Edit HTML", from the dashboard Template page.

Copy the HTML or Text file content, into the window.



In some cases, you may have to do some work, to use an HTML template.

It's your blog - and the template choice is yours too.

You can use any acceptable third party blog template. Many blog features will perform best, though, if you use the Blogger supplied post template.

To ensure up to date Blogger code, always refresh the post template, after installing a third party blog template.

And as always, I'll suggest that you backup the template, before and after installing a custom template.

If you install a third party template, you may have to support your blog, on your own.

Please understand that Blogger won't be able to support your third party template - that is the responsibility of the template publisher. Problems with your blog, after installing third party accessories, will be yours to resolve.

---

There are millions of #Blogger blog owners - and each owner is different. Blog design - and templates used - will vary similarly.

Some blog owners cannot be satisfied by the Blogger supplied template library - and require third party produced templates.

Read More

Blogger Magic - Links And Colors

We see an occasional question in Blogger Help Forum: Get Help with an Issue about blog links - and the captions that change colour, mysteriously.

Some blog owners seem to regard the colour changes as one more Blogger pecadillo - ignoring the fact that colour changing link captions have been part of Internet design, since the early days.

In most blogs, you can change link colours - and prevent the colour changes - using the Blogger dashboard Template Designer.

You can change any color using the color code, or a color chart, part of any colour wizard.



To access the Template Designer, start from the dashboard Template page.

The Template Designer is behind the "Customize" button, on the dashboard Template page.

From the dashboard Template page, click on the "Customize" button.

Start with the Template Designer main page.

Click on Advanced - and look for "Links".

On my blog, I can adjust "Link Color", "Visited Color", and "Hover Color".



Template Designer menu and wizard combinations may vary.

The Template Designer menu / display can be adjusted according to the decision of the template designer.

Your template, when customized, using Template Designer, may have a "Links" section, with "Link Color", "Visited Color", and "Hover Color". It may have additional colours - or colours and fonts may be combined. All of this is as setup in the template "Variable definitions" section.

You can change any colour using the colour code - or a color chart.



If you want your links - including titles - to remain one colour constantly, change the 3 colours (or whatever your blog has) to one common value.

My blog uses "Link Color" = "2d25ce", "Visited Color" = "ce25c5", and "Hover Color" = "583fff". Your blog may use a different colour combination.

For a useful color number / visual chart, you can use W3Schools: HTML Color Picker.

---

Not all #Blogger blog owners understand link captions - and how the caption colours change, to indicate pages that have been visited from a given browser. Some think the colour changes are a Blogger novelty.

In reality, link caption colours have been a feature, since browsers were first used in the Internet.

Read More

Blogger Magic - Backup The Template

It's always wise to backup the blog contents - and the template.

If you are publishing a blog, you may occasionally make a mistake. Being able to recover from a mistake, using backed up content, is always a good idea.

Blogger provides a dashboard wizard to backup the blog template - and a complementary wizard, to backup blog content - comments, pages, and posts.

Backing up a Blogger blog template is reasonably simple.

The template backup wizard is on the dashboard Template page.

Start from the dashboard Template page.

And click on "Backup / Restore".

Then click on "Download full template".

This will give you a standard file save wizard, that is used by your computer.



The file save wizard will depend upon the operating system.

On my computer, the file save window is "Save file as". Your computer operating system might have a similar wizard - or it may be different.

Other than choosing file and folder (your choice, on your computer) for backing up the template content, you just sit back and let the backup work. Don't wait too long though - a few seconds is all that it should take.

Understand how and why to backup.

Just don't backup blindly - or for the wrong reasons. To be useful, a backup needs to consider how to restore - and why you might restore.

Any backup is more useful, if you plan how and why you might need to restore.

---

As you develop a #Blogger blog, making regular backups of the template is always a good idea. Everybody makes mistakes - and recovering from a template coding mistake is a lot easier, if you're able to restore a previous template copy.

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

Read More

Recovering From A Corrupt Template - Persistence

Of the many Blogger Mysteries that confound blog owners and readers, none are more obscure than the many bX codes.

Some problems, reported in Blogger Help Forum: Get Help with an Issue, start so innocently.

As I edited the Template HTML, I saved my changes - and the bX error suddenly appeared.

Each different bX code refers to a different problem, with Blogger in general. Of the bX codes that refer to template corruption, each different bX code may refer to a different template corruption problem.

When a template corruption problem can be reset, the resetting process may involve repeated use of one or more dashboard pages.

Different problems may enable - or prevent - use of a different dashboard page. For problems with multiple causes, you may have to use each different wizard, persistently.

1. The Template Designer page.
2. The Template page.
3. The Template Editor ("Edit HTML") page.
4. If the blog is not operational, you start again.

Unfortunately, some problems may prevent use of all 3 pages. For the problems that permit use of one or more pages, you try each available page, repeatedly, until the blog becomes operational.

To access each page, you may need to bypass the dashboard menu.

The Template Designer page.

The Template Designer is used for one task - "Remove customizations".

The Template Designer.



"Remove customizations" may be the simplest reset that you may try - when possible. Some customizations, when removed, may enable subsequent use of the Template page, or the Template Editor.

The Template page.

The Template main page is used for two tasks.

1. Backup / Restore the existing template.
2. Get a new template.

The Template main page.



Some problems, when reset using the Template main page, may enable subsequent use of the Template Designer, or the Template Editor.

The Template Editor ("Edit HTML") page.

The Template Editor ("Edit HTML") is used for two tasks, as an alternate to the Template main page. Also, it may be used to reset any "rgba" colour combination problems.

1. Backup / Restore the existing template.
2. Get a new template.

For template corruption problems that prevent use of the Template main page, the Template Editor - combined with a second blog, where a clean template is developed and tested - can be used.

The Template Editor (aka "Edit HTML").



Some problems, when reset using the Template Editor, may enable subsequent use of the Template Designer, or the Template main page.

If the blog is not operational, you start again.

If you get a new bX code, you repeat the above sequence. Some problems, with multiple causes, may require repeated retries.

In extreme cases, you may end up creating a new blog at the URL.

---

Some #Blogger template problems, which lead to a bX code display, may have multiple causes - and all causes may require solution, to make an affected blog operational. With some causes preventing solution of others, a repetitious use of the various dashboard pages may be required - to solve some template corruption problems.

Read More

Recovering A Broken Template, Using "Edit HTML"

I have, for a long time, recommended regular template backups, for those who like to tweak the template.

Normal backup uses the "Backup" wizard, on the dashboard Template page. When backed up, an XML file, containing the template code, is extracted and saved locally. To restore, the "Restore" wizard is used and a previous Backup XML file selected.

That's how Backup / Restore should work - but it isn't always that easy.

With the current wave of bX codes, being used to diagnose the "Error 500", the Template dashboard page may not be accessible.

This is the case even attempting direct access, using the navbar "Design" link, or a hand generated equivalent.

With some blogs, the Template Editor may be OK - with the Template page broken.

For some blog owners who cannot use the dashboard Template page, the Template Editor aka Template "Edit HTML" may be accessible. This will require using a hand generated URL - since there is no direct link to the Template Editor.

If the Template Editor can be accessed directly, the blog owner may be able to continue.

1. Access the Template Editor for the broken blog, in one browser window.
2. Setup a new blog, using a clean template, in a second browser window.
3. Access the Template Editor for the new blog.
4. Copy the new blog template, to the broken blog.
5. Save the now recovered current blog template.
6. Refresh the post template.
7. Clear cache, cookies, and sessions, restart the browser, and try again.

The blog owner has a possible solution, in this case.



Access the Template Editor for the broken blog, in one browser window.

Use a hand generated URL, to access the Template Editor. If you can do this much, you are well on the way to getting your blog back.

If you truly feel the need, you can backup what's there, before you paste over what you have. Ctrl - A then Ctrl - C to copy - then Ctrl - V, into a new text document - that you can save, at your convenience.

Setup a new blog, using a clean template, in a second browser window.

Blogs are free, so make a new one. Select the "Simple" template, for best results.

Access the Template Editor for the new blog.

For the new blog, you can use the dashboard menu, and Template - "Edit HTML".

Copy the new blog template, to the broken blog.

With the Template Editor window for the new blog, containing a valid template, copy its contents (Ctrl - A then Ctrl - C) - into the Template Editor window for the broken blog (Ctrl - A then Ctrl - V).

Save the now recovered current blog template.

Hit "Save template". And say a brief prayer.

Refresh the post template.

This may not be necessary - but you should consider it. It has saved a few blogs.

Clear cache, cookies, and sessions, restart the browser, and try again.

This is always a good idea, when clearing bX codes.

It's a workaround - not perfect, but it may get the blog going again.

This is not a perfect solution. If you are tired of the bX codes, and if this will get your blog operational, you may find it useful, however. It's also possible that this error is part of a larger problem - and you need a persistent solution.

If you have a template back up, you can apply that after the blog is back in service. And your readers have stopped emailing you with angry complaints. Just use a clean backup.

And test your tweaks, going forward, more carefully.

---

Some bX codes, being used to diagnose the "Error 500" condition in #Blogger blogs with broken templates, affect the dashboard Template page. Blogs which have broken Template pages cannot be recovered by getting a new template.

In some cases, with the Template page unusable, it may be possible to directly access the Template Editor - then paste a separately developed clean template into the "Edit HTML" window, and correct the problem.

Read More

bX Codes, Diagnosing "Error 500", Being Reported

We're seeing a few reports from blog owners, in Blogger Help Forum: Get Help with an Issue, with blogs being inaccessible.

My blog can't be seen at all, it just says error when I'm trying to open my blog. I also can't edit anything, like HTML or Template.

When the blog is viewed, it will issue one of several bX codes. So far, I've identified bX-3o92c2, bX-ppgc07, bX-tqn3zr, bX-v2vqfh, bX-vg1g6a. When the blog is viewed, using an HTTP trace, the trace will terminate, showing an old friend.

Error 500 Internal Server Error

What we appear to be seeing is multiple bX codes, being used to diagnose the various causes of the "Error 500", which has long plagued Blogger blog owners.

The "bX-v2vqfh" and other errors appear to be "500 Internal Server Error".

Here, we see a "bX-vg1g6a".

And an HTTP trace, for the same blog, shows the ubiquitous "Error 500 Internal Server Error".



So, the blog owner should get a new template - or restore from backup.

The simplest solution, to the "Error 500" has been to restore the template, from a recent backup - hoping that you have a usable backup. If a backup is not available - or if the blog, with the backup applied, also returns a bX code - you must get a new template.

The fortunate blog owner, able to login to Blogger with the right account, will have a relatively simple task.

1. Click on the "Design" link in the navbar.
2. Choose a new template - or restore from a previous backup.
3. Use "Edit HTML", and reset the post template.

If the blog has a custom template, that cannot (should not) be trashed, and the Template page can be accessed, a backup before getting a new Blogger template - and a restore after - may provide relief.

In either case, you will need to use the dashboard Template page - then reset the post template, using Template "Edit HTML".

In some cases, the dashboard can't be accessed. In this case, we must (with some effort) access the Template page, directly.

Possibly a little effort may be required.

1. Extract the BlogID, from the navbar "Design" or "New Post" link.
2. Build a Template page access URL.
3. Access the Template page, using the direct URL.
4. Choose a new template - or restore from a previous backup.
5. Use "Edit HTML", and reset the post template.

If the navbar link can't be used, a little more work is involved.

1. Find a cached copy of the blog, before the template broke.
2. Extract the BlogID, from the cache source code.
3. Build a Template page access URL.
4. Access the Template page, using the direct URL.
5. Choose a new template - or restore from a previous backup.
6. Use "Edit HTML", and reset the post template.

Finally, if possible, recall what changes you made, immediately before the problem was observed - and avoid repeating those changes.

Note that some blogs absolutely won't provide access to the Template page - but they may, to the Template Editor aka "Edit HTML".

---

It appears that #Blogger Engineering, in an effort to diagnose the annoying "Error 500 Internal Server Error", has recently activated or added a series of bX codes - which are being reported by various blog owners.

We were some time ago advised to have the owner get a new template, when encountering the "Error 500".

Read More

Unfold Widgets Selectively, Instead Of All At Once

The new Template HTML Editor has been with us for just under 2 weeks.

Not every blog owner sees the new editor as an improvement. Some folks don't understand how to find the code sections, where they need to apply changes - and would probably be happier if "Expand All Widgets" were an option.

Like the old saying goes, you just cannot please everybody.

Fortunately, with this change, it's not difficult to find the code sections that need changing - you just do a little bit of research, before using "Edit HTML".

With the old editor, finding a section that needed changing could be a bit frustrating - though simple, given enough time.

1. Hit "Expand Widget Templates".
2. Search for a recognisable section of code.
3. Try very carefully, to find the right section of code.
4. Be careful, and don't select the wrong section of code.

With the new editor, you have a bit more work to do - and what you have to do appears to be simply repetitive.

1. Find a folded code section.
2. Unfold the section that's folded.
3. Repeat, until everything is visible.
4. Search for a recognisable section of code.
5. Try very carefully, to find the right section of code.
6. Be careful, and don't select the wrong section of code.

Instead of spending so much time unfolding, searching, and rechecking everything, why not do some research? Figure out what needs changing. Look at the display on the dashboard Layout wizard (previously called "Page Elements"). Identify the widget to be changed, using both the relative position on the page, and the title.

Find the widget id, by looking at the widget to be changed, then at the URL behind the "Edit" link. If you're editing the post template, you'll be looking at "Blog Posts", which has the widgetID of "Blog1". Click here, for instructions on determining the widget id.

Once you have the widgetID, for the specific widget that you need to modify, go to the Template "Edit HTML" wizard, use the "Jump to widget" pull down list, select the widget by widgetID, and there it is. Now, unfold that widget, and do what you have to do.

Isn't that simpler, when you think about it?

>> Top

Read More

All Template Changes Won't Always Be Visible, When The Blog Is Published

Not all blog owners appreciate the differences between using the various template wizards, and what they will actually see, once the blog is published.

The confusion about the various template wizards, and what is actually seen, expressed in Blogger Help Forum: Something Is Broken, is numerous.

Why aren't my changes to the template being saved?

This question is expressed in a number of ways - and has a number of causes.

There are a number of causes of template problems, in general.

• Some problem are caused by Blogger Engineering, as they manage the Blogger application.
• Some problems are caused by the blog owners, as they use (and yes, misuse) the Blogger application.
• Some problems are simply caused by the perception of the blog owners, and will never be resolved, to everybody's expectations.

If you're viewing this blog using a desktop / laptop computer, with a "normal" browser, and you can find the "View Source" control, take a look at the source for this page. Compare what you see there with the display in the Template "Edit HTML" wizard (and allow for some confusion, when using "Edit HTML").

• If you have a "normal" browser, and are viewing this blog in a "Designer" / "Layout" template, you'll see a lot of the same code, in both "Edit HTML" and "View Source".
• If you have a "normal" browser, and are viewing this blog in a "Dynamic" template, you'll see very little of the same code, in both "Edit HTML" and "View Source".
• If you have a "normal" browser, and are viewing this blog using a redirected "mobile" browser view, you'll see very little of the same code, in both "Edit HTML" and "View Source".
• If you're using a "mobile" computer, you probably won't even have an option to "View Source".

The bulk of the options in the Template "Edit HTML" wizard, in the "Layout" wizard, and in the Template Designer, are intended to change the "Designer" / "Layout" template views. The three wizards have much less effect, against the "Dynamic" / "Mobile" template views.

If you tweak the CSS settings in "Edit HTML" or the Template Designer - or if you change the layout using "Layout" or the Template Designer - you may not see all of the changes reflected in either a Dynamic or Mobile view.

Sometimes, this is because you have already tweaked the template improperly, preventing the wizard from saving your latest changes. Other times, it may be simply because the Dynamic and Mobile templates are not designed to let you tweak the settings in question.

We've also seen vague suggestions that having the mobile template active can cause the Template Designer font and style selections to be non operational. Font settings, made using the Template Designer, won't be saved and won't appear in the blog, when published. Right now, we're unsure whether the Live Preview window updates reliably.

And recently, uncontrolled customisation of the blog accessory complement, and of the dynamic template code, have caused instability in network access, when viewing blogs using dynamic views.

>> Top

Read More

The Option To "Expand Widget Templates", In The Template "Edit HTML" Wizard, Is No More

One of the more confusing features of the Blogger Template "Edit HTML" wizard, used to be the option to

Expand Widget Templates

With the new "Edit HTML" wizard, that option is not needed. Given the choice to "Expand Widget Templates", the typical blog owner was frequently caught between a rock, and a hard place, when editing gadgets.

• Don't use the option - and the gadget code section, which was to be edited, remained concealed.
• Use the option - and all gadget code sections were expanded, revealing all gadget code.

This frequently left the owner with either no information - or too much information, from which to work. Broken templates, caused by improper template HTML edits, were common.

The new Template "Edit HTML" wizard replaces the single "Expand Widget Templates" option with selective widget expansion. Now referred to as "folded" code, a concealed widget code section is identified by a fold marker ("sideways arrow icon"), next to the line number.

The code inside the widget is folded by default.

Clicking on any fold marker, the concealed gadget code section is revealed. If the now revealed code section itself contains concealed code sections, those sections are displayed as folded, and can then be revealed - if necessary, and only if necessary.

Thus we can eliminate unnecessary depth (internal gadget code sections) and width (additional gadget code sections) from being displayed when we only need to edit a specific gadget, at a given level of complexity. This will make it easier to identify and to edit the necessary lines of code, and to avoid editing lines of code which should not be edited.

If you're looking for a specific section of the template - for instance, the CSS rules - you may find that section folded also. CSS rules, for instance, are at the top of the template.

<b:skin>---</b:skin>

and

<b:template-skin>---</b:template-skin>

On the other hand, if you're looking for the content of an HTML / JavaScript gadget, that's still edited from the specific gadget in the Layout wizard.

<data:content/>

Gadget content is not folded.

Hopefully, we'll soon see less problem reports, in Blogger Help Forum: Something Is Broken, about broken templates - though we will probably continue to see confusion, about templates that only appear to be broken.

As always, if you change template code, remember to clear browser cache and restart the browser, before concluding that your changes were not effective.

>> Top

Read More

Some Blog Owners Reporting The Template Designer Changes Do Not Update On Their Blogs

For several weeks, we're been seeing various reports in Blogger Help Forum: Something Is Broken, mentioning problems with template updates, being made using the Template Designer wizard.

The reports are not so widespread to indicate a complete malfunction - but neither can we dismiss the problem, as being unique to one browser, one template type, or one particular update pattern.

It's likely that we are looking at a number of problems, aggregated and compounded, into one common symptom.

I cannot Save changes in Template Designer.

With a problem report like this, some examining of the details may be appropriate.

The Template Designer wizard, which is a component in the Blogger Dashboard, is a complex and sophisticated collection of menus and utilities, which runs on the blog owners computers.

Like most Blogger code, the Template Designer is subject to the effects of other programs, and various security settings - which may be installed or set on each individual computer, with or without the understanding of the blog owner and / or computer owner. In some cases, the blog owner and computer owner may be different people.

If you are seeing a problem with the Template Designer, when trying to update the layout on your blog, there are several tests which you can make, which may help to isolate the problem.

• Try making the same updates, using another computer.
• Try making the same updates, using another browser on your current computer.
• Try setting up a new blog, with the same template, and make the same updates to the new blog.

If you're able to make one or more of the above alternate updates, that will help to eliminate some, or many, alternate suspects, as the cause of your problem. If other people are reporting this problem, their results from the above tests may or may not correspond with yours - because their base problem may differ from yours.

Right now, we're seeing seven different causes of these problems.

1. Changes made by Blogger Engineering, to support new browser versions and browser updates, and to provide new template features.
2. Changes inherent in new browser versions, made by the browser vendors.
3. Third party browser add-ons, installed by the owners of the various computers.
4. Security settings, inherent in new browser versions and third party add-ons.
5. The cumulative effects of various template tweaks, both made using "Edit HTML" and the Template Designer itself.
6. Unrealistic expectations of blog owners, about effects of Template Designer settings, against all templates provided by Blogger.
7. Unrealistic expectations of blog owners, about effects of Template Designer settings, against templates not provided by Blogger.

Of these possible causes, only #1 (and possibly #2 and #6) are the sole responsibility of Blogger Engineering. The blog owners (and computer owners) must assume some partial responsibility for #2 - and sole responsibility for #3, #4, and #5. The blog owner, and the developer of any custom, third party template, must jointly assume responsibility for #7.

Recently, Blogger Support acknowledged the problem, in part.

Some users have reported that the Apply to Blog button in the Template Designer is non-functional for some Dynamic View templates.

We also have a Rollup Discussion, in Blogger Help Forum: Something Is Broken, where individual details are being provided by various blog owners.

Right now, we're starting to suspect that some "problems" are actually caused by the blog owners, who are simply not aware that not all changes made, using the Template Designer (or the Layout or Template "Edit HTML" wizards), are designed to update all templates used in viewing our blogs.

Read More

Blogger Blogs Redirecting To "blogspot - ping . com"

Today, we see the latest in the never ending saga of blog owners, who previously (maybe / maybe not recently) installed some deviously created software - whether intentionally or not - and who now find their readers unable to view their blogs, and themselves even unable to access the template editor to remove the malicious code.

My blogs are redirecting auto to ping . blogspot - ping . com", can anybody tell me how to fix this?

The malicious redirecting appears to be cause by a small snippet of JavaScript code - which has been installed, in most cases, as template HTML. Alternatively, some blog owners have added separate HTML / JavaScript gadgets, to host this code.

It's easy enough to identify - not so easy to remove, as some owners have found. In many cases, we are seeing reports that even when directly accessing the Layout wizard or Template Editor, the malicious code activates, and redirects the blog owner's browser.

Since the redirect is running from a snippet of JavaScript code, blocking the malicious code will prevent the redirection, and allow corrective access to the Layout wizard or Template Editor.

<script src='http : // ping . blogspot - ping . com / ping . js' type='text/javascript'></script>

Whichever GUI wizard you use to remove the code, remember to clear cache and restart the browser after removal and before testing for success.

Since I routinely - and consistently - use Firefox with NoScript to browse, I was able to access one victim blog without the redirection occurring, view the blog source, and extract the above code. If you use NoScript, you (the blog owner) should be likewise able to access your dashboard, and the Template Editor, and remove the bogie.

Please note that the code snippet, excerpted above, has extra spaces inserted into the URLs, to prevent advertising of the actual hijacking domain.

Anybody who knows where this bogie originated, and how it was deviously conned upon the blog owners, can help a lot of people by identifying the origin. Only when this is done, can we try to prevent the problem - rather than advise how to remove the problem.

First, install the popular Mozilla browser, Firefox. Having added Firefox, install the add-on NoScript. NoScript uses a Unix level security policy.

Deny by default, permit by exception.

Keep in mind the different trust levels of Blogger and BlogSpot - with NoScript, you will have to allow Blogger, yet forbid BlogSpot. Code from unknown domains, such as "blogspot - ping . com", will not run on any NoScript protected computer - unless you, intentionally, enable it. Knowing the threat from this bogie, you will hopefully choose to not enable this domain.

>> Top

Read More