{ * Mild Adult Content * } EscortsNZ.com

Hey Guys

This ones slightly ’adult’ so don’t look at it if T&A offends you.

Here’s the link

http://www.escortsnz.com/

Hi,

nice site indeed.

I’ve found a bug when you look at model details. As I could not explain it properly, here is a screenshot (browser Safari V2)



:-)

Edit: one more, when you are in minigallery search input overlay images.

Quote from: heliotrope at May 05, 2006, 09:29 AM

Hi,

nice site indeed.

I’ve found a bug when you look at model details. As I could not explain it properly, here is a screenshot (browser Safari V2)



:-)

Edit: one more, when you are in minigallery search input overlay impages.

- thanks!

You know the title description just makes everyone click

Nice site I like this one best

http://www.escortsnz.com/index.php?id=53

Quote from: daniel591992 at May 06, 2006, 01:37 PM

You know the title description just makes everyone click

Nice site I like this one best

http://www.escortsnz.com/index.php?id=53

haha - she’s expensive, as the story goes

Hi Starbuck,

The method I would adopt for adding extra fields would be to create a x-ref table (id, site_content_id ....)
and then you can add as many fields as you want and just join the tables when you run queries etc.

That way, you future-proof the setup against any future MODx upgrades that might add fields that could conflict with your fields.

Anyway, nice site you have there

Cheers, Garry

Quote from: garryn at May 06, 2006, 02:21 PM

Hi Starbuck,

The method I would adopt for adding extra fields would be to create a x-ref table (id, site_content_id ....)
and then you can add as many fields as you want and just join the tables when you run queries etc.

That way, you future-proof the setup against any future MODx upgrades that might add fields that could conflict with your fields.

Anyway, nice site you have there

Cheers, Garry

Thanks Garry. The adding of the fields works, but I get your point about future proofing

Quote from: Starbuck at May 06, 2006, 03:04 PM

Quote from: garryn at May 06, 2006, 02:21 PM

Hi Starbuck,

The method I would adopt for adding extra fields would be to create a x-ref table (id, site_content_id ....)
and then you can add as many fields as you want and just join the tables when you run queries etc.

That way, you future-proof the setup against any future MODx upgrades that might add fields that could conflict with your fields.

Anyway, nice site you have there

Cheers, Garry

Thanks Garry. The adding of the fields works, but I get your point about future proofing

One thing to also keep in mind when future-proofing is that 1.0 will feature a significant change in the way content is handled. Since we will be supporting native revisioning and rollback of all MODx content, as well as maintaining revisions by culture (i.e. a combination of language and other localized presentation preferences that might be more granular than just language), just creating an xref table may not be completely cover the "future-proofing" in this case, but the isolation it will provide you should help you migrate it to the new structures easily and with a minimal amount work.

Quote from: OpenGeek at May 07, 2006, 01:38 PM

Quote from: Starbuck at May 06, 2006, 03:04 PM

Quote from: garryn at May 06, 2006, 02:21 PM

Hi Starbuck,

The method I would adopt for adding extra fields would be to create a x-ref table (id, site_content_id ....)
and then you can add as many fields as you want and just join the tables when you run queries etc.

That way, you future-proof the setup against any future MODx upgrades that might add fields that could conflict with your fields.

Anyway, nice site you have there

Cheers, Garry

Thanks Garry. The adding of the fields works, but I get your point about future proofing

One thing to also keep in mind when future-proofing is that 1.0 will feature a significant change in the way content is handled. Since we will be supporting native revisioning and rollback of all MODx content, as well as maintaining revisions by culture (i.e. a combination of language and other localized presentation preferences that might be more granular than just language), just creating an xref table may not be completely cover the "future-proofing" in this case, but the isolation it will provide you should help you migrate it to the new structures easily and with a minimal amount work.

I guess we’ve got a custom cms.. working with modx.

We just put rss in.