Tonight is the night! ;) After some thinking over i think i ll keep the actual html in root as it is now, i will move the whole Drupal installation to root but just remove/rename index.php so user will still be routed to the actual index.html. Then i will create in /sites 2 folders named www.mysite.com.island1 and www.mysite.com.island2 and add to each one a settings.ini In this way i ll be able to: 1-keep on working on the site theming 2-begin to add content on each site separately When the site will be ready all i ll have to do is redirect the links from the index.html i have in root to the 2 sites respectively.
The only concern is about what can happen when you have a drupal installation in root and some html code at the same time
Simone
On Mon, Dec 15, 2008 at 12:27 PM, simone-www. io-lab. org cimo75@gmail.com wrote:
ok, more reading.
Right now i have some html in www.mysite.com, the main drupal installation is in www.mysite.com/island1
My plan is: move the actual html content in a subfolder, modify the .htaccess of the main site to point to that folder so i can freely work in root
Create a new settings.ini in the proper folder for www.mysite.com/island2 and modify the settings.ini file in www.mysite.com/island1 accordingly.
Create a new html file in root with the island switcher and, when everything is ready, change back the .htaccess file to point to that html file.
I d really appreciate some opinion about my plan, especially i d like to know if there is anything wrong with keeping the drupal installation in www.mysite.com/island1 or is it best practice to have the main installation in www.mysite.com
Simone
On Sun, Dec 14, 2008 at 1:06 PM, Christopher M. Jones cjones@partialflow.com wrote:
Links are content. Or, arguably, configuration. These should be kept separate from presentation, which is the domain of the template. That is to say your template should be as content agnostic as possible. When you build your template, try to pretend that you're building it so that anyone could use it, for any purpose. It's just best practice programming.
simone-www.io-lab.org wrote:
I have to admit that i can follow the general idea but i need to dip my toe in it to get a wider overview. I d like to ask: why is it not advised to use hard coded links in my template? It definetely makes sense to me but i don t know why, probably because i ve never seen it before. I ask it becasue i ve solved a problem i had doing just that: i have a menu where i wanted to have only linked images and no text, and i have only 4 items that won t change in the future, so i ve hardcoded them in my template and put them inside a div and added an id each so i can style them.
Back t the "island switcher" I would prefer not going back to create a region and a block in it if possible but rather substitute the link which is hardcoded now with a variable and .... ok there my knowledge ends.. time for some readings, i d like to mention that i am in Drupal 6 so if can point me out to some interesting topics please remember that, it seems like doco for D6 is not so uptodate as for D5.
Simone
On Fri, Dec 12, 2008 at 1:05 PM, Christopher M. Jones cjones@partialflow.com wrote:
Yes, you are sharing it. Sorry, I didn't follow your other thread. Don't know what your template looks like, but you could just as well create a menu in each site. In your page.tpl.php, instead of hard-coding the link you simply say
<?php if( $region ){?>
<div id="region"><div id="region-inner"> <?php print $region; ?> </div></div> <?php } ?>
In your template.php you add your region into the array that contains all the other regions. Now this region is available in your blocks administration. In each site you can create a menu to place into this region, with links that point exactly where you want them to point. May be a bit more work, but this method has the advantage of avoiding too much conditional logic in your template. And IMHO, links should not be hard coded into the template.
simone-www.io-lab.org wrote:
Hi the "island switcher" button is created on page.tpl.php, and i am sharing this file on both sites (or not??), i think i have to replace the link with a php function such as <?php print $front_page ?> (see my other post "Adding link to image (logo style)"). In fact I have 2 buttons (images) created in page.tpl.php, one links to home page, the other one links to the home page of the other site. Simone
On Fri, Dec 12, 2008 at 3:17 AM, Christopher M. Jones cjones@partialflow.com wrote:
What will happen is: you will install your sites, set each one up to use it's own database, or prefix within the same database. For each site you will choose your template, available to each because it's located in sites/all/themes. Now each site looks the same. But you'll find that when you set up your menu in one, it won't appear in any of the others. Different databases, you see.
simone-www.io-lab.org wrote: > Ok thanks, i am trying to figure out all the details: there will be a > button in each page that will link to the other one, that sounds a bit > tricky since i plan to share the same theme but i am sure there is > common way to go... > Simone > > On Fri, Dec 12, 2008 at 12:29 AM, Shyamala Rajaram > shyamala@netlinkindia.com wrote: >> We have sites running as multisites, it works just fine! >> >> >> >> For multisite on windows: >> >> http://drupal.org/node/32715 >> >> >> >> Read 'settings.php', in the sites/default folder, to understand how drupal >> searches it's folder to locate the file storing a particular domain's >> settings.php. >> >> >> >> Drupal by default reads the settings.php file in the default folder. You can >> configure the main portal settings in the default directory. The subdomains >> a.com and b.com can be configured by creating two new folders under the >> sites directory called yourdomain.a.com and yourdomain.b.com. Each of these >> folders should have it's own settings.php. In the settings.php of each site >> you have to name the database to be used. >> >> >> >> If you want some settings to be shared between the sites you could go in for >> a shared database configuration. >> >> >> >> refer: http://drupal.org/node/147828 for >> >> Multi-Site, Single Codebase, Shared Database, Shared Sign-on 5.x >> >> >> >> >> >> Shyamala >> >> Netlink Technologies Ltd >> http://shyamala-drupal.blogspot.com/ >> >> >> -----Original Message----- >> From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On >> Behalf Of simone-www.io-lab.org >> Sent: Thursday, December 11, 2008 6:26 PM >> To: support@drupal.org >> Subject: [support] Double site >> >> Hi >> I ve read a bit about multi site installation, but still i am not so >> sure about how to go: >> I ll have basically 2 "twin sites" each referring to a different >> island in the same archipelago, the structure both on content >> management and on the theme graphic will be the same but all content >> will be different and i d like to have the 2 sites on 2 different >> databases. >> first site: www.mysite.com/islandx >> second site: www.mysite.com/islandy >> of course at www.mysite.com there will be an island chooser >> considering i ll have to change details on the future i d like to have >> the 2 sites using the same theme and the same module folder although i >> think i need 2 different installations (to get the 2 contents on 2 >> different databases) >> It s clear to me how to have a site using different themes but not >> really the other way round.. >> Any hint is welcome >> Simone >> -- >> .wmv , .wma , .pps along with all proprietary Windows formats won t be >> accepted and/or viewed.... >> -- >> [ Drupal support list | http://lists.drupal.org/ ] >> >> -- >> [ Drupal support list | http://lists.drupal.org/ ] >>
>
[ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- .wmv , .wma , .pps along with all proprietary Windows formats won t be accepted and/or viewed....