If you’re running WordPress on multiple servers, chances are you’ve come across an issue where once you’ve copied WordPress to the new domain, none of your scripts, styles or images are loading. One of the most common occurrences of this happening is running an installation on your local machine (localhost) and allowing people from an internet or network IP to view it. If you dig a little further by viewing page source you’ll notice the issue is caused by WordPress using your old domain (or localhost) for loading – resulting in extreme load on a single server or worse; a HTTP 404 error.
By default, CodeIgniter only allows segment-based URLs, however it is also possible with a little fiddling to use querystrings and even to make the change application-wide or controller-specific.
Have you ever wanted to require a script in PHP without it inheriting all your current scripts’ variables? Did you instead want to pass different variables to it? With this nifty little function you’ll be able to do just that.
CodeIgniter is an incredibly powerful and easy to use PHP Framework that makes developers’ lives alot easier. In its default configuration it only supports one site per installation – quickly result in thousands of files on your file server which can be a pain for all involved. With a little fiddling we can fix this.
WordPress is great. It allows you to quickly set up a blog with minimal effort. In the case of setting up the Google Syntax Highlighter, however, it ended up being quite a hassle due to WordPress’s WYSIWYG editor. This tutorial shows how to modify the editor to make Google Syntax Highlighter work as advertised.
Update Jan 3 2011 To allow pre tag in TinyMCE, we’re now modifying functions.php instead of a wordpress admin file so changes aren’t erased when WP is updated. See here for more details.