Sounds great. <br><br>As per Ken's advice I've decided to create custom templates even if I strictly speaking didn't need to ( so I'm glad you think so aswell ) , I had felt it was a good idea. And I guess with views, there's always the export feature aswell.<br>
Thanks<br><br><div class="gmail_quote">On Fri, Jan 29, 2010 at 5:15 PM, Alex Barth <span dir="ltr"><<a href="mailto:alex@developmentseed.org">alex@developmentseed.org</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;">
<div class="im"><br>
On Jan 29, 2010, at 11:53 AM, Ken Winters wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Where possible, do everything in code rather than the database.<br>
</blockquote>
<br></div>
Right. Have a look at Features. It helps you export configuration to code and manage it. It does this by relying on other module's export APIs. If you're building a module with configuration options, take a look at CTools/export API for making them exportable. Using CTools/export is best practice for exporting ATM, IMO.<br>
<br>
<a href="http://drupal.org/project/features" target="_blank">http://drupal.org/project/features</a><br>
<a href="http://drupal.org/project/ctools" target="_blank">http://drupal.org/project/ctools</a><div><div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Trying to merge two databases is a giant<br>
pain, but pushing new code and running update.php is fairly painless.<br>
<br>
If you do have to make database changes after the client has already entered data, you'll want to script it (often<br>
using an importer).<br>
<br>
- Ken Winters<br>
<br>
On Jan 29, 2010, at 11:47 AM, Stewart Birch wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello all<br>
<br>
very early on in my Drupal learning process but have been asked to come up with a solution where the client will be entering content on the production site and we may very well be making structural changes ( css etc )<br>
on DEV and changes to the site setup ( for example a page name or somesuch ) , is there a way to seperate the data entered for content types from everything else so when deploying a site to production we can do so without worrying about content being lost.<br>
<br>
Thanks<br>
<br>
Stewart<br>
<br>
<br>
<br>
<br>
<a href="http://www.flickr.com/people/mrbirch" target="_blank">http://www.flickr.com/people/mrbirch</a><br>
</blockquote>
<br>
</blockquote>
<br></div></div><font color="#888888">
Alex Barth<br>
<a href="http://www.developmentseed.org/blog" target="_blank">http://www.developmentseed.org/blog</a><br>
tel (202) 250-3633<br>
<br>
<br>
<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><br><br><br><br><a href="http://www.flickr.com/people/mrbirch">http://www.flickr.com/people/mrbirch</a><br>