hallo frank, danke für die blumen das mit dem senf ist irgendwie erhalten geblieben, als ich anfing das theme zu veröffentlichen, aber es hindert einen ja glücklicerweise nichts daran, einfach von deutsch nach deutsch zu lokalisieren. mal sehen, vielleicht biete ich ja demnächst mal ne de_DE.po als Grundlage zum Download an.

Größere Probleme mit einem Update solltest du nicht haben, wenn du den Style für das Blog deiner Eltern konsequent ins Schemes-Verzeichnis ausgelagert hast. Es kann sein, dass du aber an der einen oder anderen Einstellung im CSS noch etwas tun musst, da sich der zugrundeliegende HTML-Code, den die PHP-Seiten generieren, leicht verändert hat.

Bei KCYaps Wettbewerb mache ich mir da keine Illusionen mehr - das sieht inzwischen doch sehr stark danach aus als wäre das ein großer Scam gewesen; schade eigentlich, denn die angekündigten Prämien waren wirklich lecker.

david,

It is fun being your beta tester.

good to hear that in this special case, there is a nice double meaning of that quick word, as I am indeed the alpha tester with my site as you are the first person who has started to use Binary Blue as well, it is obvious you are the beta one
but back to the roots now - thank you very much for your trust; I logged in and disabled/enabled one plugin after the other at your site to see whether one of them renders the scheme switcher disfunctional, but I didn’t find anything useful as there are at least some plugins that shouldn’t be switched off for security reasons (spamkarma, for example), I didn’t try very much with it.

what I can see is that the format you’ve defined for your recent comments isn’t HTML compliant, but this shouldn’t harm the javascript code. I have two proposals to you - 1st is to send you the current development version of 0.9.9 - this at least includes the fixes for nice shaping design of F2B in inferior exploder (very nice wording, BTW :D)
2nd is to assist you on the installation of a minixampp suite on your local machine, where you can install a local wordpress for testing purposes.

the issues you are having there must have their reasons somewhere in the distinct configuration of your server, as it is running fine here, and the only chance to chase ‘em down is, in my opinion, the local testing machine way.

unfortunately, MSIE doesn’t deliver any single usable information of debug output on these issues - it’s really a shitty piece of crap regarding this aspect. In firefox I’d have the chance to get the venkman extension chasing down the bugs, for immature exposer, at least as far as I know, there doesn’t exist anything as useful.

so, it seems as if I’ve found a solution. I think it is not that nice, but it works - I introduced a little span with the stylesheet class clear assigned to it between the end of the content div and the beginning of the category div, and voilà, the content extraction works as expected in the good old BB design again - even with relative positioned headlines
the final fix will be available in 0.9.9; I first want to address some other issues (fancy titles and lightbox aren’t applied to the expanded content yet) before I’ll release another version.

argh, that’s odd….
okay, for the category area part sticking to its position when including the content of an article, this is an issue I am addressing the whole afternoon for now. at first, the content expanded the div correctly, but then the heading of the following post would stick where it was, now the headings flow down correctly, but the category stands still… this is really disgusting, especially as it is clearly a browser bug.

today I got rid of MANY internet exploder specific CSS bugs (especially in fade2blue regarding all those PNG images), but this one is an issue I seem to get handled at least I know its reason has to do something with the relative positioning of these content parts. If you change the stylesheet not to shift the headings to the left for 30px, everything worls correct - but it then doesn’t look as nice as before if you switch to fade2blue scheme, you’ll see what I mean - another stylesheet, same functions and HTML, and it’ll work perfectly.

what’s even more disgusting is the fact that I can reproduce the inline comment error on your site without any problem, but I can’t see any error if I do so on my site or my personal computer here at home. each and every browser I use works just fine here…. that nodeName attribute is part of the fancy titles plugin. I suppose, if you switch that off, everything will be fine as well…

regarding your son, that’s indeed some nice anecdote well, more than 50 percent of my visitors use firefox as well, and MSIE7 at least seems to improve its behaviour, so there is at least a chance that designing a nice layout will be much easier some day

hi David,

once again a strange problem, as it worked smoothly on my local testing machine and my own site. Additionally, I kept getting “ActiveX automation errors” today, which is even more strange as I hadn’t changed anything on my system - at least I thought so (see further down).

I’ve written a quick workaorund for the issue you’ve described, it makes sure the correct object is selected before trying to read out the targetID. I didn’t rename the file and the button, but the download is now referring as version 0.9.8a.

If you ever run across some of the ActiveX errors I mentioned above, reset your internet security settings to “medium” default, clear your browser cache and restart the browser. That was a real strange package of errors induced with this crappy piece of code shit. You should really talk some important words with your son

This comment has the simple and only purpose to serve as a demonstration of the inline comments feature. It’ll be obsolete as soon as the first real comment will be entered here