PSDCovers

Interesting, indents only work if I turn OFF the css that comes with the plugin. Odd.

I have CM Answers Pro (paid) 2.6.1 installed and we have this same problem. Answers are there but the questions are not rendered at all.

Hi Jeremy, you are right, I’m using 1.6.1 (queued from Google). Seems like 1.9.1 breaks a few things on it’s own so I’ll need to debug those as well.

Thanks for the heads up, now that I know what it is I’ll work backwards and try to get this updated properly.

eherman24, if you got this working I would really like to know how. I’m having the same problem and would appreciate your help if you’ve already solved it.

Thanks,
Simon

Interesting, part 1 of my 2 part comment never appeared…

So I have my theme which is using get_post_meta quite successfully and it’s humming along just fine. I make frequent backups and all the data is there. So I recently tried to recover a DB as a test to see how well I would recover and it turns out that for the most part it’s great. However, all my custom fields are empty — but only get_post_meta returns the values as empty. The data is still there in the SQL backup as well as in the DB (I had thought the post ID was changed but that was a brain fart).

It’s really quite frustrating. This thread was the closest thing I could find to people talking about get_post_meta

My bad, the database DOES have the same ID’s so that’s one less issue. Here is the metadata after it’s imported into the DB:

a:5:{s:10:"resolution";s:18:"2040x3800 | 300DPI";s:10:"zoomsample";s:66:"imageZOOM";s:9:"psdaction";s:80:"downloadZIP";s:7:"widthmm";s:2:"54";s:8:"heightmm";s:3:"120";}

So the data is there but the following returns nothing:

$my_meta = get_post_meta($post->ID,'_my_meta',TRUE);
echo '<b>' . __('Resolution: ') . '</b>' . $my_meta['resolution'] . '<br>';

Nothing. I can see it in the DB but PHP thinks otherwise.

BTW, the exact same code is running fine on the live site and is happily displaying the data.

It spontaneously started doing the same thing to me after working flawlessly for months.

I’m having the issue and working to fix it. However, here’s a question I can’t seem to find an answer to: Why does Google Pagespeed complain about serialization and penalize *me* when the issue is completely on their end?

Can I even deal with this other aside from removing AdSense?

The following requests are serialized. Try to break up the dependencies to make them load in parallel.

https://pagead2.googlesyndication.com/pagead/expansion_embed.js
https://pagead2.googlesyndication.com/pagead/js/r20120425/r20120410/show_ads_impl.js
https://pagead2.googlesyndication.com/pagead/show_ads.js
The following requests are serialized. Try to break up the dependencies to make them load in parallel.

https://pagead2.googlesyndication.com/pagead/osd.js
https://pagead2.googlesyndication.com/pagead/js/r20120425/r20120410/show_ads_impl.js
https://pagead2.googlesyndication.com/pagead/show_ads.js

I had the same problem. Turns out I had the user agent set to iOS Safari for iPad. Might not be your problem but that was mine.