• Resolved TigWeb

    (@tigweb)


    Just updated the plugin and I’m getting this fatal error with the first field of my list. The field is for their Last Name.
    Fatal error: Access to undeclared static property: PDb_Shortcode::$readonly_inputs in /home/tigersaa/public_html/wp-content/plugins/participants-database/classes/PDb_Field_Item.class.php on line 221

    Any ideas? The lists were working before the upgrade?

    https://www.ads-software.com/plugins/participants-database/

Viewing 11 replies - 1 through 11 (of 11 total)
  • I’m getting the same problem with the new update too. There are some other things in the error log that might help. The page load terminates when it tries to print out a read only field (a four digit int field) in the display. The first two fields load correctly (they are not read only).

    09-Feb-2014 05:36:14	PHP Notice: date_default_timezone_set() [<a href='function.date-default-timezone-set'>function.date-default-timezone-set</a>]: Timezone ID '' is invalid in /homepages/22/d233747096/htdocs/tridev.dougsdiy/tridev/wp-content/plugins/participants-database/participants-database.php on line 2825
    09-Feb-2014 05:35:42	PHP Fatal error: Access to undeclared static property: PDb_Shortcode::$readonly_inputs in /homepages/22/d233747096/htdocs/tridev.dougsdiy/tridev/wp-content/plugins/participants-database/classes/PDb_Field_Item.class.php on line 221
    09-Feb-2014 05:31:26	PHP Notice: Trying to get property of non-object in /homepages/22/d233747096/htdocs/tridev.dougsdiy/tridev/wp-content/plugins/participants-database/participants-database.php on line 2922

    If I remove the “read only” for the field then the page loads properly. I do still see the following error in the log:
    09-Feb-2014 18:34:53 PHP Notice: date_default_timezone_set() [<a href='function.date-default-timezone-set'>function.date-default-timezone-set</a>]: Timezone ID '' is invalid in /homepages/22/d233747096/htdocs/tridev.dougsdiy/tridev/wp-content/plugins/participants-database/participants-database.php on line 2825

    The above error is printed in the error log 9 times when the page is loaded. This error may be independent of the “read only” problem.

    Plugin Author xnau webdesign

    (@xnau)

    The “read only” problem is a bug I am fixing today.

    The second error is due to the fact that you have not set your timezone in your PHP installation. It is unrelated to the plugin.

    I have a fix for the $readonly_inputs fatal error.
    The following statement needs to be added to the new version of the plugin. It was present in the older version of the plugin.

    /**
       * holds the current value of the "readonly_inputs" shortcode attribute
       */
      public static $readonly_inputs;

    This statement should be placed in the following file:
    classes/PDb_shortcode.class.php

    Plugin Author xnau webdesign

    (@xnau)

    Yes, that will work, but that’s not the fix I am issuing in my patch today.

    Thread Starter TigWeb

    (@tigweb)

    Just applied the patch and I am still getting the error with the read only fields. I did what solarheatengines did and unselected read only and those fields appeared.

    Fatal error: Access to undeclared static property: PDb_Shortcode::$readonly_inputs in /home/tigersaa/public_html/wp-content/plugins/participants-database/classes/PDb_Field_Item.class.php on line 221

    Thanks

    To TigWeb,

    The patch should correct the error you are receiving. Make sure you placed the code in the PDb_shortcode.class.php file. The file on your installation will be found in the following directory:
    wp-content/plugins/participants-database/classes.

    If you can wait I think xnau will have a patch out soon.

    Plugin Author xnau webdesign

    (@xnau)

    Yes, I have a patch coming out in an hour. The 1.5.4.2 patch for some reason did not include the fix…so this time for sure!

    Thread Starter TigWeb

    (@tigweb)

    That got it. Thanks for your hard work in fixing the problem. The one thing I have noticed is that the read only fields look like you can update them but you can’t. They look the same as the text-line which is different then the last version which just showed the figure in the field but that’s fine.

    Plugin Author xnau webdesign

    (@xnau)

    Yes, the read-only text fields look exactly the same. If you want them to look different you can do that with a little CSS.

    Thread Starter TigWeb

    (@tigweb)

    No problems. Thanks again.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Fatal error after upgrade to 1.5.4.1’ is closed to new replies.