New Howto; How to use the Dev mode

I created a first (small) draft of this howto on the wiki, you can find
it
here: http://dev.radiantcms.org/radiant/wiki/HowToDevAndProduction

I’ve learned this accidentally from the code just a few days ago. It’s
nice
someone took time to wikify this, thanks!

I tried the dev mode out on my Radiant blog the other day but I just
can’t
get Radiant to recognise that it’s running under
dev.digitalblueprint.co.uk.
I’ve tried both server aliases and seperate virtual hosts for the
different
domains but still no go. Has anyone else had a similar problem that
they’ve
managed to fix?

Thanks,
Kevin A.

Technical Director
BN23 Search Ltd.

blog: http://www.digitalblueprint.co.uk

How’s the alias set up? And how’s your radiant installation set up?

2006/9/29, Kevin A. [email protected]:

Well, I currently have it set up as two seperate virtual hosts. One for
www.mydomain and the other for dev.mydomain, both DocumentRoot’s are
referencing the same symlink to radiant/public. The server is running
Apache
1.3 with fcgi.

The Radiant::Config[“dev.host”] is also definately set to “dev.mydomain”

Any ideas? Maybe it’s the server setup, I’ll have a go at getting an env
dump from both domains as soon as I get a moment.

Thanks,
Kev

dev.host should be set to “dev” only. Other than that it should work.

2006/9/29, Kevin A. [email protected]:

OK, I’ve tried it with both “dev” and “dev.mydomain” with no go. Env
dumps
for both domains can be found here if it’s any help:

http://www.digitalblueprint.co.uk/test
http://dev.digitalblueprint.co.uk/test

I’ll have a look at the code later and see if i can see why it’s not
recognising the domains.

Thanks,
Kev

On 9/29/06, Giovanni I. [email protected] wrote:

The Radiant::Config[“dev.host”] is also definately set to “dev.mydomain”
On 9/29/06, Giovanni I. < [email protected]> wrote:

Radiant mailing list
Site: http://lists.radiantcms.org/mailman/listinfo/radiant


Kevin A.

Technical Director
BN23 Search Ltd.

It’s a simple regex on the hostname, are you sure you’re not
redirecting?

2006/9/29, Kevin A. [email protected]:

No, it’s definately not redirecting. Looking at the code, the first
check it
performs is whether or not @request.host == Radiant::Config[‘dev.host’]
so
the config var should definately be set to the full domain, not just
“dev”
as the second check it performs checks for that as the default.

I’ve updated the env_behavior to show the output from the dev? checks,
and
as you can see it’s picking performing them fine (although the logic for
the
default check in radiant may be wrong? - the regex returns 0 if it
detects
the default ‘dev’ subdomain, otherwise nil)

http://www.digitalblueprint.co.uk/test
http://dev.digitalblueprint.co.uk/test

So, even though the dev? check returns true, I still cannot see the
draft
articles on my dev domain. I’ll have to do some further investigation I
think.

Kev

On 9/29/06, Giovanni I. < [email protected]> wrote:

dev.mydomain"
On 9/29/06, Giovanni I. < [email protected]> wrote:

else had a similar problem that they’ve managed to fix?


Search: http://radiantcms.org/mailing-list/search/

Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant


Kevin A.

Technical Director
BN23 Search Ltd.

You don’t see them in the main page, have you tried going directly to
their
url? Because <r:children:each> still doesn’t catch draft pages, even in
dev
mode.

2006/9/29, Kevin A. [email protected]:

Ah, this could very much explain why i thought it wasn’t working. Maybe
a
note could be put up about this on the wiki, I was fully expecting the
site
to act exactly as if everything was set to “published” in dev mode.

Thanks,
Kev

On 9/29/06, Giovanni I. [email protected] wrote:

domain, not just “dev” as the second check it performs checks for that as
So, even though the dev? check returns true, I still cannot see the

It’s a simple regex on the hostname, are you sure you’re not

I’ll have a look at the code later and see if i can see why it’s not

dev.host should be set to “dev” only. Other than that it should

dev.mydomain"
On 9/29/06, Giovanni I. < [email protected]> wrote:

anyone else had a similar problem that they’ve managed to fix?


Search: http://radiantcms.org/mailing-list/search/

Post: [email protected]
BN23 Search Ltd.
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant


Kevin A.

Technical Director
BN23 Search Ltd.

I’ll look into it right now and see if I’m able to fix it. Still
learning my
way into radiant code :slight_smile:

2006/9/29, John W. Long [email protected]:

Giovanni I. wrote:

You don’t see them in the main page, have you tried going directly to their
url? Because <r:children:each> still doesn’t catch draft pages, even in dev
mode.

Perhaps this is an oversight on my part. I’d accept a patch for this if
it is truly a problem.


John L.
http://wiseheartdesign.com

John I looked through the sources to see if I could easily fix this
problem
and I fear it can’t easily be fixed because <r:children> is inside a
model,
and the published state for retrieval is hardcoded in there.

On the other hand the subdomain recognization is controller level stuff.
I
think this is what someone was referring to when he said that Radiant
stretches the MVC boundaries.

2006/9/29, Giovanni I. [email protected]: