Pawtucket 2.0.11 Collections Page

Tryg

I am bringing pawtucket 1.7 into the modern world of 2.0.11. Front page is working, but clicking on 'collections' in the front page menu bar reports "No Collections Found".

Execution for the collections click goes to ./default/views/Collections/index_html.php. Here it first tries to set $qr_collections. When I dump $qr_collections, I see a flood of error indications as follows:
"object(CollectionSearchResult)#390 (29) { ["errors"]=> array(0) { } ["error_output":"BaseObject":private]=> bool(false) ["opo_search_config":"SearchResult":private]=> NULL ["opo_db":"SearchResult":private]=> object(Db)#196 (6) { ["opb_die_on_error"]=> bool(false) ["errors"]=> array(0) { } ["opo_db":"Db":private]=> object(Db_mysqli)#197 ..."

So I dumped $qr_collections in the pawtucket 1.7 system and there $qr_collections. seems happy, viz:
"CollectionSearchResult Object ( [ops_table_name:protected] => ca_collections [opo_list:BaseSearchResult:private] => ca_lists Object ( [TABLE:protected] => ca_lists [PRIMARY_KEY:protected] => list_id [LIST_FIELDS:protected] => Array ( [0] => list_code ) [LIST_DELIMITER:protected] => [NAME_SINGULAR:protected] => list [NAME_PLURAL:protected] => lists [ORDER_BY:protected] => Array ( [0] = ..."

Database accesses to view all collections work fine in the 2.0.11 providence context. Object browse and search are working in pawtucket 2.0.11. Collection config files are synched. Nothing reported in /var/log/apache2/error.log or
in the CA app/log files.

darrigan

Hi,
May be something missing in the pawtucket/theme/<your_theme>/conf/collections.conf, if you just replace it by your previous collections.conf file?
In the default file, check the line:

# --- collection type to dipslay on landing page
landing_page_collection_type = collection

By default, the displayed type is "collection", but it could be different, such as "internal" or other...

Tryg

darrigan,

Thanks for the thoughts:. The landing page type is correct in my conf.

the PHP linter says syntax of ./Collections/index.html.php is OK.

Since getVar is a workhorse in CA, I don't suspect the function is flaky.

Providence returns the collection hierarchy correctly in a search for all collections. So I doubt that the database is a prime suspect.

That leaves "collection_results" in the frame and it only occurs twice. First in ./Collections/index.html.php as
$qr_collections = $this-.getVar("collection_results");
and it occurs in the collections controller as
$this->view->setVar ("collection_results", $qr_collections);
which is the result of a database search. Someone, maybe you, had suggested a modified search which I tried to no avail.
Maybe the query is defective--But debugging the PHP-mysql interface is not in my skill set.
I am trying to get pawtucket 2.0.11 working together with providence 2.0.11.

monica

Tryg compare your themes collections.conf with the one in default theme to see if anything is missing/needed in the new version that isn’t there. Same with the files in views/Collections. This is needed if you have just copied your old 1.7 theme to use in 2.0.11.

Tryg

Thanks for looking at this. Turns out that the "accessible on front end" bit was not set, so collections were hidden.

I'd suggest that the error message 'No collections found' might be changed to 'No publicly accessible collections found'