yksin
Forum Replies Created
-
Finally had time to contact Bluehost support with my problem.
Short version: all is good now.
Long version (for anyone with a similar problem who might need to write to their own tech support):
What I wrote to them.
The control panel says I’m under PHP version 5.2.17. However, use of the WordPress plugin Health Check on my blog tells me that my server is running PHP 4.4.9. I’ve had to deactivate to use one of my standard essential plugins because it requires at least PHP 5.2 versions, and WordPress 3.2 when it comes out will require PHP version 5.2.4.
What they wrote back:
Your account should be showing as 5.2.17. I set the Addhandler to use php5 just to be sure. You can verify it by going to [URL for my blog].
Based on this, seems the Addhandler, whatever that is, must’ve been been the issue. Healthcheck now returns healthy results; but even more imporantly, YARPP is working fine now.
I reckon now would be a good time to break out my Paypal and give you some $upport. Thanks Mitcho!
Thanks, Mitcho. I ran Health Check and found that in spite of Bluehost saying it’s running PHP 5.2.17, in fact Health Check says it’s running PHP version 4.4.9.
So I will get with Bluehost & ask them why it’s giving a false report of which version of PHP is used for my site, & ask them to please upgrade.
Any word on a possible solution to this problem?
Seems like this plugin would work great for Spanish-language blogs, but not so well for an English-language blog like mine.
Forum: Alpha/Beta/RC
In reply to: How to remove/replace the WordPress footer in TwentyTenperthmetro — I couldn’t get the php solution you posted above to work properly. But one quicky CSS style change turns out to work just fine.
Simply add:
#site-generator { display:none; }to your style.css file. And voila!, it be gone!
(As advised by ipstenu, best to use child themes of twentyten for this & any other style changes.)
I see that non one at WordPress.com stats has yet taken time to take a look at this problem.
Is it because the someone put “Resolved” in the subject header of this thread even though it’s not resolved, & the proposed solution did not in fact work properly but instead caused people to lose their stat histories?
The problem continues. It sure would be nice if this otherwise great plugin could be fixed.
P.S. I’m using WordPress.com Stats 1.5.4 on WordPress 2.8.4. I can check daily stats and 30-day stats. Any attempt to access quarterly stats returns this error message:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate ## bytes) in /home/henkimaa/public_html/blog/wp-includes/wp-db.php on line 930 — Henkimaa being the name of my blog, obviously. The ## represents a number that sometimes changes.
Any attempt to access yearly or “all time” stats results in a blank page.
Again, since other people’s histories got clocked back to zero when the followed the original proposed solution, I’m not going to try it. Is there anyone over there at WordPress.com Stats who can fix this? Or propose a solution that won’t wax our stats histories?
Any word on a true solution to this issue yet? I’ve started encountering it but I don’t want to implement the original solution but don’t want to implement for fear my history will be wiped out too.