WordPress Ideas » Tag: config - Recent Posts

WraithKenny on "Export/Import Wordpress configuration file"

WraithKenny — Thu, 23 May 2013 15:00:15 +0000

The importer was updated with a ton of new hooks recently.

cyberwani on "Export/Import Wordpress configuration file"

cyberwani — Wed, 08 May 2013 09:29:53 +0000

WraithKenny on "Export/Import Wordpress configuration file"

WraithKenny — Tue, 22 Jan 2013 19:12:25 +0000

From a plugin/theme standpoint, you could use meta_data on a private CPT to store your options instead of options. Then the importer would work. Additionally, you could do some sort of versioning as a bonus. Seems like a hassle tho.

Ipstenu (Mika Epstein) on "Export/Import Wordpress configuration file"

Ipstenu (Mika Epstein) — Fri, 18 Jan 2013 21:17:25 +0000

I don't think there is a ticket, but it does get talked about.

WraithKenny on "Export/Import Wordpress configuration file"

WraithKenny — Fri, 18 Jan 2013 21:08:16 +0000

A hook system could make the export of theme/plugin settings opt-in. On export, look for setttings marked for export, and on import, check if plugin/theme is installed. the signature for it might be something like exportable_option( 'my_option', 'my_plugin' );

WraithKenny on "Export/Import Wordpress configuration file"

WraithKenny — Fri, 18 Jan 2013 21:04:01 +0000

This thread is marked with "working on it" but I couldn't find a ticket for it.

Ipstenu (Mika Epstein) on "Export/Import Wordpress configuration file"

Ipstenu (Mika Epstein) — Mon, 03 Sep 2012 14:32:21 +0000

The import/export is intended for posts/pages only (and actually as menus are a CPT, they should be getting brought over as well).

Settings are complicated, as many are per-plugin or per-theme, and WP can't know what it doesn't know. The only workaround I could think of is if WP gave hooks that they could latch into so it would be detected on export, but even then

1) You'd have to have the plugin/theme on the new site
2) The plugin/theme would have to actually use the hooks (which we can't assure)

Speaking of links... Please check out http://core.trac.wordpress.org/ticket/21307 - We're talking about removing it and replacing with a plugin.

basememara on "Export/Import Wordpress configuration file"

basememara — Mon, 03 Sep 2012 11:50:23 +0000

The built WP import/export goes a long way, but falls short on a few major "core" areas. Here are my humble requests for the builtin import/export tool:

1. Settings
3. Links
4. Menu's

Although you can get to the DB and file level for this, many times the old site is corrupted, hacked or going to be completely redesigned.

Ipstenu (Mika Epstein) on "Export/Import Wordpress configuration file"

Ipstenu (Mika Epstein) — Mon, 04 Jun 2012 11:35:50 +0000

The easiest way is to export the DB, do a search/replace for localhost/yourdomain and import that into BlueHost.

Works just like this: http://codex.wordpress.org/Moving_WordPress#Moving_WordPress_to_a_New_Server

Basically your local install is the old server :)

DB: all your posts content, theme settings

Files: all the files that run WP, plugins, theme design, images

beanneu on "Export/Import Wordpress configuration file"

beanneu — Sun, 03 Jun 2012 14:52:07 +0000

After three days of trying to upload my local test site to bluehost I agree it's crazy not to have this. Folks here are talking about doing it manually, which I'm willing to do but not sure how to do that. I made a child theme from 2010.I'm new to WP, so I can't get clear on what is stored in mysql db (or how to it export correctly) and what is stored in WP files......permissions seem to be getting me..

If I export under tools, sounds like I lose themes changes, widgets, what about media content....sorry to be such an idiot brain is fried......

Realize building a local test site was probably a bad idea.