nhaskins.com » simplehelix

folder permission issue with simple helix dedicated server.

Nathan Haskins — Thu, 30 Sep 2010 14:15:36 +0000

The one line take away is, public_html needs to be 775 permission.

permission set to 755, and ready to go

So I learned that when moving a site to simple helix, the file permissions for the domain’s public_html/ folder need to be ’755′ or else the site will throw access denied error. Originally I thought the domain folder itself needed to be 755… doesn’t seem to be the case. By default the folder is set to 775, however i had to remove and recreate the public_html folder.

MIME for .vcf files can be hit or miss. …

Nathan Haskins — Mon, 10 May 2010 20:26:04 +0000

MIME for .vcf files can be hit or miss. Simplehelix’s justin goldsmith figured out the solution:

modify .htaccess…
IE/Safari/FF fix: AddType application/octet-stream .vcf

Simplehelix Git’s it, thanks for the se…

Nathan Haskins — Mon, 10 May 2010 20:13:33 +0000

Simplehelix Git’s it, thanks for the setup! Looking forward to testing it out

Simplehelix no Git on shared account qq….

Nathan Haskins — Sun, 09 May 2010 20:14:16 +0000

Simplehelix no Git on shared account qq. After speaking with tech support it seems only the dedicated servers can run Git. The issue with the shared accounts is that if it requires root access for anything, they can’t do it. So they can’t install it, even if you offer to pay. Damn.

When hosting a wordpress site at simpleh…

Nathan Haskins — Mon, 03 May 2010 18:15:06 +0000

When hosting a wordpress site at simplehelix remember to ask them to turn OFF dir_open() restrictions for the domain.. otherwise your media library is going to throw errors.

the (max) account uses .htaccess, no acc…

Nathan Haskins — Mon, 03 May 2010 18:07:58 +0000

the simplehelix (max) account uses .htaccess, no access to php.ini… had to setup some max timeouts so i used the following in a .htaccess file in the sites root directory:

php_value upload_max_filesize 20M
php_value post_max_size 20M
php_value max_execution_time 200
php_value max_input_time 200

That should do it in theory.

Localizing wordpress, and some handy mySQL to speed it up

Nathan Haskins — Mon, 03 May 2010 02:46:56 +0000

Localizing wordpress after moving it from one domain name to another? It use to be a pain in the ass to hunt down all the link.. well it still can be. However, these mySQL find and replace commands speed it up a heck of a lot. If your theme is pretty basic, you may be done after running these.

In the commands below, Im going from my old dev address ‘studio2108.com.s52733.gridserver.com’ to my new address ‘studio2108.simplehelix.com’. Remember to back up your database before trying this.. anyway take the 4 lines below, cut them, edit them, and then paste them into phpmyadmin’s SQL tab and your good.

Whats weird is the theme file has hardcoded references to studio2108.com in the header file… im finding and replacing them for now.

update wp_posts set guid = replace(guid,'com.s52733.gridserver.com', 'simplehelix.com');
update wp_posts set post_content = replace(post_content,'com.s52733.gridserver.com', 'simplehelix.com');
update wp_options set option_value = replace(option_value,'com.s52733.gridserver.com', 'simplehelix.com');
update wp_postmeta set meta_value = replace(meta_value, 'com.s52733.gridserver.com', 'simplehelix.com');