Support Forum

Actualy you should get an info message, where pagemaster is looking for the templates and did not find. Then the generic template is shown. But only with admin rights.

Well, I try to understand but the results are...
I explain my installation from the beginning:
I work with pn.8
1/ I download pagemaster from the SVN
2/ I upload the includes and module folder on my server
3/ I activate pagemaster from admin panel
4/ I go to pagemaster admin
5/ In parameters: for upload path I have "datas" (but I don't know if pagemaster want the full server path or a relative path from /modules/pagemaster
6/ I create a new publication call MyTest filling only the required field and "save" (or record it)
Fine it appears in my PublicationTypes list
7/Clicking on the title ofthe publication go to publicationtype manager where I notice some changes like names for output and input templates
8/I went again to PublicationTypes list and add to fields in MyTest fields manager (title and main(choosing scribite in extra field))
9/ Back from PublicationTypes Manager for create a new article
10/ He tells me that I could create my own form template

Code

This is a generic Template. Your can create individual Templates in the the directory '/pntemplates/pnForm/pubedit_{STEPNAME}_{$tid}.html'.

Fine but for the moment I used the default one (scribite work fine)
I choose view in pub list and approve...
And arrive on report errors page:

Code

This is a generic Template. Your can create individual Templates in the the directory '/pntemplates/pubdata/publist_{$tid}.html'. Take publist_template.htm as a template.

Exit-Handler: Exiting after SQL-error Stacktrace: Exit-Handler: Exiting after SQL-error Stacktrace: Exit-Handler: Exiting after SQL-error Stacktrace: template not found: output/publist_MyTest.htm

11/in pntemplate directory I found the publist template... I made a copy, rename it as publist_MyTest.html and upload it in output folder.
12/I refresh the page...
Damned PostNuke informe me that:

Code

Table 'demo.pn_pagemaster_pubdata2' doesn't exist
SELECT pm_id AS "id",pm_pid AS "core_pid",pm_online AS "core_online",pm_indepot AS "core_indepot",pm_revision AS "core_revision",pm_showinmenu AS "core_showinmenu",pm_showinlist AS "core_showinlist",pm_publishdate AS "core_publishdate",pm_expiredate AS "core_expiredate",pm_language AS "core_language",pm_8 AS "title",pm_9 AS "main",pm_obj_status AS "obj_status",pm_cr_date AS "cr_date",pm_cr_uid AS "cr_uid",pm_lu_date AS "lu_date",pm_lu_uid AS "lu_uid" FROM pn_pagemaster_pubdata2 WHERE pm_showinlist = 1 AND pm_online = 1 AND pm_indepot = 0 AND (pm_publishdate <= NOW() or pm_publishdate is null) AND (pm_expiredate >= NOW() or pm_expiredate is null) 

and pagemaster

Code

Exit-Handler: Exiting after SQL-error Stacktrace: Exit-Handler: Exiting after SQL-error Stacktrace: Exit-Handler: Exiting after SQL-error Stacktrace: template not found: output/publist_MyTest.htmExit-Handler: Exiting after SQL-error Stacktrace:

(I first try to go to publicationtypes manager and list articles and obtained the same result)
13/In my memories, it reminds there's an other choice when I create the publication: Update tables in DB
I clicked it and try again to list my article. (of course there was none because no table to record it)
14/ I create a new article...but after approve it nothing happen only a pagemaster error message

Code

Exit-Handler: Exiting after SQL-error Stacktrace: Exit-Handler: Exiting after SQL-error Stacktrace: Exit-Handler: Exiting after SQL-error Stacktrace: template not found: output/publist_MyTest.htmExit-Handler: Exiting after SQL-error Stacktrace:

... but publist_MyTest.htm is in my pagemaster/pntemplates/output
15/Back to publicationtypes manager and try to list article again:
In list of publications... nothing (execept no output template and new article link)
In Admin list of publications I could edit my article and view history but if I want to view it, once again there's a pagemaster error with outup template (no viewpub_MyTest.htm... that's right) and pnRender (I suppose) open a pop window with many information)
Here I stop my test, because I'm unable to go away.

