Comments on: pkContextCMS: a sneak preview for the worthy

By: John

John — Wed, 13 May 2009 18:52:49 +0000

Just in case anyone else has trouble with saving settings for pages – try turning csrf off – worked for me.

By: John

John — Mon, 30 Mar 2009 12:09:08 +0000

Hey Tom,

Just trying to setup cmstest and getting:

./symfony doctrine:data-load

Notice: Undefined variable: conn in /home/bwdev/playground/pkContextCMS/plugins/pkToolkitPlugin/lib/pkZendSearch.class.php on line 170

Fatal error: Call to a member function getTable() on a non-object in /home/bwdev/playground/pkContextCMS/plugins/pkToolkitPlugin/lib/pkZendSearch.class.php on line 170

And also on the web page I get -

Fatal error: Call to a member function setCulture() on a non-object in /home/bwdev/playground/pkContextCMS/plugins/pkContextCMSPlugin/lib/model/doctrine/PluginpkContextCMSPageTable.class.php on line 69

I like your new demo site generator, you clever sod

John

By: Tom

Tom — Sun, 15 Mar 2009 22:06:54 +0000

Hi John,

Check out the cmstest project. That project uses the usual Symfony default routing rule, which lights up all of your modules at the URL /modulename/actionname, without conflicting with the CMS. As long as the pk_context_cms_page rule comes last and the CMS invokes that rule by name when it wants to make a link to a page (which it does), then there’s no issue.

You could also do individual routing rules for individual actions and put them first to make swankier URLs for frequently seen front end actions.

By: John

John — Sun, 15 Mar 2009 16:59:33 +0000

Hey Tom,

Plugin looks cool! Thanks loads for making it available.

One question . . .

How do you approach the integration of bespoke modules, like a news module for example? In terms of routing (without /cms ) and being able to put a bespoke module/action link in the menu and for clients to move it in the structure?

So you could have /my-cms-page and /news/list and for it to know where to route them and to be able to move them in the menu.

Hope that makes sense.

John

By: Tom

Tom — Sun, 15 Mar 2009 16:04:14 +0000

I’ve just released version 0.13 (and checked it in to svn of course) with further fixes to the routing rules to simplify matters. By using an explicit routing rule name rather than pkContextCMS/show in pkContextCMSTools::urlForPage() I’m able to implement short URLs to CMS pages without conflicting with the default Symfony rules, which is very handy.

By: Tom

Tom — Sat, 14 Mar 2009 14:29:11 +0000

I’ve fixed this- do an svn update of your cmstest project and a symfony cc. I also released it as version 0.12. I opted to move the fancy “override the root of the site” routing rules to the cmstest project and documented the technique in the manual. The CMS plugin now defaults to the wimpier “everything in the CMS is under /cms unless you change the rules to suit your needs” approach. Most people won’t want that but it’s easy to override at the app level.

Thanks to Stephen for his analysis of the issue.

By: Stephen Ostrow

Stephen Ostrow — Sat, 14 Mar 2009 01:19:29 +0000

Tom,
And I guess beleneglorion if you want to get this thing going because it looks cool so far.

First
/plugins/pkContextCMSPlugin/modules/pkContextCMS/templates/_login.php
Line 14 should read:

* Notice I’m using the routing name instead. It’s cleaner.

Second, the main problem with the routing is line 11 of
/plugins/pkContextCMSPlugin/lib/pkContextCMSRouting.php

You’re making this a catch all basically is what’s killing the other routing rules. So You can prefix this with something or change it to
$r->appendRoute(‘pk_context_cms_show’,

and then remove the default_index route from /apps/frontend/config/routing.yml

I personally chose to go with the latter, but it means the whole site will have to go through the cms which is fine for me.

By: Stephen Ostrow

Stephen Ostrow — Sat, 14 Mar 2009 00:51:32 +0000

Tom,
Figured I’d let you know your routes are messed up. Well the pkContext routes are messing with the sfGuard Routes. So when you get to the login page, you’re going to /cms/sfGuardAuth/ for some reason rather than to /login which is the correct route for @sf_guard_login. But the form there is submitting to action /login which doesn’t exist. Same as /logout doesn’t exist either. When I commented out your route registration I was able to login. Then I re-enabled it and I can use the system.

By: Stephen Ostrow

Stephen Ostrow — Sat, 14 Mar 2009 00:31:26 +0000

Tom,
I don’t know if this is what beleneglorion meant. But when I try to login with the default sfDoctrineGuardPlugin credentials I get redirected to a 404 page. This is a clean checkout of the cmstest project. Thanks for any help.

By: Tom

Tom — Fri, 13 Mar 2009 22:56:19 +0000

Hi beleneglorion,

You’re looking at a default install of sfDoctrineGuardPlugin when you’re looking at that admin screen. Log in as user admin password admin.

We’ve set up a publicly accessible place to submit trouble tickets etc. Of course comments here are welcome as well. To talk to me directly write to tom@punkave.com.

Cheers!