<div dir="ltr">I am also plagued with the same issues. I think it would be extremely beneficial to separate what makes a site go from content. They data is so mashed up it is hard to know what ports and what does not.<br>gina<br>
<a href="http://www.wupal.com">www.wupal.com</a><br><br><div class="gmail_quote">On Sat, Aug 9, 2008 at 12:57 AM, Yuval Hager <span dir="ltr"><<a href="mailto:yuval@avramzon.net">yuval@avramzon.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'd like to draw the dev list members' attention to a thread from support<br>
about staging:<br>
<a href="http://lists.drupal.org/pipermail/support/2008-August/009492.html" target="_blank">http://lists.drupal.org/pipermail/support/2008-August/009492.html</a><br>
<br>
The reason I am sending this here, is that I believe there is no structured<br>
and well defined solution to the problem. There are many trials to handle<br>
this (e.g. even/odd nid numbering scheme, dbscripts), but most of them are<br>
cumbersome and/or limited in many ways.<br>
<br>
I believe this is a very common problem, and that the only real solution<br>
should come from core. I think the most difficult part here is to separate<br>
content from configuration. The first step would be how to define what is<br>
content and what is config (for example - site name - is it a content<br>
property or a config property?). The next step then would be to find a way to<br>
transfer config from a staging/dev site onto production, without overwriting<br>
any content that might have been added there during development.<br>
<font color="#888888"><br>
--<br>
Yuval Hager<br>
[T] +972-77-341-4155<br>
[@] <a href="mailto:yuval@avramzon.net">yuval@avramzon.net</a><br>
</font></blockquote></div><br></div>