The database connection constants are defined in the wp-config.php file. Whether the 2 wp-config.php files in the jiewmeng directory and the WordPress directory are the same? You need to create 2 different databases and set their constants in the respective wp-config.php files.
While this might be not the easiest task for a beginner, it is very well possible – with a little help from some plugins. In a similar scenario I would usually install WordPress under a subdomain. When everything is looking ok to launch, I would recommend to first (always!) make a backup of everything. You can … Read more
There’s not a correct order. Either way will work and results in a WordPress install that is secured with SSL. What makes sense in a situation, depends on the setup and workflow. If you can plan ahead, it’s optimal to set up the SSL on your server first. Because doing so, you don’t have to … Read more
Short answer: Plugins do not modify existing files, they hook into WordPress via an exposed API. Plugins can modify database schema. Plugins don’t have to uninstall cleanly. Plugin Hooks Plugins hook into WordPress at specific point exposed by the WordPress core. http://codex.wordpress.org/Plugin_API As an example, the function get_option() reads a site option from the database. … Read more
The article you linked to covers everything you need to know. I will just clarify what you do not understand and what is outdated. Site Redirect The domain mapping is done through wordpress.com to do a 301 direct, which tells search engines that you have moved permanently to a new address. It is outdated now … Read more
I’ve answered a similar Question. Basically: create a Dropin plugin at the root of wp-content named install.php inside install.php, create a new version of the pluggable function wp_install_defaults() remove all unwanted defaults and customize at will, like: update_option(‘template’, ‘your-theme’); update_option(‘stylesheet’, ‘your-theme’); update_option(‘current_theme’, ‘Your Theme’); update_option(‘my_theme_options’, $theme_options_array ); auto-activate some bundled plugins bundle everything into one … Read more
I finally found a solution to this problem and thought I would post my solution for anyone looking for assistance. My main website sits on /public_html on my server I was installing new sites on a subdomain (e.g. newwebsite.com.au) in a sub-directory: /public_html/sites/newwebsite.com.au Even though /public_html/sites/newwebsite.com.au was the root directory for the subdomain: newwebsite.com.au for … Read more
Set server_name to the IP address, eg: server { listen 80; server_name 0.1.2.3; // other stuff } You could also leave it out, because the default in ngninx is an empty string. But then all those pieces in WordPress that don’t validate $_SERVER[‘SERVER_NAME’] and similar values … will just break. See ticket #25239 for the … Read more
If you have access to your host commandline and are running linux, why not pair wp_cli with a bash script. In this way you can have a fairly defined standard set of plugins to activate per install. wp plugin activate plugin_a wp plugin activate plugin_b wp plugin activate plugin_c Here’s a WP_CLI and YT demo … Read more
I’ve installed WordPress on my virtual server running Windows Server 2008 R2. Installation was easy, no troubles. I installed PHP using Web Platform Installer. PHP 5.3 performs well on IIS7 and you can also use WP super cache to increase performance. There haven’t been any downsides for me so far 🙂