Search Results for 'wordpress'
-
Search Results
-
@seanbaugh What I posted above was for two single WP installs. I have to add that if you’re going to do the above, make sure that the 1st WP install and the 2nd WP install have the same versions. So if existing install is WP 2.9.2, then your second install must also be WP 2.9.2 – can’t guarantee it will work if you use different versions. Just backup your 1st install’s database first if you want to experiment with different versions.
How To Set Up A WordPress “Under Construction” Environment
The following technique works with WordPress installed on your production server and shows everyone a “Under Construction/Under Maintenance” page while you and only you can see the site as if it were live.
Rename index.php
• Open up the root folder of your WordPress installation and locate the index.php file. Rename this file to index_wp.php. Don’t worry, we’ll be loading this file later.
Create a new index.php file
• Fire up your favorite code editor and create a new file called index.php and save it on the root folder of your WordPress installation.
• Paste the following code, besure and save the file, now upload the new index.php to your server.
Click Image to copy code text.
I still can’t figure out how to post code, tried "code tags", "pre tags", "text area tag in form", would appreciate some help on this that works.
Another place you can copy the code.
Open your site
If you have correctly performed the previous steps you should have a WordPress installation with a custom index.php file and a index_wp.php file, both on your root installation folder. Open up your home URL and you should see your “Under Construction” page. Whoo Hoo! now everyone is seeing this page. But now we need to continue development or perhaps show our clients the current progress on their site. Head on to your browser’s address bar and type this after your home URL.
/?uc=true&pwd=123456
A fully functioning WordPress installation visible only to you during the complete length of your session. No redirects, no rerouting, no separate development and production folders. The code starts the session engine and looks for two variables sent as GET. The first variable is ‘uc’ (short for Under Construction). If this variable is set with any value then the var ‘pwd’ is checked to see if it matches the hard coded password. If these conditions are met a session variable is set to include the index_wp.php during the complete length of that session. If the conditions don’t match then the current session is forwarded to the “Under Construction/Under Maintenace” page and the WordPress installation never gets loaded.
• Set your own password
On line 06 in the new index.php change "123456" to set a your own password. i.e. "00cz942ab".
Besure to upload and replace the initial "under construction" index.php, with your new password version.
• To end the development session type: /?stop=true
The development session will be closed and you’ll be back on the “Under Construction” page.
• Redeploy or Open your website for users
simply rename the new index.php file to index_uc.php and then rename the index_wp.php file to index.php. If you ever need to set your website in a “Under Construction/Under Maintenace” state, simply rename the files and your done!
Hopefully you find this Under Construction hack useful, it was created by: Juan Camilo Estela
I did not so long ago but wasn’t happy with the memory footprint I was having on my VPS mainly due to Apache being too resource hungry and the intermintent lock ups of my server because Apache likes memory for breakfast, especially when it gets busy and even when its not busy at times. Plus I had to tone down the static caching because I was doing a lot of development work on it and got fed up waiting for the new content to appear.
Gone back to pure Nginx and certainly not looking back at the moment.
Running Nginx, PHP-FastCGI, WP3 MS, BP and a whole heap of WP plugins and my site certainly has an edge over any other setup I’ve installed on it in the past, especially Memory/Speed wise.
Biggest problem I have found with Nginx Rewrites is getting Images, avatars, avartar uploadds working. Nginx rewrites for WPMU 2.9.2 and WP3 MS are different (not sure about WP 2.9.2). Couldn’t find a working solution online so came up with my own based on the what I’ve learnt over the last few months. Probably better solutions as I’m not an expert but the important thing is that they work
.If you want to try yourself heres the Nginx rewrites I’m currenly using…
location / {
root /www//root;
index index.php;gzip on;
gzip_http_version 1.0;
gzip_vary on;
gzip_comp_level 3;
gzip_proxied any;
gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
gzip_buffers 16 8k;if (!-e $request_filename) {
rewrite ^.+/?(/ms-.*) $1 last;
rewrite ^/files/(.+) /wp-includes/ms-files.php?file=$1 last;
rewrite ^.+/?(/wp-.*) $1 last;
rewrite ^.+/?(/.*.php)$ $1 last;
rewrite ^(.+)$ /index.php?q=$1 last;
expires 10d;
break;}
}location ~* ^.+.(html|jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|doc|xls|exe|pdf|ppt|txt|tar|mid|midi|wav|bmp|rtf|js)$
{
root /www//root;
rewrite ^/.*(/wp-.*/.*.(html|jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|doc|xls|exe|pdf|ppt|txt|tar|mid|midi|wav|bmp|rtf|js))$ $1 last;
rewrite ^.*/files/(.*(html|jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|doc|xls|exe|pdf|ppt|txt|tar|mid|midi|wav|bmp|rtf|js))$ /wp-includes/ms-files.php?file=$1 last;
if (!-e $request_filename) {
rewrite ^.+/?(/wp-.*) $1 last;
rewrite ^.+/?(/.*.php)$ $1 last;
rewrite ^(.+)$ /index.php?q=$1 last;
}expires 30d;
break;
}location ~ .php$ {
root /www//root;
keepalive_timeout 0;fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /www//root/$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_script_name;
include fastcgi_params;
}
