2718.us blog » theme http://2718.us/blog Miscellaneous Technological Geekery Tue, 18 May 2010 02:42:55 +0000 en hourly 1 http://wordpress.org/?v=3.0.4 Child Themes to Upgrade-Proof Your Theme Changes http://2718.us/blog/2008/07/03/child-themes-to-upgrade-proof-your-theme-changes/ http://2718.us/blog/2008/07/03/child-themes-to-upgrade-proof-your-theme-changes/#comments Fri, 04 Jul 2008 04:52:30 +0000 2718.us http://2718.us/blog/?p=47 I’ve had yet another why-didn’t-anyone-tell-me-sooner moment–child themes in WordPress.  From How To Protect Your WordPress Theme Against Upgrades (via Parent Child Themes and How I used a WordPress Child Theme To Redesign My Blog The Smart Way):

Problem: You’ve finally found a theme you like but you want to modify it. The modifications are pretty simple but what happens when you want to upgrade the theme? Do you really want to go through all those files again hunting down the changes? Don’t you wish you could just upgrade and be done with it?

So, basically, install the theme you want, create a new theme directory for you modifications, and in the style.css file, which defines the metainfo for the style, designate the original (unedited) theme as the template.  If need be, use functions.php to make more modifications.  Just note that any template files in your own version’s directory beyond style.css and functions.php will be ignored.

When it comes time to upgrade the theme, you upgrade the “parent” theme and your modifications are unchanged in their own directory.

]]>
http://2718.us/blog/2008/07/03/child-themes-to-upgrade-proof-your-theme-changes/feed/ 0
covert blog hacks? http://2718.us/blog/2008/04/08/covert-blog-hacks/ http://2718.us/blog/2008/04/08/covert-blog-hacks/#comments Tue, 08 Apr 2008 15:24:36 +0000 2718.us http://2718.us/blog/?p=8 Having noticed what seemed like it might be an urgent-ish security-related post show up in the mass of post links at the bottom of my WordPress dashboard, then following some links:

There seems to be two kinds of hackery going on, just like I’ve described:

1. Inserting “invisible” HTML full of links (for NSFW sites) into your WP template that isn’t obvious when you go to your blog, but is VERY obvious when you look at the source code (and start seeing that you’re getting traffic for some “peculiar” terms).

2. Inserting whole new source code / new sneaky themes that copy other blogs / content *exactly*, which is full of spammy content and affiliate links.

(Vulnerable WordPress Blogs Not Being Indexed > Massive Blog Hackery Exposed > TailRank Exposes Massive Number of Blogs Hacked) It seems like if you’re running WordPress, it’s advisable to upgrade to 2.5 (which was relatively painless) as well as checking the actual code of your theme…

]]>
http://2718.us/blog/2008/04/08/covert-blog-hacks/feed/ 0