Hello!
I followed the instructions at http://www.project-open.org/en/install_ubuntu_precise_pangolin to install ]po[ for Ubuntu 12.04. Everything went smoothly, except when I decided not to use the demo data and go for a "clean" install. This means the database was empty.
So I used:
project-open-Update-4.0.4.0.0.tgz
web_projop-aux-files.4.0.4.0.0.tgz
When the process starts that initializes the database I am getting these errors:
*
__Error 1:
__*
Installed Search, version 5.7.0.
Package enabled.
Search not installed.
Error:
site node not found at url ""
site node not found at url ""
while executing
"error "site node not found at url \"$url\"""
(procedure "get_from_url" line 33)
invoked from within
"get_from_url -url $url"
(procedure "get" line 12)
invoked from within
"get -url $url"
(procedure "site_node::get_node_id" line 3)
invoked from within
"site_node::get_node_id -url "/""
(procedure "apm_package_install" line 161)
invoked from within
"apm_package_install -load_data_model -enable -callback $callback $spec_file"
*
__Error 2:
__*
Failed to install Content Repository, version 5.7.0. The following error was generated:
psql:content-create.sql:314: WARNING: changing return type of function cr_items_tree_insert_tr from "opaque" to "trigger"
psql:content-create.sql:369: WARNING: changing return type of function cr_items_tree_update_tr from "opaque" to "trigger"
psql:content-create.sql:639: WARNING: changing return type of function cr_revision_del_ri_trg from "opaque" to "trigger"
psql:content-create.sql:643: WARNING: changing return type of function cr_revision_up_ri_trg from "opaque" to "trigger"
psql:content-create.sql:647: WARNING: changing return type of function cr_revision_ins_ri_trg from "opaque" to "trigger"
psql:content-create.sql:651: WARNING: changing return type of function cr_revision_del_rev_ri_trg from "opaque" to "trigger"
psql:content-create.sql:672: WARNING: changing return type of function cr_cleanup_cr_files_del_trg from "opaque" to "trigger"
psql:content-create.sql:1009: WARNING: changing return type of function cr_keywords_tree_insert_tr from "opaque" to "trigger"
psql:content-create.sql:1070: WARNING: changing return type of function cr_keywords_tree_update_tr from "opaque" to "trigger"
psql:content-create.sql:1132: WARNING: changing return type of function cr_text_tr from "opaque" to "trigger"
psql:content-update.sql:207: WARNING: nonstandard use of \ in a string literal
LINE 1: create function inline_1 () returns integer as '
^
HINT: Use the escape string syntax for backslashes, e.g., E'\'.
psql:content-update.sql:207: WARNING: nonstandard use of \' in a string literal
LINE 1: SELECT 'create view cr_resolved_items as
^
HINT: Use '' to write quotes in strings, or use the escape string syntax (E'...').
QUERY: SELECT 'create view cr_resolved_items as
select
i.parent_id, i.item_id, i.name,
case s.target_id is NULL then \'\'f\'\' else \'\'t\'\' end as is_symlink,
coalesce(s.target_id, i.item_id) resolved_id, s.label
from
cr_items i left outer join cr_symlinks s
on i.item_id = s.symlink_id'
CONTEXT: SQL statement in PL/PgSQL function "inline_1" near line 43
psql:content-update.sql:207: WARNING: nonstandard use of \' in a string literal
LINE 1: SELECT 'alter table cr_folders add
^
HINT: Use '' to write quotes in strings, or use the escape string syntax (E'...').
QUERY: SELECT 'alter table cr_folders add
has_child_folders boolean
default \'\'f\'\''
CONTEXT: SQL statement in PL/PgSQL function "inline_1" near line 52
psql:content-update.sql:207: WARNING: nonstandard use of \' in a string literal
LINE 1: SELECT 'update cr_folders f set has_child_folders =
^
HINT: Use '' to write quotes in strings, or use the escape string syntax (E'...').
QUERY: SELECT 'update cr_folders f set has_child_folders =
coalesce((select \'\'t\'\' from dual where exists
(select 1 from cr_folders f_child, cr_resolved_items r_child
where r_child.parent_id = f.folder_id
and f_child.folder_id = r_child.resolved_id)), \'\'f\'\')'
CONTEXT: SQL statement in PL/PgSQL function "inline_1" near line 56
psql:content-update.sql:207: WARNING: nonstandard use of \' in a string literal
LINE 1: SELECT 'create table cr_text ( text text default \'\' not n...
^
HINT: Use '' to write quotes in strings, or use the escape string syntax (E'...').
QUERY: SELECT 'create table cr_text ( text text default \'\' not null )'
CONTEXT: SQL statement in PL/PgSQL function "inline_1" near line 84
psql:content-update.sql:207: WARNING: nonstandard use of \' in a string literal
LINE 1: SELECT 'alter table cr_items add
^
HINT: Use '' to write quotes in strings, or use the escape string syntax (E'...').
QUERY: SELECT 'alter table cr_items add
publish_status varchar(40)
constraint cr_items_pub_status_chk
check (publish_status in
(\'\'production\'\', \'\'ready\'\', \'\'live\'\', \'\'expired\'\'))'
CONTEXT: SQL statement in PL/PgSQL function "inline_1" near line 95
psql:content-update.sql:207: WARNING: nonstandard use of \' in a string literal
LINE 1: SELECT 'update cr_items set publish_status = \'\'live\'\'
^
HINT: Use '' to write quotes in strings, or use the escape string syntax (E'...').
QUERY: SELECT 'update cr_items set publish_status = \'\'live\'\'
where live_revision is not null'
CONTEXT: SQL statement in PL/PgSQL function "inline_1" near line 101
psql:content-update.sql:207: WARNING: nonstandard use of \' in a string literal
LINE 1: SELECT '
^
HINT: Use '' to write quotes in strings, or use the escape string syntax (E'...').
QUERY: SELECT '
create table cr_scheduled_release_log (
exec_date timestamptz default current_timestamp not null,
items_released integer not null,
items_expired integer not null,
err_num integer,
err_msg varchar(500) default \'\' not null
)'
CONTEXT: SQL statement in PL/PgSQL function "inline_1" near line 147
psql:content-schedule.sql:25: WARNING: changing return type of function cr_scheduled_release_tr from "opaque" to "trigger"
psql:content-type.sql:40: WARNING: changing return type of function cr_type_template_map_tr from "opaque" to "trigger"
psql:content-item.sql:2849: WARNING: changing return type of function cr_items_update_tr from "opaque" to "trigger"
psql:content-item.sql:2874: WARNING: changing return type of function cr_items_publish_update_tr from "opaque" to "trigger"
psql:content-revision.sql:784: WARNING: changing return type of function cr_revision_latest_tr from "opaque" to "trigger"
psql:content-keyword.sql:305: WARNING: nonstandard use of \ in a string literal
LINE 2: returns boolean as '
^
HINT: Use the escape string syntax for backslashes, e.g., E'\'.
psql:content-keyword.sql:305: WARNING: nonstandard use of \' in a string literal
HINT: Use '' to write quotes in strings, or use the escape string syntax (E'...').
CONTEXT: string literal in PL/PgSQL function "content_keyword__is_assigned" near line 47
psql:content-keyword.sql:365: WARNING: changing return type of function cr_keywords_update_tr from "opaque" to "trigger"
psql:types-create.sql:322: ERROR: function acs_object_type__create_type(character varying, character varying, character varying, character varying, character varying, character varying, unknown, unknown, unknown, character varying, boolean, unknown) does not exist
LINE 1: SELECT acs_object_type__create_type ( $1 , $2 , $3 , $4...
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
QUERY: SELECT acs_object_type__create_type ( $1 , $2 , $3 , $4 , $5 , $6 , null, 'f', null, $7 , $8 , 'f' )
CONTEXT: PL/pgSQL function "content_type__create_type" line 41 at PERFORM
psql:types-create.sql:333: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:types-create.sql:344: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:types-create.sql:355: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:types-create.sql:366: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:types-create.sql:377: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:types-create.sql:388: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:types-create.sql:399: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:content-image.sql:36: ERROR: function acs_object_type__create_type(character varying, character varying, character varying, character varying, character varying, character varying, unknown, unknown, unknown, character varying, boolean, unknown) does not exist
LINE 1: SELECT acs_object_type__create_type ( $1 , $2 , $3 , $4...
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
QUERY: SELECT acs_object_type__create_type ( $1 , $2 , $3 , $4 , $5 , $6 , null, 'f', null, $7 , $8 , 'f' )
CONTEXT: PL/pgSQL function "content_type__create_type" line 41 at PERFORM
psql:content-image.sql:47: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:content-image.sql:58: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:content-image.sql:68: ERROR: insert or update on table "cr_content_mime_type_map" violates foreign key constraint "cr_content_mime_map_ctyp_fk"
DETAIL: Key (content_type)=(image) is not present in table "acs_object_types".
CONTEXT: SQL statement "insert into cr_content_mime_type_map ( content_type, mime_type ) values ( $1 , $2 )"
PL/pgSQL function "content_type__register_mime_type" line 24 at SQL statement
psql:content-image.sql:73: ERROR: current transaction is aborted, commands ignored until end of transaction block
psql:content-create.sql:1276: ERROR: insert or update on table "cr_content_mime_type_map" violates foreign key constraint "cr_content_mime_map_ctyp_fk"
DETAIL: Key (content_type)=(content_revision) is not present in table "acs_object_types".
CONTEXT: SQL statement "insert into cr_content_mime_type_map ( content_type, mime_type ) values ( $1 , $2 )"
PL/pgSQL function "content_type__register_mime_type" line 24 at SQL statement
SQL statement "SELECT content_type__register_mime_type('content_revision', 'text/html')"
PL/pgSQL function "inline_1" line 5 at PERFORM
psql:content-create.sql:1350: ERROR: -20000: Invalid parent ID -200 specified in content_item.new
CONTEXT: PL/pgSQL function "content_item__new" line 20 at assignment
PL/pgSQL function "content_template__new" line 25 at assignment
SQL statement "SELECT content_template__new( 'default_template', '-200', $1 , now(), null, null )"
PL/pgSQL function "inline_2" line 8 at PERFORM
psql:content-search.sql:143: WARNING: changing return type of function content_search__itrg from "opaque" to "trigger"
psql:content-search.sql:146: WARNING: changing return type of function content_search__dtrg from "opaque" to "trigger"
psql:content-search.sql:149: WARNING: changing return type of function content_search__utrg from "opaque" to "trigger"
psql:content-search.sql:153: WARNING: changing return type of function content_item_search__utrg from "opaque" to "trigger"
NOTE: If the error comes from a sql script you may try to source it manually. When you are done with that you should revisit the APM and try again but remember to leave the manually souced sql scipts unchecked on the previous page.
*
__Error 3:
__*
Failed to install Messaging, version 5.7.0. The following error was generated:
psql:acs-messaging-create.sql:37: ERROR: insert or update on table "acs_object_types" violates foreign key constraint "acs_object_types_supertype_fk"
DETAIL: Key (supertype)=(content_revision) is not present in table "acs_object_types".
CONTEXT: SQL statement "insert into acs_object_types (object_type, pretty_name, pretty_plural, supertype, table_name, id_column, abstract_p, type_extension_table, package_name, name_method) values ( $1 , $2 , $3 , $4 , $5 , $6 , $7 , $8 , $9 , $10 )"
PL/pgSQL function "acs_object_type__create_type" line 37 at SQL statement
psql:acs-messaging-create.sql:133: WARNING: changing return type of function acs_message_insert_tr from "opaque" to "trigger"
psql:acs-messaging-create.sql:182: WARNING: changing return type of function acs_message_update_tr from "opaque" to "trigger"
NOTE: If the error comes from a sql script you may try to source it manually. When you are done with that you should revisit the APM and try again but remember to leave the manually souced sql scipts unchecked on the previous page.
*
__Error 4:
__*
Installed Subsite, version 5.7.0.
Package enabled.
Acs-subsite not installed.
Error:
Database operation "0or1row" failed
(exception ERROR, "ERROR: query string argument of EXECUTE is null
CONTEXT: PL/pgSQL function "content_type__create_type" line 36 at EXECUTE statement
")
Database operation "0or1row" failed
(exception ERROR, "ERROR: query string argument of EXECUTE is null
CONTEXT: PL/pgSQL function "content_type__create_type" line 36 at EXECUTE statement
")
while executing
"ns_pg_bind 0or1row nsdb0 {
select content_type__create_type(:content_type,:supertype,:pretty_name,:pretty_plural,:table_name,:id_column,:name_method..."
("uplevel" body line 1)
invoked from within
"uplevel $ulevel [list ns_pg_bind $type $db $sql]"
invoked from within
"db_exec 0or1row $db $full_statement_name $sql"
("uplevel" body line 8)
invoked from within
"uplevel 1 $code_block "
invoked from within
"db_with_handle -dbn $dbn db {
# plsql calls that are simple selects bypass the plpgsql
# mechanism for creating anonymous fun..."
(procedure "db_exec_plsql" line 57)
invoked from within
"db_exec_plsql exec_func_plsql {}"
(procedure "package_exec_plsql" line 36)
invoked from within
"package_exec_plsql -var_list [list [list content_type $content_type ] [list supertype $supertype ] [list pretty_name $pretty_name ] [list pretty_p..."
(procedure "content::type::new" line 3)
invoked from within
"content::type::new -content_type "email_image" -pretty_name "Email_Image" -pretty_plural "Email_Images" -table_name "users_email_image" -id_column "e..."
(procedure "subsite::package_install" line 2)
invoked from within
"subsite::package_install "
("eval" body line 1)
invoked from within
"eval $command"
(procedure "apm_invoke_callback_proc" line 37)
invoked from within
"apm_invoke_callback_proc -version_id $version_id -type after-install"
(procedure "apm_package_install" line 155)
invoked from within
"apm_package_install -load_data_model -enable -callback $callback $spec_file"
Anonymous
Please perform the installation with the DB dump provided. Once you have a running system with demo data, please go to ADMIN-> Cleanup Demo Data and remove the demo data that way.