As I wrote in the last posting another bug was found in pagebar (thanks to Kai-shao). The reason for this strange behaviour was not easy to find but in the end it was a problem caused by the new WordPress v2.5 components namely jquery. Here a news version which solves the problem:
Download:
pagebar219.zip
pagebar219.rar
pagebar219.7z
Technical background:
In WP2.5 the [...]
WordPress 2.5 doesn’t like me… Yet another bug crept from under the dirty, wet sink. This time it’s a JavaScript problem:
I’m using jquery to enable/disable some options (automagic insert / stylesheet). The exact same code works under WP2.3.3 while it’s totally unhappy under WP2.5. First I thought I messed up the code but it looked [...]
So, busy day… I tried to fix the bugs which are most annoying:
the debugging output should have disappeared now (and Murphy knows that there is still another one).
automatic updates should now work. I tried it on my own server (this one) and it worked. It still deletes the old pagebar2/ directory and creates a new [...]
OK, OK, the new bug fix version still got bugs:
1) It prints “pagebar2.php” after the pagebar. This is a debug output which survived… brave little output!
2) It’s still not update-able with the new WP update function. The update function simply deletes the old pagebar2 directory and installs new pagebar directory. “$$%&&$%ยง%!!!” as Mr. D. Duck [...]
I deployed a bug fix version of pagebar, Version 2.17, which solves the problem described by Cristiano in the comments.
Background: The problem was caused by the usage of the ‘short_open_tag‘ (<?= ?>), which can be disabled in the php.ini.
I love languages where you can change the syntax by some configuration files .
Some users (only some) report an error after updating WP from v2.33 to v2.5. pagebar displays something like this:
or like this:
depending on the options set. I was not able to reproduce this error on my own blogs.
Has anybody experienced this problem and solved it? Many users would appreciate any help, I suggest….
