Failed to initialize Xanthia theme engine :: Zikula Community

Donate to Zikula

Installation, Configuration, & Upgrades ::
Failed to initialize Xanthia theme engine

Print topic

fleshymidget

rank: Freshman

registered: January 2005

last visit: 25.03.05

Posts: 3
Posted: 17.01.2005, 04:07

Hello there.
Ive been trying to upgrade my PostNuke from 0.7.2.6-Phoenix to the new 0.750 i downloaded from this website. Ive found fairly minimal documentation on the upgrade process, and kind of gave up and thought it would just work.. i followed these directions and the system seems to upgrade fine from the installer. But then when i visit my postnuked site all i get is :

Quote
Sorry! Failed to initialize Xanthia theme engine for theme: PostNuke

Ive tryed to run the PostNuke Swiss Army Knife, and /psak.php comes up with an internal server error msg. 500, Ive never used this tool before so maybe im doing somthing wrong.

Also at the end of the upgrade installer it says remember to modify your config.php before you use your website. But i cant think of anything i can modify that wont change my DB settings. And ive tryed duplicating the DB and changing the settings.

Im kind of stuck here now because i dont know much PHP at all, and there isnt many options initialize Xanthia theme engine.

Im running PHP 4.3.9 and SQL 4.0.20-standard.
Any help would be greatly appreciated. Ive tryed searching the forums for an answer.
Thanks in advance
Sam
mrmuttley

rank: Helper

registered: January 2004

last visit: 15.04.06

Posts: 195
Posted: 17.01.2005, 06:44

Check that there is a "pnTemp" directory in the top level of your the directory where you installed PostNuke (usually public_html or htdocs). Check the permissions of the pnTemp directory and all sub-directories in that directory. Your web-server must have permission to write to these directories. The method of changing permissions will depend on the OS your server is running.

Note:

You should be following the instructions that were provided in the PostNuke 0.750 archive you downloaded from this site. The file you should look for is HTML\docs\manual.txt. I have provided a copy of this below:

Quote

PLEASE READ ALL OF THIS DOCUMENT BEFORE INSTALLING OR USING PostNuke

PostNuke: The Phoenix Release (0.7.5.0)
=======================================

PostNuke is an open source, open developement content management system
(CMS). PostNuke started as a fork from PHPNuke (http://www.phpnuke.org) and
provides many enhancements and improvements over the PHP-Nuke system. PostNuke
is still undergoing development but a large number of core functions are now
stabilising and a complete API for third-party developers is now in place.

If you would like to help develop this software, please visit our homepage
at http://noc.postnuke.com/

Or at the Community Forums located at:
http://forums.postnuke.com/

New Installation
================

PostNuke has a fully graphical install process to provide a simple set of
steps to get your site up and running.

Prior to running the installer ensure that both config.php and config-old.php
are world writable. Further ensure that pnTemp and it's subdirectories are also
world writable. World writable means a permission setting of 777 or 666 depending
on your system if the system is unix based.

To install your PostNuke system run install.php from your browser to start
the installation process. The exact URL depends on your site, but for example
if your site is www.foo.com and PostNuke is installed in the 'bar' directory
then the URL will be

http://www.foo.com/bar/install.php

Follow the instructions in the installation script and when prompted for
either a new install or an upgrade select 'new install'. The installer will
create the required database tables and obtain information about the super-user
login. Once complete you should be able to start using your PostNuke site
immediately.

Note: it is important to remember in the case of new installs, that are also to create
the database, that the mysql user, most have full rights to create new databases, if not
then first create the database and grant the intended mysql user full rights to it, so
that it becomes possible for the installer and modules to interact freely, with the new
database and work correctly.

PostNuke now supports the new PHP 4.2.x+ security standard of
register_globals turned off and Apache 2.0.x.

ADDENDUM: For those that asked the mysql dump has been included if you use this
instead of the installer then take note that the admin user is: "Admin" and its
password is "Password", both case sensitive.

In order to install PostNuke this way you need to have shell access to your server
and issue the following commands.

mysqladmin create your_db_name -p

Then:

mysql your_db_name/www.foo.com/bar/install.php

Follow the instructions in the installation script and when prompted for
either a new install or an upgrade select 'upgrade', then pick the version of
PostNuke (or another Nuke variant) which you wish to upgrade from. The rest of
the procedure should be automatic.

Once installation is complete you will need to re-add your custom modules and
regenerate from the modules admin. As part of the upgrade some modules may be
ugraded. From the modules admin Upgrade and re-activate any modules require it.

Caution
=======

Previous versions of PostNuke and other derivatives often include plugins
that alter the database core tables through adding fields, changing names, etc.
It should be noted that PostNuke does not support any modification of the core
tables (those that come with this PostNuke distribution) or direct access to
the core database tables. APIs are provided for developers to use for these
purposes, so that future planned changes will have a minimal impact on
third-party added functionality, and should be used at all times.

Common Installation Errors
==========================

config.php and config-old.php not world-writable - these files need to be
writable by the webserver process during the install/upgrade to ensure that
certain configuration parameters are stored. The install procedure should
check for this and inform you if the files are not writable. Note that once
the install/upgrade has been completed these files can be re-set to read-only.

Problems creating or populating the datbase - this is often due to
incorrect MySQL privileges on the database. If you are unsure if this might be
the case then try to access your MySQL database manually with the username and
password that you have and attempt to create a database and table to ensure
that the user exists, has a correct password, and is able to carry out the
operations that PostNuke needs for installation.

Problems logging in - this is normally due to access the postnuke site with
an unqualified host name e.g. http://localhost/index.php or a domain name e.g.
http://foo.com/index.php PostNuke requires that the site name is
fully-qualified e.g. http://www.foo.com/index.php Instructions on setting up a
fully-qualified hostname for your local server can be found on the PostNuke
documentation site at http://docs.postnuke.com Alternatively you can set the
'intranet' option when installing or upgrading PostNuke, which will allow you
to run PostNuke without a fully-qualified domain name but without the ability
to filter cookies from similar domains. In most cases where PostNuke is run
like this it should not be an issue, however setting your site to run as an
intranet site when it is directly connected to the internet is not recommended.

Enjoy!
Cheers

The PostNuke Development Team
fleshymidget

rank: Freshman

registered: January 2005

last visit: 25.03.05

Posts: 3
Posted: 17.01.2005, 11:49

thanks alot for your help. Now im going to start again from scatch with my backups and see how i go, im fairly sure the only step i missed was the second .. all my permissions were set right.

The PNtemp dir , is that used mainly for the install or mainly for a working PostNuke site. ??
mrmuttley

rank: Helper

registered: January 2004

last visit: 15.04.06

Posts: 195
Posted: 17.01.2005, 12:13

It's used for a working site. Complied pnRender and Xanthia templates end up in subdirectoriies of pnTemp. The core devs can probably better describe the other purposes than me.