Addon problem

[dreamchaser]

Hi guys,

I've done installation of latest Pixelpost ver1.7.1 on 2 different domains. Installation was successful on both of them. However, when I clicked the Addon, it shows "Table 'pixelpost.pixelpost_testping' doesn't exist". My database name is "pixelpost". Please help. Thanks!

[dreamchaser]

Anyone can help?

Thanks...

[Dennis]

Pixelpost doesn't use a table called 'testping', so it has to be an addon that is not default.

Try removing the addon.

[dreamchaser]

i did a fresh installation, uploaded a photo and browse to Addons. It shows "Table 'mmdb.pixelpost_ping' doesn't exist" my database name in "mmdb". there's no addons installed previously. Everything were default now. Only uploaded a picture.

Please help. Thanks.

[arman.noroozian]

I just started using pixelpost 1.7.1 ...
I had the same problem ... when I went to the admin addon tab a similar error was shown (table "blabla"ping does not exist). I know how to fix it, but I don't know if it will have any effect on correct operation. So here is how you can fix it (use it at your own risk.I have been using it and haven't noticed any problem though):

The problem is in the admin_ping.php file
find the part of the file that says:
$query = "CREATE TABLE {$pixelpost_db_prefix}ping (
id INT(11) NOT NULL auto_increment,
pinglist MEDIUMTEXT NOT NULL default '',
PRIMARY KEY (id)
)";
This should be on line 70 (atleast on my machine)
what you have to do is to change it to:
$query = "CREATE TABLE {$pixelpost_db_prefix}ping (
id INT(11) NOT NULL auto_increment,
pinglist MEDIUMTEXT NOT NULL,
PRIMARY KEY (id)
)";

If you know a bit about SQL I will also explain the reason why you should change it.
The problem is that MEDIUMTEXT columns cannot have a default value. By removing the [default ''] part you have fixed the SQL error that resulted from the previous code.

When I changed this, the addon tab started working. And everything else is working too (as far as I know). So give it a try. If it doesn't fix your problem don't forget to revert back to same code as before.

[Dennis]

Ow right, I was thrown off because normally we would end a prefix for a table with an underscore. I guess you're prefix is 'pixelpost_test'. Initially that makes it hard for me to identify the table since I thought the prefix was 'pixelpost_' which will make the table name 'testping'.