Blogger action - two skins, broken art

This is my first blog design change since upgrading to 6 The change was the addition of a rollover button and some descriptive text (top right, under banner).

For some reason, when I paste in the code I get an alert “There should be one and only one skin in the template, and we found: 2”. Also, the link to the art for the rollover button breaks and the button group is moved up to abut the header image. I tried grouping the text and button and the button object jumps to the top of the group. The page looks fine in preview and when viewed directly, first with the button and text, and then after I removed them:(news).

I completely removed the button and text elements from the page, uploaded, restarted Freeway, and then published, copied and pasted the code into blogger, and the element is still there. For some reason, the Blogger action is not generating code that represents the current state of the document.

Any ideas?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Update: I created a new page from scratch, copied and pasted in the blog content and history objects. This time the mysterious “two skins” alert went away but the history blog object is now placed above the content instead of to the right, as in the Freeway layout. The blog content object decided that it would fill the width of the page

I kept playing with the layout. Everything continued to be stacked. I got rid of the blog history object and stretched the blog posts object. This resulted in the “two skins” alert again.

I’ve devoted around an hour trying to get these two objects to behave. With 5.5 I never had a problem. I suspect that this is a version 6 thing. I had been having problems with Hype animations breaking but the 6.1 patch fixed it.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Trey,

I know I’ve dealt with the “two skins” thing before, I just don’t quite remember how I fixed it. Could you post the code that Freeway want’s you to use with Blogger here?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

You are a scholar and a gentleman.

Here’s the code:

span a, #fwNav1 .fwNavItem:hover > a { color:#000000; text-decoration:none; background:#EEEEEE; } #fwNav1 .fwNavItem a:hover, #fwNav1 .fwNavItem span a:hover, #fwNav1 .fwNavItem a:focus { color:#000000; text-decoration:none; background:#EEEEEE; } #fwNav1 * .sub { visibility: hidden; position:absolute; left:-0; float:left; padding:0; margin:0; list-style:none; } #fwNav1 .sub * .sub { top:-0; } #fwNav1 .fwNavItem .sub .fwNavItem { display:block; margin:0; padding:0; left:0; width:128px;border-bottom:0; border-left:0; border-right:0; border-top:0; } #fwNav1 * * * .sub { left:100%; top:0} #fwNav1 .fwNavItem .sub .fwNavItem a { display:block;color:#858585; text-decoration:none; background:#EEEEEE; margin:0;padding:3px 2px 3px 22px; height:1%; } #fwNav1 .fwNavItem .sub .fwFirstChild { border-top:0; } #fwNav1 .fwNavItem .sub .fwLastChild { border-bottom:0; } #fwNav1 .fwNavItem .sub .fwNavItem:hover > span a, #fwNav1 .fwNavItem .sub .fwNavItem:hover > a { color:#000000; text-decoration:none; background:#F9F9F9; } #fwNav1 .fwNavItem .sub .fwNavItem a:hover, #fwNav1 .fwNavItem .sub .fwNavItem span a:hover, #fwNav1 .fwNavItem .sub .fwNavItem a:focus { color:#000000; text-decoration:none; background:#F9F9F9; } #fwNav1 :hover > .sub { visibility:visible; } * html #fwNav1 { float:right; } * html #fwNav1 .fwNavItem a { float:left; height:1%; } * html #fwNav1 .fwNavItem .sub { clear:left; } * html #fwNav1 .fwNavItem .sub .fwNavItem { clear:left; float:left; } * html #fwNav1 .fwNavItem .sub .fwNavItem a { float:none; } #fwNav1 .fwNavItem.over *#fwSub1 { visibility:visible; } #fwNav1 .fwNavItem.over1 *#fwSub2 { visibility:visible; }]]> <![CDATA[.BlogArchive h2 { margin-top:0; font-family:'Raleway', sans-serif; font-weight: 400;font-size:24px; color:#6985A9; text-align:Left; } .archivedate { font-family:Verdana,Arial,Helvetica,sans-serif; font-size:12px; color:#594751; } a.post-count-link { font-family:Verdana,Arial,Helvetica,sans-serif;font-size:12px; color:#594751; text-decoration:underline; } a:hover.post-count-link { color:#0060A1; text-decoration:underline; } li { list-style:none; } .posts li a { font-family:'Raleway', sans-serif; font-weight: 400; font-size:12px; color:#6985A9; text-decoration:underline; } .posts li a:hover { color:#0060A1; text-decoration:underline; }

