I checked my Nginx log files and saw a lot of errors as below:
*11047 FastCGI sent in stderr: “PHP message: PHP Warning: Parameter 1 to W3_Plugin_TotalCache::ob_callback() expected to be a reference, value given in /home/users/yinfor.com/wp-includes/functions.php on line 3597” while reading response header from upstream,
I googled it and found the answer.
The reason why it happened is PHP 7 and W3 Total Cache.
Since I can not change PHP 7, I have to change something in W3 Total Cache plugin.
Find the file /wp-content/plugins/w3-total-cache/lib/W3/Plugin/TotalCache.php
Go to line 512, and replace following function ob_callback(&$buffer)
with function ob_callback($buffer)
There are very few guide on web about migrate blog from MovableType 5.27 to WordPress 3.7.
Here is my own experience to do it.
Step 1: Prepare the data on MovableType 5.27
Using MovableType export function is not enough, because the exported file has entries, tags and comments, but no keywords.
When WordPress import plugin working on this type of export file, it will not import tags. It only import MovableType keywords as WordPress tags.
So that, I found an solution to export MovableType with keywords, which are actually tags in MovableType.
Add a new template file. Add following into it and publish it.
WordPress 3.4.2 released today. I did a quick upgrade on my WordPress installations.
It is a security update, so, do not wait.
Fix some issues with older browsers in the administration area.
Fix an issue where a theme may not preview correctly, or its screenshot may not be displayed.
Improve plugin compatibility with the visual editor.
Address pagination problems with some category permalink structures.
Avoid errors with both oEmbed providers and trackbacks.
Prevent improperly sized header images from being uploaded.
I upgraded almost eight blogs powered by WordPress yesterday when I got the release news of WordPress 3.3.1.
WordPress 3.3.1 is now available. This maintenance release fixes 15 issues with WordPress 3.3, as well as a fix for a cross-site scripting vulnerability that affected version 3.3. Thanks to Joshua H., Hoang T., Stefan Zimmerman, Chris K., and the Go Daddy security team for responsibly disclosing the bug to our security team.
The good part is that update procedures are pretty simple.
visit Dashboard → Updates in your site admin.
Actually, I update themes and plugins first. Then update WordPress.
During past week, I saw two shell accounts are hacked. Both are on Dreamhost.
One of it is reported by Google Webmaster Tools. It said there are some malicious code found.
The other one is found, because that the memory usage is increased too fast, but no increase on PV.
I checked the account and be noticed some wired issues.
One of the important files, .htaccess is changed by a hacker.
It send web spiders, such as Google bots, Bing, ASK, to a third party site, which has a malicious code. The code may affect the user computers.
When user enter a wrong URL, user should see a 404 error page from the site. The hacker also send these users to the remote site, which has malicious codes.
SO, if you land the website on the right page URL, you will not see it.
It looks normal and no problems.
The hacker steal the traffic from the sites. And also has potential risk to the users of the site. How to fix hacked WordPress blog?
The way I did to clean it is that simply.
1) Export the data
2) Make a new shell account on Dreamhost
3) Point the site to new account
4) Install the fresh, updated version software
5) Import the data
Then last step to delete the old shell account.
Just few days after the release of WordPress 3.2, wordpress 3.2.1 released.
It is said that it fixes a JSON-related server incompatibility problem that affected some users. Fixes for the new dashboard design and the Twenty Eleven theme, based on the popular Duster theme, are also included.
There is no problem for me. I would like to keep my installation of WordPress update as usual.