Viewing 15 replies - 46 through 60 (of 74 total)
  • Thread Starter skippy

    (@skippy)

    The .pot file is not a PowerPoint template, but a source file used to provide localized translations of the plugin. The .mo file is also used for translating the plugin’s display.

    Please double check your error log. Feel free to send the whole thing to me, and I’ll parse it for relevant information. You have my solemn promise that I’m not interested in any kind of malfeasance — I merely want to debug my plugin.

    I’m having some difficulties with this plugin, and several questions I’m afraid :).

    I installed several plugins. A few of them are wp-cron and short-stats. First I tried making a backup including the two tables that short-stats had created in the database. But when I import the file in a dummy database, the two tables of short-stats are not there?

    When disabling the wp-cron plugin and short-stats I get a error message at the bottom of my testpage:

    WordPress database error: [Table 'spoenk.wp_ss_stats' doesn't exist]
    INSERT INTO wp_ss_stats (remote_ip,country,language,domain,referer,resource,user_agent,platform,browser,version,dt) VALUES ('127.0.0.1','Indeterminable','en-us','','','/spoenk/index.php?p=375','Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6','Windows XP','Firefox','1.0.6',1124021878)

    while I did NOT include those tables.

    Also a question about character encoding. My site has always been encoded iso-8859-1. Now when making a dummy database I get the option to what charset/encoding I want to set the database (collate?) and when importing I get some same question about what kind of encoding the sql-file is. I find this all very confusing, and when testing the results I can see that something is wrong there because all my ?? and ?¨ are now question marks.

    One final question and perhaps the most important one:
    When I export my database using the phpmyadmin from my provider I get a sql-file of 797 Kb. When I use gzip and extract this file on my computer I get a sql-file of just 392 Kb. And when looking at the extracted version of the backup that wp-backup has made I get a sql-file of just 294 Kb. In the last two cases a whole lot of posts are missing! Only in the first case I get a good backup, the rest seems to be broken.

    Am I missing something here?

    Correction: Some of my problems must have to do with a wrong setup of that dummy database, because when importing the zipped backupfile directly into my online beta-website everything seems to be OK, but still I don’t understand it. When I open both files (the sql-file of 797 kb and the 294 kb file) and search for a word from one of the posts, I can find that word in the first but not in the smaller file.

    Needless to say I don’t trust the second file at this moment :(.

    Is there a way to set this up to do the backup 2x a week rather than nightly?

    Thread Starter skippy

    (@skippy)

    nmallory: no, it’s daily or not at all. That kind of variable delay is more trouble than it’s worth to include in WP-Cron.

    moxie: I made two backups, one using phpMyAdmin with the default export settings, and one using WP-DB Backup. I selected only one additional non-core table for both of them. The gzipped downloads are 539K (phpMyAdmin) and 561K (WP-DB Backup).

    Unzipped, the files were 1.7M (phpMyAdmin) and 1.7M (WP-DB Backup).

    The contents of the backup files are slightly different. phpMyAdmin uses --- as a comment, whereas WP-DB Backup uses #. WP-DB Backup is also slightly more verbose in its commenting.

    If you’d like to send me your backups, I can try to compare them to see what’s missing, and where. This is the first report that I’ve heard that some data gets lost.

    Skippy,

    On the main backup page, in the Backup Options section, I’m showing the following error:

    WordPress database error: [You have an error in your SQL syntax near '-_wordpress' at line 1]
    SHOW TABLE STATUS FROM korereactor_com_-_wordpress

    Warning: Invalid argument supplied for foreach() in /wp-content/plugins/wp-db-backup.php on line 754

    Any ideas on how to fix? The backup does seem to work fine, would just like to get rid of the error message. Thanks!

    Thread Starter skippy

    (@skippy)

    SHOW TABLE STATUS FROM korereactor_com_-_wordpress — the dash in the table name is technically illegal. I don’t know how you got that dash in there, but my experience has always been that dashes are bad.

    The foreach error most likely is the result of an empty table. Do all your tables have rows in them? (I thought we had fixed this with 1.6, but perhaps not.)

    Thread Starter skippy

    (@skippy)

    Update: dashes are legal in database names as long as you use backticks around the name. Guess what WP-DB Backup forgot to put around database names?

    A new version should be released shortly. This new version should also hopefully help those folks with the “stuck” status bar. Stay tuned.

    Looking forward to it. Thanks!

    Thread Starter skippy

    (@skippy)

    I’ve just released WP DB Backup v1.7! If you had trouble with 1.6, please try this version!

    Works perfectly now! Great work! Thanks!

    I installed WP-Backup a few days ago to work with WP-Cron. the scheduled backup worked fine the first few days but since then I am receiving several emails in one day with a backup database. Often it is the exact same email sent multiple times. Has anyone else had this problem?

    Thread Starter skippy

    (@skippy)

    bianca: I’ve been using WP-Cron to drive WP-DB-Backup since July, and I’ve only received duplicate emails once. It was last night when the time went back an hour for Daylight Savings Time.

    Up until today, I’ve never received duplicate emails. For some reason, last night with the time change, I received 10-15 duplicates.

    No big deal, they were easy enough to delete.

    But I have been extremely happy with the plugin and using it the past few months.

    This is one great plugin.

    Ok, I did receive multiples last night so maybe that was the cause of that. I will continue watching it to see if it happens again.

Viewing 15 replies - 46 through 60 (of 74 total)
  • The topic ‘WordPress Database Backup Plugin’ is closed to new replies.