WordPress/Mandigo/Current Issues
From onehertz
Contents |
[edit] Current issues
[edit] Confirmed issues in Mandigo 1.39
[edit] Random headers don't work when viewing a category archive
The new per-category headers feature breaks the legacy random headers functionality. The fix is simple though: open header.php and around line 145
Search for:
// if we didn't find one but the "random headers" option is enabled
elseif ($mandigo_options['header_random_image']) {
And replace with:
// if we didn't find one but the "random headers" option is enabled
if (!$noheaderimg && $mandigo_options['header_random_image']) {
[edit] Confirmed issues in Mandigo 1.37
[edit] Flash objects are cut down to half-height
The fix intended to keep the dimensions of resized images proportional affects the way flash object are displayed. The faulty CSS property responsible for this behavior is located in header.php, around line 185.
Search for:
$lastminutecss[] = sprintf(
' .entry img, .entry embed, .entry object { max-width: %spx; width: expression(this.clientWidth > %s ? %s: true); height: auto; }',
$maxwidth, $maxwidth, $maxwidth
);
And replace with:
$lastminutecss[] = sprintf(
' .entry img, .entry embed, .entry object { max-width: %spx; width: expression(this.clientWidth > %s ? %s: true); }',
$maxwidth, $maxwidth, $maxwidth
);
$lastminutecss[] = ' .entry img { height: auto; }';
[edit] The page loads then goes blank
This problem happens when you place some javascript in a widget on a sidebar that displays on the left. Ad-Sense ads were not affected until recently but Google has probably made some changes to the Ad-Sense code, so placing any ad on the left sidebar will blank the page. The fix is simple though, and all that has to be done is in footer.php:
Search for:
jQuery('#sidebar1 script[src@=googlesyndication]').remove();
And replace with:
jQuery('#sidebar1 script').remove();
There's a similar line for #sidebar2, just make the same change and it should be fine.
[edit] Unconfirmed issues in Mandigo 1.37
[edit] Theme Options settings lost after the upgrade
I had to re-apply my Theme Options after upgrading to 1.37 -- it wiped them all. It's never happened in an upgrade before. Not a huge problem (just had to remember what I'd changed), and could well have just been an anomaly that will affect me.
I've just updated another blog, and had no problems, it all worked as expected. Weird eh! Just one of those strange anomalies that happen sometimes I guess.
Note after upgrade to 1.38 Just thought I would add a note to this to say that I had no problems following the upgrade to 1.38 -- so I guess the problems I had last time were, indeed, just one of those odd things that happen with computers.
