OIOpublisher Coupon Code for August 2010
Monday, August 2nd, 2010Now through August 31st, 2010 you can purchase OIOpublisher* for just $37 (normally $47) by using coupon code “SOLAR-WSHED” (no quotes).
If you’re unfamiliar with OIOpublisher, it is a PHP based ad platform with a focus on performance, control and ease of use. It allows you to easily serve advertising on your blog or website and keep 100% of the revenue you bring in. For those of you using WordPress, it includes a plugin that allows for easy integration. And if you need consulting help setting it up, please contact us.
WordPress 3.0.1
Saturday, July 31st, 2010WordPress 3.0.1, was released on July 29, 2010 and is a maintenance release that addresses about 50 minor issues. While upgrading is not required, it is recommended.
Schedule your WordPress upgrade today via our WordSprung WordPress Upgrade Service.
WordPress 3.0
Wednesday, June 23rd, 2010WordPress 3.0, the thirteenth major release of WordPress and the culmination of half a year of work by 218 contributors, is now available for download (or upgrade within your dashboard). Major new features in this release include a sexy new default theme called Twenty Ten. Theme developers have new APIs that allow them to easily implement custom backgrounds, headers, shortlinks, menus (no more file editing), post types, and taxonomies. (Twenty Ten theme shows all of that off.) Developers and network admins will appreciate the long-awaited merge of MU and WordPress, creating the new multi-site functionality which makes it possible to run one blog or ten million from the same installation. As a user, you will love the new lighter interface, the contextual help on every screen, the 1,217 bug fixes and feature enhancements, bulk updates so you can upgrade 15 plugins at once with a single click, and blah blah blah just watch the video.
Schedule your WordPress upgrade today via our WordSprung WordPress Upgrade Service.
OIOpublisher Coupon Code for March 2010
Monday, March 8th, 2010Now through March 31st, 2010 you can purchase OIOpublisher for just $37 (normally $47) by using coupon code “SAXON-WSHED” (no quotes). If you’re unfamiliar with OIOpublisher, it is a PHP based ad platform with a focus on performance, control and ease of use. It allows you to easily serve advertising on your blog or website and keep 100% of the revenue you bring in. For those of you using WordPress, it includes a plugin that allows for easy integration. And if you need consulting help setting it up, please contact us.
[Update: August 2010 OIOpublisher Coupon Code - Now through August 31st, 2010 you can purchase OIOpublisher* for just $37 (normally $47) by using coupon code "SOLAR-WSHED" (no quotes).]
500 Errors with suPHP
Tuesday, March 2nd, 2010
Found in WHM via Main >> Service Configuration >> Apache Configuration >> PHP and SuExec Configuration
We were recently migrating websites from one dedicated server to another dedicated server, both of which had basically the same software setup with an upgrade in the hardware.
For the ease of use in a web based GUI, we recommend cPanel/WHM to facilitate the majority of setup, and this was no different. You place the order with the dedicated hosting company stating everything that you want, including the control panel, and you’re on your way and able to run through your standard setup procedures.
When you’re done setting up the server you can begin migrating from the old server to the new server (WHM has an excellent tool for migrating between WHM/cPanel based servers). And most of the time everything is looking good and after a local run-through you can update the DNS and be on your way.
All of that to say, during this recent migration we spotted 500 (generic “internal server”) errors that we had not seen before. After troubleshooting, it was determined to be due to some .htaccess rules being added and/or certain files and/or folders having write permissions (ex: 777). Now we knew what was causing it and could fix it to some extent, but we still wanted to know why. What had changed from the last server to the new one?
After looking around for similar situations, we pieced together where we should be looking, the PHP Handler. The old server was running dso. The new server was running suPHP which wasn’t even installed on the old server. So we switched the new server to dso (see image above) and things were back to working the way they were before. (Note: from what we were seeing, suPHP is harder on your hardware resources as well.)
As a word of caution, web hosts do setup suPHP as an additional layer of security and it is advisable to not set directories and/or files to writable unless they need to be.