Impression: install error (trunk version)
Hello,
I installed the trunk version of impression. If I use the module as "impression", the installer works fine. But in my case I renamed the module from impression into "blog". Now I get the following error under ImpressCMS 1.3:
This page cannot be displayed due to an internal error.
You can provide the following information to the administrators of this site to help them solve the problem:
Error: Handler does not exist
Module: blog
Name: altcat
Warning: constant(): Couldn't find constant BLOG_DB_VERSION in file /libraries/icms/db/legacy/updater/Handler.php line 405
Error(s): Handler does not exist
Module: blog
Name: altcat in file /include/functions.php line 2003
I installed the trunk version of impression. If I use the module as "impression", the installer works fine. But in my case I renamed the module from impression into "blog". Now I get the following error under ImpressCMS 1.3:
This page cannot be displayed due to an internal error.
You can provide the following information to the administrators of this site to help them solve the problem:
Error: Handler does not exist
Module: blog
Name: altcat
Warning: constant(): Couldn't find constant BLOG_DB_VERSION in file /libraries/icms/db/legacy/updater/Handler.php line 405
Error(s): Handler does not exist
Module: blog
Name: altcat in file /include/functions.php line 2003
Leave a comment
on 2011-11-07 03:53 *
By mcdonald3072
The trunk version of Impression uses some IPF classes for creating the database tables.
I think this is temporary as IPF supports tables with a primary key only.
Just updated icms_version.php (changed $modversion['modname'] ) and think you can rename the module install dir now.
I think this is temporary as IPF supports tables with a primary key only.
Just updated icms_version.php (changed $modversion['modname'] ) and think you can rename the module install dir now.
on 2011-11-07 04:46 *
By mcdonald3072
Summary changed from install error (trunk version) to Impression: install error (trunk version)
on 2011-11-07 09:43 *
By David Janssens
As you already noticed, the problem is created because of the rename of the folder. Most IPF modules are still unable to handle that. The newer ones now start to support it though.
IPF modules cannot be renamed at all. You can try what you want, currently it won't work!
We should have a core ticket regarding this issue. However, I can't find it right now. Maybe I'm mistaken.
I thought that we already have a ticket for this in core but it seems like we don't. Just created Ticket 442
Closing this ticket since this is not an issue of impression.
We should have a core ticket regarding this issue. However, I can't find it right now. Maybe I'm mistaken.
I thought that we already have a ticket for this in core but it seems like we don't. Just created Ticket 442
Closing this ticket since this is not an issue of impression.