Wordpress post sync / publish to production - mysql

I'm using wordpress as a simple backend CMS for a flash site. Posts are queried and displayed in list format on the frontend. I want to be able to make post edits or add new posts on my staging server, and have a quick and easy way to publish changes to production without having to do a full mysql db dump / import. I've looked around for plugins or solutions but haven't found any. Seems like wordpress needs a "publish to production" option.
The intended workflow is that users can create or edit content as much as they want, then an editor will go through it and approve content. Once everything looks good on staging, we publish to production. Any ideas?

Some of this thread at Wordpress might be relevant for you as it concerns moving from staging to production and the use of relative and absolute paths, etc.

WordPress does have a preview button that should allow you to see the WP content without actually publishing. If you must see it in the flash site, I think your best bet will be to setup your flash site with XML-PRC.

Related

How to get file contents of old site on drupal?

We have a site running to drupal and migrated it to Squarespace. I have to retrieve some pages of drupal site but I can no longer view the site. Do you know any way to get the old content of website on drupal? Please know that we still have access to the drupal box. Any suggestions will be a big help.
Easiest way would be to make the old Drupal site available again through the browser running on a different domain like old.example.com, login into the admin panel and start copy/pasting content.
If you know your way around your computer, know the IP address the old server is running on you could for the time being change the host file of your machine to send requests for your site to the old server and get access to the site that way.
Migrating content by automating the process is also an option, but it is not only time consuming, it requires in depth knowledge of both platforms so is mostly a very expensive solution if you are not able to do this yourself.
But if I read your question, I think the first option is the easiest option. Get a hold of the technical person/party of the server the site is running on and get them to make the site accessible on a different domain.

Multiple Website with Single Database and Different urls WordPress?

I was looking to find a solution for making clone websites of my existing WordPress website. the thing is I want to make clones of the website so if one of them will somehow get down the others will be Live. For Example The Piratebay.com they have a lot of clone sites and I you would upload a torrent to one site all of them will have the same torrent available, this is just for example purposes. I want to make a clone of my website so if I add a new post to my any clone website or the original all of the websites will have the same post available on it. For sure they will have their own domain name. The website will use MySql as the form of database. I have searched all over the internet and on StackOverflow as well and couldn't fine a solutuion
Use the same Cloud MySQL database (e.g. Googles Cloud SQL) for all websites. Install wordpress on the first domain and then just copy the wordpress folder to the other destinations (or modify the wordpress-configuration at the other destinations).
Don't use absolute paths for images in your posts etc. (not http://example.com/something/image.jpg).

Migrating Widget Settings in WordPress

I've done a lot of WordPress migrations from one server to another at work and elsewhere, but one strange thing I've never been able to understand is why widget settings never get carried over.
I'll dump the MySQL database, find/replace localhost with the live domain, SSH the database up to the live server, and then ftp the whole WP installation (core and theme, from my local machine), and still the widget settings are wiped out. And sometimes this is also the case with values saved in theme options pages I make in the Dashboard.
What am I missing?
Wordpress stores widget options - and some plugins and themes also store their options - as serialized data, and so you have to be more careful than a full find/replace of the URLs.
Much more comprehensive answer and some other ways to do move databases and retain serialized data: https://wordpress.stackexchange.com/questions/9076/why-is-my-database-import-losing-text-widget-data
To move a wordpress site and to reconvert all serialized data I used this script.
the using is very simple, download the script, change the credential variable to the database inside the php script and run it.
link to download the script:
http://davidcoveney.com/575/php-serialization-fix-for-wordpress-migrations/
work fine.
Don't do it manually!
Dont edit database manually when migrating between different domains!
Use small scripts, like this:
Wordpress-Migrator.php (read description too.)
because SERIALIZED arrays needs to be modified specifically too!!!

Wordpress theme editing

Well, I am a newbie with Wordpress.
I just got a free wordpress theme. I want to edit the pages to my customization. I have a shared host which provides MySQL database.
Can I edit this wordpress theme to connect to this MySQL database and pull/push data in to my database?
Is the whole process similar to working with normal php and MySQL? Whats so much difference with the set of php's being a Wordpress theme?
Thanks
Themes are just a bunch of php files which get executed in response to some particular event (basically when a particular kind of page nees to be rendered). You can do whatever you want in them, but everything which is not meant to be "aestethic" should probably be developed in a separate set of custom plugins. You then call those from your theme.
Once you have wordpress installed with the hosting provider and the database connection between the WP installation and the hosting provider MySQL database you can edit your theme through WP itself.
Make sure you set the permissions on the WP-Templates (I think thats what it is called) folder to read/write so that wordpress can write to the template files.
View the following link for any help editing the template. How to edit a WP Template
The theme is just the interfacce of your system, on your theme you only show the data, you need to run a select for instance in the apropriate part, also for the bussines logic.
If you do in the interface, in time your system will mess up.
In the official documentation have plenty of examples and How to's,..
The short answer - there are a number of different templates for the index, search, archive, page and article views of a Wordpress theme. Some themes don't include all of them - certain templates are the default for the other optional templates. You can edit them with software like Dreamweaver or a text editor of you choice, or you can alter them from the Wordpress admin panel.
Wordpress themes are a little too complicated to explain in one simple answer, but I can recommend a tutorial. It's a little dated, but it will explain the overall ideas and it's quite good.
Here's another - I've not read it over but it looks to be well done: http://themeshaper.com/wordpress-themes-templates-tutorial/
A theme is a collection of PHP files along with related files (CSS, JavaScript, images, etc.) that control the appearance of the WordPress site. The content (posts, pages, comments, options, plugin configuration, etc.) of the blog is stored in the database. Any themes on the site are thus separate from the content.
Themes can normally be edited directly from the WordPress admin console. Click on "Appearance" and then on "Editor". You can then edit any of the current theme's files from there. Useful for tweaking things if you know what you're doing, but dangerous in some ways because there's no easy way to undo your changes. Do a backup of your theme before noodling with it.
This entry in the WordPress Codex will help:
http://codex.wordpress.org/Editing_Files

Tool to monitor website(html) changes/to get snapshot

Could you recommend me some tool (not online one) to monitor html changes in website or to get complete snapshot of a website?
My task is to migrate current website to the next version of CMS. Migration requires code changes as well, because of new API. The idea is to make snapshot of the website before migration and after. After that I will compare two snapshots and see if migration went OK.
Thanks
Screen grabs (images)
As your web pages may well extend the visible area of your browser window, you'll need a specialized tool for this. For Firefox, I have made some good experiences with Fireshot. It's not fully automatic though.
Copy of the full HTML structure
For an automated solution, have you considered downloading a complete mirror of the web site? I don't mean the old CMS, but the generated HTML output including all style sheets and scripts. Any dynamic functionality would be lost of course, but it should be possible to create a running, local HTML copy of the whole thing that way. I have used GetLeft in the past. Just be sure everything gets downloaded and there are no references to the online version left anymore.
Why don't you make a copy of the entire website folder and after making the changes use beyondcompare to see what has changed. It has a filter to show only differences which will give you what you need (files that changed).
If you're migrating from one CMS to another, then content is most likely in a Database. Just dump the DB at the desired points, then build quick import script to pull in content and map any changes in DB fields.
Not too long ago I moved a site from an old PERL based CMS to a much nicer Zend Framework-based custom CMS. While the DB tables were quite different, every CMS seems to have commonalities such as Title, Content, Blurb, etc fields. It's just a matter of identifying what matches, building the import script, and running. Once the quick script is written, you could pull in updates in the same manner, allowing you to run a beta of the new code and quickly importing updates that might happen between first import and immediately prior to launch of new codebase.