.post-wrapper:first-child { margin-top:0; }
h3.post-title { font-family:‘Raleway’, sans-serif; font-weight: 400;font-size:24px; text-align:Left; }
h3.post-title a { color:#6985A9; text-decoration:none; }
h3.post-title a:hover { color:#0060A1; text-decoration:none; }
h2.date-header { font-family:Verdana,Arial,Helvetica,sans-serif; font-size:12px; color:#858585; text-align:Left; }
.comments h4 { font-family:‘Raleway’, sans-serif; font-weight: 400; font-size:12px; color:#6985A9; text-align:Left; }
.post-body, .comment-body { font-family:Verdana,Arial,Helvetica,sans-serif; font-size:14px; color:#594751; text-align:Left; }
.comment-body { font-family:Verdana,Arial,Helvetica,sans-serif; font-size:14px; color:#594751; text-align:Left; }
p.post-footer-line-1 { text-align:Left; }.post-author, .post-timestamp, .comment-author{ font-family:‘Raleway’, sans-serif; font-weight: 400; font-size:9px; color:#3B5B82; }
a.timestamp-link { font-family:Verdana,Arial,Helvetica,sans-serif; font-size:12px; color:#618EC3; text-decoration:underline; }
a:hover.timestamp-link { color:#0060A1; text-decoration:underline; }
a.comment-link, .comment-timestamp a, .comment-author a { margin-left:5px; font-family:Verdana,Arial,Helvetica,sans-serif; font-size:12px; color:#618EC3; text-decoration:underline; }
a:hover.comment-link, .comment-timestamp a:hover, .comment-author a:hover { color:#0060A1; text-decoration:underline; }
p.post-footer-line-2 { text-align:Left; }.post-labels { font-family:‘Raleway’, sans-serif; font-weight: 400; font-size:12px; color:#6985A9; }
.post-labels a { color:#618EC3; text-decoration:underline; }
.post-labels a:hover { color:#0060A1; text-decoration:underline; }
.post-footer { margin: 10px 0 20px; }.feed-links { font-family:‘Raleway’, sans-serif; font-weight: 400; font-size:12px; color:#594751; text-align:Left; }
a.feed-link, .comment-footer a, .blog-pager a { font-family:Verdana,Arial,Helvetica,sans-serif; font-size:12px; color:#618EC3; text-align:Left; text-decoration:underline; }
a:hover.feed-link, .comment-footer a:hover, .blog-pager a:hover { color:#0060A1; text-decoration:underline; }]]></b:skin>

news, product info and features

BannerNoLabelsWide
OHairBannerLogo

800 • 582 • 2625


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Yikes! That is unreadable.

Try pastebin instead. Post back with the link.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

The code displays properly, as far as I can tell.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Trey,

Thanks! Okay, this is a Freeway bug, but it can be fixed with some code tinkering.

Freeway tends to put a lot of the CSS stuff in the document , wrapped inside tags. When it creates the code for Blogger, it wraps those blocks of styles with a special blogger-specific tag ( <b:skin> ).

The problem is that Blogger will only accept one block of styles, and Freeway often outputs two or three. This bug popped up in 6.0x, but Softpress fixed it. Apparently, it needs to be fixed again.

So, how can you fix it? I would start by setting the output to use external stylesheets (the option is in the document setup dialog). If that doesn’t work, you will need to lump all the style blocks together with a code editor.

For example, if this is Freeway’s output:

<head>
    <b:skin>
         #lala { background-color: camo; }
    </b:skin>

    <!-- Some other stuff here (this is an HTML comment) -->

     <b:skin>
          #another { text-align: left; }
     </b:skin>  
</head>

You will need to change it to look like this:

<head>
    <b:skin>
         #lala { background-color: camo; }
          #another { text-align: left; }
    </b:skin>

    <!-- Some other stuff here (this is an HTML comment) -->

</head>

I went ahead and fixed it for you, this code should pass Blogger’s muster:


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I went ahead and fixed it for you, this code should pass Blogger’s muster:

Strange, I though that Freewaytalk would render that. Here’s a regular old link: http://freewaytalk.net/thread/view/136350 · GitHub

And another attempt at embedding:


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

To embed a Gist, simply put the URL to the Gist page all by itself on a line in your e-mail message. This should just be the URL of the HTML page you see when Gist reloads after a save. The script looks for Gist and Pastie URLs and alters them to be their respective embed syntax. Adding the syntax long-hand, as you did, will just convert the script tag to entities (for security reasons).

Walter

On Aug 16, 2013, at 11:48 AM, Caleb Grove wrote:

I went ahead and fixed it for you, this code should pass Blogger’s muster:

Strange, I though that Freewaytalk would render that. Here’s a regular old link: http://freewaytalk.net/thread/view/136350 · GitHub

And another attempt at embedding:


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks Walter, let’s try that again.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I wish I could do something in return. Thanks very much.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

After pasting in the repaired code it worked perfectly.

Then I added a text item and a button, published and pasted the code straight out of Freeway. There was no issue with multiple skins this time, but it took longer for them template to process in Blogger. When checking out the result the text item and button did not appear. I cleared the cache and the items were a no-show. Not sure what is happening. I assume that Blogger simply refused to apply the revised template.

BTW, when checking out the corrected code, I noticed that there were two b:skin opening tags but only one close tag.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Trey,

Sometimes I found that I have to click on the “Copy code to clipboard” two or three times before it really copies. This might be your problem.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options