This is the codebase for the expozine site.
It's Wordpress driving the pages & posts, and a CakePHP (1.3) app handling exhibitors, registration and sponsors.
We're using the Wordpress plugin WPML for the multilingual side of things.
I'm putting it up here mainly in case it helps anyone else get wordpress & cake playing together.
Otherwise it's been kept fairly simple.
Uses some .htaccess rewrites to route things to wordpress install in webroot, and in the functions.php of the expozine theme, you'll see we just fetch the fragments we need from cake to display sponsors & exhibitors.
The cake forms are still accessible via direct url.
One change i made in my cake core.php when i went live was uncommenting the config for App.baseUrl, and switching it to:
You may have to change that to suit your setup.
You'll find a copy of the schema in config/schema/expozine.sql. This just contains the sql for the cake component. You should install wp in the regular fashion.
Overall, it's working ok. There's one or two kinks to work out (like logging into admin with a redirect). Accessing via hitting the wp-login.php directly works fine, but trying to log in when redirect is set doesn't work.
Why not use the custom post types/taxonomy in wordpress?
On the surface, it looked like custom post types would be fine. But at the time, I couldn't find any clear answers that I could do what I needed to, including making it bilingual ( one of my biggest gripes with wp - the docs/codex - eg: sometime I search for a problem, and you find stuff from WP 1.5). WPML wasn't clear at the time (it's been updated the last few months). I didn't have the time to go down that rabbit hole. And it's pretty some simple relational data, and form validation. Getting that portion of the site up fast was the motivation.
So the old pages from the site were thrown into cake pages, and Wordpress was added after.
When I have to do this again, I think i would move the cake install to a subdomain, and just install wp on www. I think that might turn out to be the simpler solution. Or, who knows - i may have reason to dive further into wp, in which case, might just go with custom. I've since learnt what I want to do can be done all in wp.
If you have any better suggestions/comments/feedback let me know.