Based on your question, I am not exactly sure where your local build sits right now. This answer is assuming you are starting from scratch, but have a copy of a working wordpress website on a live web server, and working on a mac. You need to install a web server onto your local computer. … Read more
Once you have same db, you will have same users, so offcouse the password for the user ‘admin’ (please do not use ‘admin’ as username) will be the one setted in database, and of course is the same for the 2 sites, once they shared the db. However you can create users that can login … Read more
If you are using Pantheon for hosting it turns out to be trivial to do this as a test (they call it dev), stage (they call it test) and production server are built into their platform along with tools to manage moving data and files around. Plus with Pantheon you get easy but optional Git … Read more
I suggest if you want to use BuddyPress always, just ignore/remove WordPress profile informations and you can: Redirecting User to Their Buddypress Profile when They access their wordpress profile(wp-admin/profile.php): http://buddydev.com/buddypress/playing-with-buddypress-and-wordpress-some-codes-for-the-site-admins/
This code works, but it’s only been tested in a localhost environment. There’s a function extracted from the plugin Multisite User Management, which is based on the get_blog_list function, that has been deprecated. No alternative available. For performance reasons this function is not recommended. The user meta has to be checked individually, i.e.: Aim, Jabber, … Read more
Based on the details above, I can think of the following suggestions: Create a setup in which you have two servers using the same database. This can work if both your setups are identical to each other Sync the data (option 1). Write a plugin that you install on both servers, and this plugin will … Read more
The reliable two–way sync is simply not something that have happened in WordPress. The typical way is in line with what you are doing — pulling a copy of production database into development environment. Note that this is commonly the one direction it goes. It’s much more problematic to try sync development back to production. … Read more
Newer hosting providers that cater specifically to WordPress usually have tools in place to ease this pain. I put my clients on Pantheon which has this neat Git-enabled workflow, where code only moves up (from dev to staging to production) and DB stuff only moves down (vice versa from the code). Copying a database from … Read more
WordPress already has a XML-RPC client class implemented. It’s in the same file as the server part: class-IXR.php located in wp-includes. The following code will generate a new post. You could wrap this in a function and attach it to the save_post/update_post action hook. To sync both parts, you could check for the post-slug or … Read more
The reality is that what we want is this: http://www.liquibase.org/ Liquibase is an open source (Apache 2.0 Licensed), database-independent library for tracking, managing and applying database changes. It is built on a simple premise: All database changes are stored in a human readable yet trackable form and checked into source control. However our development process … Read more