dirkt
Forum Replies Created
-
I don’t know why I was not having greater problems installing things since I had a collation value in my DB_CHARSET. After correcting that and DB_COLLATE with values from my server everything is working as it should.
A weird problem.
Thanks for the help
I reinstalled the plugin while in debug mode and received 56 database errors all related to “Unknown character set: ‘utf8_unicode_ci’.
CREATE TABLE wp_pxmzti_burst_archived_months (IDint(11) NOT NULL AUTO_INCREMENT ,monthint(11) NOT NULL,yearint(11) NOT NULL,batch_idint(11) NOT NULL,row_countint(11) NOT NULL,statusvarchar(250), PRIMARY KEY (ID), UNIQUE KEY month_year (month, year) ) DEFAULT CHARACTER
SET utf8_unicode_ci
Unknown character set: 'utf8_unicode_ci'
dbDelta()There are no Burst tables in the database after running the install.
Also Table ‘wp01.wp_pxmzti_burst_goals’ doesn’t exist. I’m going to reinstall the plugin (again).
Yes, that didn’t do anything. I’m looking around at different tables and configs and I noticed the following burst cron entries have no action:
burst_daily
burst_every_hour
burst_every_ten_minutes
burst_monthly
burst_weeklyYes, there is. Mainly deprecated warnings but there is this:
PHP Fatal error Uncaught RuntimeException: Unable to claim actions. Database error: Table 'wp01.wp_pxmzti_actionscheduler_actions' doesn't exist. in /home/sites/36b/4/458d77c972/public_html/wp-content/plugins/internal-links/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:1019
Stack trace:
#0 /home/sites/36b/4/458d77c972/public_html/wp-content/plugins/internal-links/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php(861): ActionScheduler_DBStore->claim_actions(0, 25, NULL, '', '')
#1 /home/sites/36b/4/458d77c972/public_html/wp-content/plugins/internal-links/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(253): ActionScheduler_DBStore->stake_claim(25, NULL, Array, '')
#2 /home/sites/36b/4/458d77c972/public_html/wp-content/plugins/internal-links/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php(179): ActionScheduler_HybridStore->stake_claim(25)
#3 /home/sites/36b/4/458d77c972/public_html/wp-content/plugins/internal-links/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php(158): ActionScheduler_QueueRunner->do_batch(25, 'WP Cron')
#4 /home/sites/36b/4/458d77c972/public_html/wp-includes/class-wp-hook.php(341): ActionScheduler_QueueRunner->run('WP Cron')
#5 /home/sites/36b/4/458d77c972/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters('', Array)
#6 /home/sites/36b/4/458d77c972/public_html/wp-includes/plugin.php(570): WP_Hook->do_action(Array)
#7 /home/sites/36b/4/458d77c972/public_html/wp-cron.php(191): do_action_ref_array('action_schedule...', Array)
#8 {main}
thrown in /home/sites/36b/4/458d77c972/public_html/wp-content/plugins/internal-links/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 1019- This reply was modified 1 month ago by dirkt.
Just because everything looked like it worked on the archive creation, save for the build interrupt message, I tried installing it… and it worked. I am doing a more thorough test now but a cursory one showed no problems.
I haven’t been able to get it to throw an error in a log. To me the Duplicator log looks complete.
******************************************************************************** PACKAGE-LOG: 2016-02-29 15:56:46 NOTICE: Do NOT post to public sites or forums ******************************************************************************** VERSION: 1.1.4 WORDPRESS: 4.4.2 PHP INFO: 5.6.18 | SAPI: cgi-fcgi SERVER: Apache PHP TIME LIMIT: (0) no time limit imposed PHP MAX MEMORY: 5000M (128M default) MEMORY STACK: 19.5MB ******************************************************************************** DATABASE: ******************************************************************************** BUILD MODE: MYSQLDUMP MYSQLTIMEOUT: 5000 MYSQLDUMP: Is Supported FILTERED: [] RESPONSE: Ran from /usr/bin/mysqldump TABLES: total:17 | filtered:0 | create:17 SQL CREATED: 20160229_1_VCCA_56d46a3429d179762160229155636_database.sql SQL FILE SIZE: 5.94MB (6229444) SQL FILE TIME: 2016-02-29 15:56:53 SQL RUNTIME: 6.51 sec. ******************************************************************************** ARCHIVE (ZIP): ******************************************************************************** ARCHIVE DIR: /home/vcca/public_html ARCHIVE FILE: 20160229_1_VCCA_56d46a3429d179762160229155636_archive.zip FILTERS: *ON* DIRS: /home/vcca/public_html/wp-content/uploads;/home/vcca/public_html/incoming;/home/vcca/public_html/mp3s; EXTS: mp3; ---------------------------------------- COMPRESSING SIZE: 97.48MB STATS: Dirs 869 | Files 8,933 SQL ADDED: 20160229_1_VCCA_56d46a3429d179762160229155636_database.sql COMPRESSION RESULT: '1' COMPRESSED SIZE: 48.23MB ARCHIVE RUNTIME: 323.61 sec. MEMORY STACK: 23MB ******************************************************************************** MAKE INSTALLER: ******************************************************************************** Build Start Build Finished Preping for use Template parsed with new data Complete [/home/vcca/public_html/wp-snapshots/tmp/20160229_1_VCCA_56d46a3429d179762160229155636_installer.php] Added to archive ******************************************************************************** INTEGRITY CHECKS: ******************************************************************************** SQL File: 5.94MB Installer File: 318.95KB Archive File: 48.23MB ******************************************************************************** RECORD ID:[30] TOTAL PROCESS RUNTIME: 383.25 sec. PEAK PHP MEMORY USED: 24.75MB DONE PROCESSING => 20160229_1_VCCA 2016-02-29 16:03:10I’m still looking for where the PHP errors woulds be. The last lines of the log are:
********************************************************************************
INTEGRITY CHECKS:
********************************************************************************
SQL File: 5.94MB
Installer File: 318.95KB
Archive File: 48.22MB********************************************************************************
RECORD ID:[24]
TOTAL PROCESS RUNTIME: 355.74 sec.
PEAK PHP MEMORY USED: 24.75MB
DONE PROCESSING => 20160221_1_VCCA 2016-02-25 02:21:05Thanks for the reply but I had messed up a WordPress setting and had a character set mismatch. I changed wp-config.php and everything worked as advertised. Thanks again.