Hello all - We're current trialling Couch (currently it's installed in our dev environment)...

I have to say it's a joy to finally find something that allows US to control our site and not the CMS! It's a fantastic concept and very much complimented by not being 'bloated' like 'others out there'!

One early question I have is how are images (etc) referenced - for example if I install Couch at /var/www and then a bunch of different sites also at var/www which I want to leave alone (so just initially putting the 'necessary' pages from each site "into" Couch) how would add necessary '../' to the image location.

The question may get a bit more complicated further down the road as we have a fairly sprawled architecture as well as managed sites on both our own and clients' own servers (and hosting companies). But I'm assuming the solution would ultimately be pretty much the same.

Thanks in advance!

[KK]

Hi

I think I should make this point clear from the very outset - Couch is *not* a multi-site CMS.
That is to say suppose you have a setup like the following -

Code: Select all

root
    |__site1
    |__site2
    |__site3
    |__site4

To couchify the sites above you'll have to add Couch to each of those sites e.g. as follows -

Code: Select all

root
    |__site1
        |__couch
    |__site2
    |__site3   
        |__couch
    |__site4   
        |__couch

Where in the tree above, only site1, site3 and site4 are Couch managed - site2 will not be managed by Couch as there is no 'couch' folder nested below it.

That is to say, the following will *not* work (i.e. will not make a single instance of Couch manage all the four site present) -

Code: Select all

root
    |__couch
    |__site1
    |__site2
    |__site3
    |__site4  

With that clear, the answer to your question is that you don't need to make any changes to the path of your images if they are not Couch managed (i.e. not uploaded through the Couch admin).

For images uploaded via Couch, the full path is always saved automatically so you don't have to do bother about those anyway.

Does this answer your question? I somehow feel that I was not able to get a complete sense of what you were trying to ask. I request you to please elaborate a little more on the issue.

Thanks.

Hi, I agree, I wasn't looking for a single Couch instance 'over' multiple sites (thankfully due to the small footprint couch has multiple instances are quite feasible) but what I do need is some flexibility over the URL which Couch presents to the site, for example, where my structure is:

Code: Select all

root
    |__site1
    |__couch

instead of

Code: Select all

root
    |__site1
          |__couch

So in the page header, I need to use

Code: Select all

<?php require_once( '../couch/cms.php' ); ?>

instead of

Code: Select all

<?php require_once( 'couch/cms.php' ); ?>

I found (working through the Aurelius example) that images I upload via Couch Admin don't appear (see http://development.graphicomputer.com/a ... c/blog.php)

I'm assuming its simply I need to add

Code: Select all

../

to the URL which Couch is presenting to 'blog.php'. I do realise the obvious solution for this example is to move Couch(!) but that's not a practicle option with all we have on the various production servers... This is just an example to see if it's possible to add some control in this area!

From the site you linked above, if you are speaking only about the image at the top of the aurelius post.. From studying your source code I see the image code as

Code: Select all

<img class="thumb" src="cms:show blog_image" alt="">

as you can see the src=="" is wrong.

Please try this:

Code: Select all

<img class="thumb" src="<cms:show blog_image />" alt="">

It would seem that other images are working fine.
Please let us know if this solves the problem