[wp-hackers] WP Development & Production Sites

William Davis will.davis at gmail.com
Tue Nov 23 01:35:13 UTC 2010


Also, SQL dumps are a pain in the ass. Why have WP-import/export at all?

On Nov 22, 2010, at 8:33 PM, Ryan Bilesky wrote:

> that would get everything, even settings from plugins the user may  
> no longer
> have installed.
>
> On Mon, Nov 22, 2010 at 5:28 PM, Andrew Nacin <wp at andrewnacin.com>  
> wrote:
>
>> On Mon, Nov 22, 2010 at 7:41 PM, Ryan Bilesky <rbilesky at gmail.com>  
>> wrote:
>>
>>> what if there was a plugin that could backup the settings you've set
>> from
>>> one site (say a dev site) and import them to another site (say your
>>> production site).  Now I am not aware of any way currently to  
>>> where a
>>> plugin
>>> can know what settings another plugin makes, but you could have a  
>>> txt
>> file
>>> with a list of option names like
>>>
>>> setting1
>>> setting2
>>> ect
>>>
>>> Go though the db and get_option for each of those, save it out to  
>>> a file
>>> like
>>>
>>> setting1:value1
>>> setting2:value2
>>> ect
>>>
>>> Import that generated file into the production site that would step
>> though
>>> that file line by line and update_option to move all settings from  
>>> one
>> site
>>> to another.
>>
>>
>> I believe they call that an SQL dump.
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers



More information about the wp-hackers mailing list