Print

[forkedatfark]

Hi,

After the upgrade, CPG isn't seeing my albums folder, even though config is clearly pointing to it.
In the database, I see duplicate tables, such as the new ones like cpg1410_albums.
The old tables look like this.
e107_CPG_albums

Here is the debug info.
http://www.forkedatfark.org/Tutorials/CPGdebug.txt

[Joachim Müller]

e107 integration goes unsupported, so I can't tell for sure. Your coppermine install appears to be at http://www.forkedatfark.org/e107_plugins/coppermine_menu/
What did you set as "URL of your coppermine gallery folder (no 'index.php' or similar at the end)" in Coppermine's config? What did you set as "The album directory" in Coppermine's config?

[forkedatfark]

e107 integration goes unsupported, so I can't tell for sure. Your coppermine install appears to be at http://www.forkedatfark.org/e107_plugins/coppermine_menu/
What did you set as "URL of your coppermine gallery folder (no 'index.php' or similar at the end)" in Coppermine's config? What did you set as "The album directory" in Coppermine's config?

That is correct.
http://www.forkedatfark.org/e107_plugins/coppermine_menu/
The album directory is set as
albums/

Should I try going into phpMyAdmin and deleting the new CPG tables and trying to upgrade again?

[Joachim Müller]

What did you set as "URL of your coppermine gallery folder (no 'index.php' or similar at the end)" in Coppermine's config?

Please answer my question.

[forkedatfark]

Please answer my question.

Sorry, GauGau.
I meant that http://www.forkedatfark.org/e107_plugins/coppermine_menu/ is the path you were asking about.

Right now, I am trying to load my database backup into a new MySQL 5.0 database.
If that works, I will be able to revert my database to 6 days ago.
That isn't going to upgrade me to the latest coppermine, but I guess I can live with that if it fixes my broken galleries.

[Joachim Müller]

I'm sorry, I have no idea how the e107 integration works, I can't help you very much. For security reasons it's mandatory to upgrade to cpg1.4.10. Going back to cpg1.4.9 is not an option.

[forkedatfark]

I'm sorry, I have no idea how the e107 integration works, I can't help you very much. For security reasons it's mandatory to upgrade to cpg1.4.10. Going back to cpg1.4.9 is not an option.

Thanks.
The bridging wasn't really a problem.
If I get things stable again if the database change, how do I upgrade to cpg1.4.10?
Following the instructions in the bridging manual were farking me up because I wasn't doing either a fresh install or a upgrade from 1.3x.
I would rather not see two sets of tables in my db again, neither of them doing me any good.

[forkedatfark]

Thanks.

Fixed the problem with a DB restore.