Problem creating Pawtucket2 pages

I'm running the latest version of Providence from GitHub. When I click on "New Page" on 


I get this message:

Invalid parameter type for template_id


  • Hi bhoggard,

    You need to set up template types in template.conf and then run the utility scan-site-page-templates from the support folder in your Pawtucket installation.
  • Hello sophie,

    I'm glad I found this thread and your reply, as I'm having the same problem. I'm still strugglin tho:
    1) I'm not able to find the template.conf on my installation or in github, can you provide me the path?
    2) Is this documented somewhere? I've been looking for a while and couldn't find anything.

    Thanks for your help!
  • Hi Ammo,

    The templates feature is brand new and still under active development, so it is not documented yet.  You'll find an example of the templates.conf in the latest version of the default theme on the develop branch:
  • Thank you so much Sophie, yes I found it now, was looking for template.conf before.

    I have enough to start tinkering with it and get to know if at the stage it is right now, thank you!
  • I managed to edit Pawtucket Templates in Providence (I had to set up an editor for site pages) but how do you manage to show those pages in Pawtucket2?
  • Hi kbecker,

    After you've set the path in your site page editor, such as /About/faq (including the first backslash), you can link to page using the standard caNavLink() function.  For example,

    print caNavLink($this->request, 'Frequently Asked Questions', '', '', 'About', 'faq');
  • edited May 2019

    Sophie, I was able to make and customize pages. Only, it seems that PHp session variables cannot be read.
    Example: this line of code at the beginning of the template <?php $g_ui_locale=$_SESSION['g_ui_locale'];?> does not get any value. Obviuosly, PHP in custom pages is enabled (allow_php_in_site_page_templates = 1 in app.conf).

    Any hint? I am working with pawtucket2 v. 1.7.8.
    thank you!

  • oops... found trick... just put before using the variable the statement: global $g_ui_locale;

Sign In or Register to comment.