Don, are you reading this?
Yeah, I'm reading this.
Here is the deal - its really a few different things happening as near as I can tell.
[1.] The plugin looks to see if a template's stylesheet contains .serendipity_findmore class. If it does NOT contain that class, it emits the following:
Code: Select all
.serendipity_findmore {
margin: 5px auto 5px auto;
padding: 5px;
text-align: center;
}
.serendipity_findmore img {
border: 0px;
}
.serendipity_diggcount {
float: left;
}
.findmore_like_button img, .findmore_like_button iframe {
cursor: pointer;
}
.lazyload_switcher {
margin-right: 0.5em;
display: inline;
float: left;
margin-top: 4px;
}
.findmore_like_button {
display: inline-block;
vertical-align: middle;
margin-right: 2em;
}
.google_like {
width: 150px;
height: 21px;
}
.gplus_like {
display: inline;
}
.serendipity_findmore_like {
vertical-align: middle;
height: 21px;
}
So, NoelB's use of bulletproof, which does not style that class, has these styles in the generated serendipity.css. Any template that styles .serendipity_findmore, like 2k11, will not have these styles because the plugin defers to the template stylesheet.
[2.]The plugin contains the smarty template plugin_findmore.tpl. That smarty template renders the entire output of the plugin as a series of links, wrapped in a <div>, so its display was horizontal. Bulletproof does not contain a custom copy of this template, so (< s9y 2.0) anyone using bulletproof, or any other theme that did not contain a custom plugin_findmore.tpl, inherited the version shipped with the plugin.
[3.]Now we have s9y 2.0, and 2k11 is both the new default theme and the source of smarty templates if a theme does not have one. These files were previously fetched from ../templates/default/.
NoelB is using Bulletproof. Bulletproof has no specific template engine, so any smarty templates it doesn't provide will come from 2k11. 2k11 DOES have a plugin_findmore.tpl template, so NoelB's blog uses it. In fact, EVERY theme will use 2k11's version of this file that a)doesn't provide its own plugin_findmore.tpl, or b) defines a template engine other than 2k11. In other words, the version shipped with the plugin is virtually unused because 2k11 has this file. This is true for any plugin's smarty template that 2k11 provides.
2k11's version of plugin_findmore.tpl emits output as an unordered list, not a bunch of links within a div. 2k11's stylesheet correctly handles the output with list-style-type: none on the <ul>, and display: inline on the <li>'s. The plugin itself doesn't emit these styles. In fact, the plugin continues emitting its original styles because it doesn't find the class .serendipity_findmore in bulletproof's stylesheet. In this case, its not really hurting NoelB, but its not helping either.
NoelB has a couple of potential solutions:
1) Copy the file ../plugins/serendipity_event_findmore/plugin_findmore.tpl to the template folder, presumably ../templates/bulletproof/
2) copy 2k11's findmore styles to a user stylesheet (user.css) in the bulletproof folder, and activate that option within bulletproof's configuration. The 2k11 findmore styles are as follows:
Code: Select all
.serendipity_findmore,
.serendipity_findmore_like {
list-style: none;
margin: 0;
}
.serendipity_findmore {
padding: 0;
text-align: left;
}
.serendipity_findmore li,
.serendipity_findmore_like li {
display: inline-block;
margin: 0 4px 8px 0;
}
.lazyload_switcher {
display: inline-block;
margin: 0 4px 0 0;
}
.lt-ie8 .serendipity_findmore li,
.lt-ie8 .serendipity_findmore_like li,
.lt-ie8 .lazyload_switcher {
display: inline;
zoom: 1;
}
.findmore_like_button { min-width: 120px; }
.facebook_like iframe {
position: relative;
top: 15px;
}
.gplus_lazyload_switcher {
float: left;
position: relative;
top: 8px;
}
.gplus_like iframe {
position: relative!important;
top: 6px!important;
}
Going forward, at minimum, it seems maybe the plugin could be modified to emit the same styles as 2k11, and to also copy 2k11's version of plugin_findmore.tpl to the plugin, though it will be virtually unused under the present template inheritance/template engine policy.
Whew... sorry for being so long winded!!!!