Thanks for your complete test report.
Actually, you dont need to put any templates into /input or /output for havin a working pagemaster. You should be able to insert/edit/show publications with the generic ones. I propose to delete them and start using them after you can insert/edit/show publications with the generic templates.

"Update tables in DB I clicked it and try again to list my article." This is something you have to do, everytime you change the fields. I will print out a better error message, if the table are not available.

Is the server online? URL? Then I would have a look on it.
Are you using the SVN version?

spax

This looks like a Bug of Module in PostNuke, because these dependency functionality is not implemented in pagmaster, rather in PostNuke core.
May you should open a bug in tracker of PostNuke.

Marco,

The problem with the dependancies is with pagemaster. In your dependency list you've used the module display names not the real module name. Since the display name can change you *must* use the real module name. So 'scribite!' must be 'scribite' and 'thumbnails' must be 'Thumbnail'.

After this change, tested using revision 145 of SVN, pagemaster installs fine.

-Mark

Thanks for the tip, I will change this asap

I give you information for online URL by pm

I'm using SVN

Hi,

I test after checking a comparaison with my online version and the SVN 145.
So there are many not updated file on my version. Many problems have solved.

But I still have the pnRender's debugg window (I suppose) opening when I try to view a publication.

pnRender's debugg window is desired with the generic templates and admin rights.
If you want it to disapear, you have to create your own templates, without the lin
[--pndebug--] line in it.

fyi, you should not change workflow of publicationtypes which have allready publications. Then workflow will not been found anymore

ok I found it and desactivate it.
Great.

I could try next step soon : working on template.

If I understand, I can start my template with generated code in publicationtypes manager.

I copy pnform code in an edit pnform code in a input/pubedit_MyPub_all.htm
And for the twice basic output (list and view) I can use the respective generated code in indicated files in output folder.

Is there tips for rss templates or block templates??

May I have a suggestion?
Why do not use template name as in page setter such as MyPub_typeoftemplate.htm instead of typeoftemplate_MyPub.htm?
In the templates directories it is easiest to sort the template by publication.
(If I don't say another bullshit... MagicConfuse with synchronization...)

Hi spax,
Looks all great thus far! I'm missing an equivalent for pagesetter_admin_getPublicationTypes. I see in pnblocks/list.php (and in a few other places) something like this:

Code

$pubTypesData = DBUtil :: selectObjectArray("pagemaster_pubtypes");

$pubTypes = array ();
foreach ($pubTypesData as $pubType) {
    $pubTypes[] = array (
        'name' => $pubType['title'],
        'id' => $pubType['tid']
    );
}

Any chance of making this into an API function?

Hi

I often have this problem during programming in .8. It's very easy to get an array DBUtil :: selectObjectArray("pagemaster_pubtypes");
so is it better to create an API function, which does exactly this? It needs more code and is slower...

foreach ($pubTypesData as $pubType) {
$pubTypes[] = array (
'name' => $pubType['title'],
'id' => $pubType['tid']
);
}
I hade to do, because I was too lazy to do the block complete new and copied the Pagesetter block, and had to be compatible to the code, so I needed this array in this format.

spax

I often have this problem during programming in .8. It's very easy to get an array DBUtil :: selectObjectArray("pagemaster_pubtypes");
so is it better to create an API function, which does exactly this? It needs more code and is slower...

I definitely see your point, but an API function allows me to call the method from outside (independent of the internal workings) . So perhaps both is an option?

I would prefere a solution, with its possible to cache stuff in a static variable, because with this I could safe a few of DB queries.
For sure this could be implemented in a API function.

A quick solution for you could be to create a pnuserapi folder an put the function in it -> 10 mins work for you

spax

A quick solution for you could be to create a pnuserapi folder an put the function in it -> 10 mins work for you

Sure, no problem, I'll do that.