[Plugin: podPress]

  • l0c0luke

    (@l0c0luke)


    12 years, 4 months ago

    I have installed podPress but the two stats tables are not getting created.

    I tried deactivating plugin and reactivating. No. I tried turning off statistics, then turning them back on again. No.

    Could you send me the SQL that is required to crate these two tables if you ahve it?

Viewing 5 replies - 1 through 5 (of 5 total)
  • ntm

    (@ntm)

    12 years, 4 months ago

    If you use the 8.8.10.12 then podPress should create the statistic tables if necessary when you save the settings of the general settings page of podPress and the statistic feature is active.
    That this has not worked in your case (an probably in this case) is a clear sign that something is wrong with the procedure or the SQL statements podPress uses to create these tables.

    My guess is that it has something to do with the DB_COLLATE and DB_CHARSET setting. Have you customised these constants (in wp-config.php)?

    The SQL statements are:

    CREATE TABLE wp_podpress_stats (id int(11) unsigned NOT NULL auto_increment, postID int(11) NOT NULL default '0', media varchar(255) NOT NULL default '', method varchar(50) NOT NULL default '', remote_ip varchar(15) NOT NULL default '', country varchar(50) NOT NULL default '', language VARCHAR(5) NOT NULL default '',domain varchar(255) NOT NULL default '', referer varchar(255) NOT NULL default '', resource varchar(255) NOT NULL default '', user_agent varchar(255) NOT NULL default '', platform varchar(50) NOT NULL default '', browser varchar(50) NOT NULL default '', version varchar(15) NOT NULL default '', dt int(10) unsigned NOT NULL default '0', completed TINYINT(1) UNSIGNED DEFAULT '0', UNIQUE KEY id (id))
    CREATE TABLE wp_podpress_statcounts (postID int(11) NOT NULL default '0',media varchar(255) NOT NULL, total int(11) default '1', feed int(11) default '0', web int(11) default '0', play int(11) default '0',PRIMARY KEY (media))

    Depending on the settings podPress attaches to both statements an additional part for the COLLATE and CHARSET.

    if ( TRUE == defined('DB_COLLATE') AND '' !== DB_COLLATE ) {
	$db_charset = ' COLLATE ' . DB_COLLATE;
} elseif ( (FALSE == defined('DB_COLLATE') OR '' == DB_COLLATE) AND TRUE == defined('DB_CHARSET') AND '' !== DB_CHARSET ) {
	$db_charset = ' DEFAULT CHARACTER SET ' . DB_CHARSET;
} else {
	$db_charset = '';
}

    Do you know how-to access the error.log of your blog? It would be very interesting to know whether it contains error messages regarding these queries.

    Thanks,
    Tim

    Thread Starter l0c0luke

    (@l0c0luke)

    12 years, 4 months ago

    Thanks for the reply. Finally reversed my way to the createstatistictables function in the podpress_class.php file and was able to create the tables manually by hand. I left out the $db_charset portion (of course) so I presume this might be the part getting hung up.

    Looking at my DB, it seems to be a hodgepodge of InnoDB and MyISAM tables with a hodgepodge of latin1_swedish_ci and utf8_general_ci. Not much sense to how each table gets what.

    Running pretty much the same queries as you put above, the tables got InnoDB and latin1_swedish_ci.

    The statistics are now working of course with these tables in the DB. Great plugin and thanks a lot.

    Thread Starter l0c0luke

    (@l0c0luke)

    12 years, 4 months ago

    define(‘DB_COLLATE’, ”);

    is what is in my config. If there is an error log floating around, ill show it but I do not want to recreate the situation and set it all up to make an error happen.

    ntm

    (@ntm)

    12 years, 4 months ago

    I’m glad that it works now for you and I’m very interest in any related error message you can find.
    The error.log file should already contain an error message. You don’t have to rebuild the situation again.

    Of which type are the other WP tables of your blog innoDB or MyISAM? and what type have the podPress tables?

    Thanks,
    Tim

    Thread Starter l0c0luke

    (@l0c0luke)

    12 years, 4 months ago

    no error.log in the installation

    Looking at my DB, it seems to be a hodgepodge of InnoDB and MyISAM tables with a hodgepodge of latin1_swedish_ci and utf8_general_ci. Not much sense to how each table gets what.

    Running pretty much the same queries as you put above, the tables got InnoDB and latin1_swedish_ci.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: podPress]’ is closed to new replies.