Comments on: Making WordPress Run More Securely and More Efficiently http://www.natebal.com/2010/02/wordpress-securely-effiently/ Website Design Tutorials And Social Media Marketing Tue, 07 Sep 2010 12:37:53 +0000 hourly 1 http://wordpress.org/?v=abc By: Nate Balcom http://www.natebal.com/2010/02/wordpress-securely-effiently/comment-page-1/#comment-6 Nate Balcom Thu, 04 Feb 2010 00:15:46 +0000 http://www.natebal.com/?p=29#comment-6 JP - Since my move to a new host I've actually instituted Google sitemaps again. This is for people really trying to optimize. Google sitemaps is an important one. It's all about the dynamic xml! Thanks for all your advice. You've been a great help! JP – Since my move to a new host I’ve actually instituted Google sitemaps again. This is for people really trying to optimize.

Google sitemaps is an important one. It’s all about the dynamic xml!

Thanks for all your advice. You’ve been a great help!

]]> By: JP http://www.natebal.com/2010/02/wordpress-securely-effiently/comment-page-1/#comment-5 JP Wed, 03 Feb 2010 23:18:28 +0000 http://www.natebal.com/?p=29#comment-5 The "number of queries" code can be left in the footer of your blog, just wrap it in HTML comment tags: i.e. <!-- php code goes here -->. That way you can check it anytime without having every visitor see it, and without having to remove or comment it out after looking at it. Also, the Debug Queries plugin can also help you identify bottlenecks: http://wordpress.org/extend/plugins/debug-queries/ I think you're making a mistake with the Google XML Sitemaps plugin settings. The whole benefit of using WordPress and plugins is that you are automating the dynamic building of the site. By disabling automatic rebuilding, you're defeating the automatic function of the plugin. Sure, it uses memory, but only when you publish and only for a few seconds. Also limiting the number of posts in the sitemap is bound to screw it up. Because now you have to remember to increase the limit as you add more posts. If you forget, your sitemap is inaccurate and everyone you (automatically) submit it to is getting an incomplete picture of your site. The “number of queries” code can be left in the footer of your blog, just wrap it in HTML comment tags: i.e. <!– php code goes here –>. That way you can check it anytime without having every visitor see it, and without having to remove or comment it out after looking at it.

Also, the Debug Queries plugin can also help you identify bottlenecks:
http://wordpress.org/extend/plugins/debug-queries/

I think you’re making a mistake with the Google XML Sitemaps plugin settings. The whole benefit of using WordPress and plugins is that you are automating the dynamic building of the site. By disabling automatic rebuilding, you’re defeating the automatic function of the plugin. Sure, it uses memory, but only when you publish and only for a few seconds.

Also limiting the number of posts in the sitemap is bound to screw it up. Because now you have to remember to increase the limit as you add more posts. If you forget, your sitemap is inaccurate and everyone you (automatically) submit it to is getting an incomplete picture of your site.

]]> By: Shane http://www.natebal.com/2010/02/wordpress-securely-effiently/comment-page-1/#comment-4 Shane Wed, 03 Feb 2010 15:34:12 +0000 http://www.natebal.com/?p=29#comment-4 After all the craziness you have endured trying to keep this site up, we have both learned more about security than I would have ever thought we needed to know. Now i am crossing my fingers that neither of us will need to further this education! After all the craziness you have endured trying to keep this site up, we have both learned more about security than I would have ever thought we needed to know. Now i am crossing my fingers that neither of us will need to further this education!

]]>