• Still lots of coding bugs in 2.0.7. Some of these I reported in 2.0.4, but apparently, you just marked it “resolved” without actually looking at the error log.

    Please look at the line number referenced and fix the bugs.

    PHP message: PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/pie-register/classes/registration_form.php on line 915
    PHP message: PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/pie-register/classes/registration_form.php on line 1296
    PHP message: PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/pie-register/classes/profile_front.php on line 41
    
    PHP message: WordPress database error Invalid default value for 'modified' for query ALTER TABLE pieregister_code CHANGE COLUMN modified modified datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP NOT NULL made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), call_user_func_array, PieRegister->pie_main, PieReg_Base->install_settings, dbDelta" while reading response header from upstream, request: "GET /wp-admin/update-core.php HTTP/1.1", referrer: "wp-admin/update-core.php?action=do-plugin-upgrade"
    2014/04/28 11:24:01 [error] 14705#0: *4644695 FastCGI sent in stderr: "PHP message: WordPress database error Invalid default value for 'modified' for query CREATE TABLE pieregister_code (
                              id mediumint(9) NOT NULL AUTO_INCREMENT,
                              created datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
                              modified datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP NOT NULL,
                              name text NOT NULL,
                              count int(11) NOT NULL,
                              code_usage int(11) NOT NULL,
                              status mediumint(2) NOT NULL,
                              UNIQUE KEY id (id)
                            ) made by activate_plugin, do_action('activate_pie-register/pie-register.php'), call_user_func_array, PieReg_Base->install_settings, dbDelta

    It also appears there is a memory leak in your code, since you shouldn’t be using up 200megs of memory to activate your plugin, right? I do have a lot of users – perhaps you tried to load all of them into memory at the same time?

    PHP message: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 64 bytes) in /wp-includes/meta.php on line 781″, request: “GET /wp-admin/plugins.php?action=activate&plugin=pie-register%2Fpie-register.php HTTP/1.1”, referrer: “http://dev2.primalpalate.com/wp-admin/update.php?action=install-plugin&plugin=pie-register”

    https://wordpress.org/plugins/pie-register/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor genetech

    (@genetech)

    Hello,

    We apologize for the inconvenience. Please allow us some time to review the problem you pointed out.

    We will get back to you on this one Soon.

    Thanks

    Plugin Contributor genetech

    (@genetech)

    Hello,

    We could not re-produce the problems you have mentioned, it seems like its your environment specific issue. Would like us to go over on your server and find the issue?

    Please use our contact form either on Plugin’s Help page or on our Website to send us login details.

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Can't activate 2.0.7’ is closed to new replies.