sethpackham

Just tried it. Works just fine.

Yes, I’d love to talk to you to see if our goals line up. If you have an office number I can call, or an email address, I’ll try to get in touch. My email is my username @ gmail if you’d rather send it there.

Hi Mike. Yeah, we have our entire WP package, including themes and plugins, in Rational Team Concert for source control — it handles revision control as well as our builds to rsync source code to various web servers (staging, production, etc). So, I can pretty easily decide which server to push code changes to with just a few clicks. This model seems to work well for the development of our theme and plugins. It’s when we mix in the need for our content owners to manage content in a CMS-like way where I’m getting stuck mentally. What tools are you developing. Are they open source?

I see what you mean. Perhaps then for Ramp to be effective, you basically have two “production” WordPress instances with Ramp powering the movement of content: One where content is staged and written but is not visible to the public, and the other where the content is pushed for the public domain. In this case, couldn’t there still be additional development staging and local environments for testing our theme and plugin changes before pushing these to the Ramp instances? We plan to automate the regular migration of production DB to staging and dev environments for rich testing for our programmers.

Thanks for the responses. Ramp from Crowd Favorite is something we’ve been looking at. And we have also been exploring how best to manage multiple WordPress installs to have a flow for both code changes and content changes. The code change is the easiest one to put our minds around, but is still tricky when migrating DBs from production to dev to staging.

1. Development environments on each developer’s localhost mirroring latest content from production db.
2. Staging environment for formal testing and staging of code before pushing to production. Also perhaps the place for all content production using tool like Ramp.
3. Production environment. Latest content and code.

It is starting to look like commercial tool Ramp is best and only option outside of copying and pasting content.

Hi Krishna, I’m very experienced with WordPress as both a user and a theme developer, and I’m aware of how it stores a revision history as you make changes to pages and posts. However, these do not answer my question.

My question is how to use WordPress to “stage” revisions to existing pages so that reviewers can see the changed content for the website before it is published.

Put another way … how could I edit 10 existing pages, show these changes to a client, then promote the changes in batch?