HI David
I installed the pt test site on {link saved}
But when I try to import the feed I am getting the following sql error. But I am using the same PT code from my live site so I don;t why I am getting this error.
I have updated the config and advance config file with test databse and href path accordingly.
Any Idea what am I doing wrong?
Warning: mysql_fetch_array() expects parameter 1 to be resource, boolean given in /home/fstorec1/public_html/zeesht/pt/includes/database.php on line 27
Warning: mysql_num_rows() expects parameter 1 to be resource, boolean given in /home/fstorec1/public_html/zeesht/pt/includes/database.php on line 32
Warning: Cannot modify header information - headers already sent by (output started at /home/fstorec1/public_html/zeesht/pt/includes/database.php:27) in /home/fstorec1/public_html/zeesht/pt/admin/feeds_import.php on line 31
David
I found out the my pt_products table is crashed..is there any quick fix? Or I will have to delete and recreate this table?
#144 - Table './fstorec1_zeesh/pt_products' is marked as crashed and last (automatic?) repair failed
Hi,
Create a repair.php as follows and then upload and browse to from the Price Tapestry installation folder:
<?php
set_time_limit(0);
require("includes/common.php");
$sql = "REPAIR TABLE `".$config_databaseTablePrefix."products`";
database_queryModify($sql,$result);
print "Done.";
?>
Cheers,
David.
--
PriceTapestry.com
Hello Hassan,
If it's a new install of a modified site it may well be missing the require db modifications to support various changes you may have made.
Whenever you mysql errors are displayed, turn on database debug mode to find out more information about the error. To do this, edit config.advanced.php and change line 6 as follows:
$config_databaseDebugMode = TRUE:
Re-import the feed and additional MySQL error information will be displayed. If it's something like "unknown column...." check whether you need to run a dbmod.php script associated with a script modification that you have made - that should be all it is...
Don't forget to turn database debug mode off by changing back to FALSE once resolved. If you're not sure - let me know what is displayed with debug mode enabled and I'll check it out...
Cheers,
David.
--
PriceTapestry.com