Welcome to Geeklog, Anonymous Saturday, December 21 2024 @ 09:20 am EST
Geeklog Forums
migrate from 1.3x to 2.0 nl2br errors
Dan
Anonymous
ive put my previous config.php file in the geeklog root and also dumped my database which im trying to import via migration
getting this error. any ideas?
Migrate From Backup
Processing file: /var/www/geeklog/backups/geeklog.dump.20140102.sql
Fatal error: Call to undefined function COM_nl2br() in /var/www/geeklog/public_html/admin/install/bigdump.php on line 271
getting this error. any ideas?
Migrate From Backup
Processing file: /var/www/geeklog/backups/geeklog.dump.20140102.sql
Fatal error: Call to undefined function COM_nl2br() in /var/www/geeklog/public_html/admin/install/bigdump.php on line 271
12
12
Quote
Status: offline
Laugh
Site Admin
Admin
Registered: 09/27/05
Posts: 1470
Location:Canada
Hmmm, A quick look at the code and it looks like that the migrate script redirects to the bigdump.php file to handle the data import. Migrate seems to have lib-common.php loaded (which is were the function COM_nl2br is located) but bigdump does not. Bigdump.php only has the one com_ function call to lib-common.
The configuration doesn't seem to be loaded so we don't know the html path to lib-common.php so you have 2 options.
1) Either load the database yourself with your backup and run the migration that way
or
2) Change line 271 to
echo INST_getAlertMsg($LANG_BIGDUMP[17] . $linenumber . ': ' . trim($dumpline) . '.<br ' . XHTML . '>' . $LANG_BIGDUMP[18] . trim(htmlentities($query)) . '<br ' . XHTML . '>' . $LANG_BIGDUMP[19] . mysql_error());
Either option should get you around the problem (but not really fix it).
One of the Geeklog Core Developers.
The configuration doesn't seem to be loaded so we don't know the html path to lib-common.php so you have 2 options.
1) Either load the database yourself with your backup and run the migration that way
or
2) Change line 271 to
Text Formatted Code
echo INST_getAlertMsg($LANG_BIGDUMP[17] . $linenumber . ': ' . trim($dumpline) . '.<br ' . XHTML . '>' . $LANG_BIGDUMP[18] . trim(htmlentities($query)) . '<br ' . XHTML . '>' . $LANG_BIGDUMP[19] . mysql_error());
Either option should get you around the problem (but not really fix it).
One of the Geeklog Core Developers.
14
18
Quote
Dan
Anonymous
awesome will try it now! thanks
18
17
Quote
All times are EST. The time is now 09:20 am.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content