Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter titsmaker

    (@titsmaker)

    This triggers following PHP notices:

    PHP Notice:  Trying to get property 'option_name' of non-object in /wp-content/plugins/transients-manager/transients-manager.php on line 106
    PHP Notice:  Trying to get property 'option_name' of non-object in /wp-content/plugins/transients-manager/transients-manager.php on line 414
    PHP Notice:  Trying to get property 'option_name' of non-object in /wp-content/plugins/transients-manager/transients-manager.php on line 376
    PHP Notice:  Trying to get property 'option_name' of non-object in /wp-content/plugins/transients-manager/transients-manager.php on line 377
    PHP Notice:  Trying to get property 'option_value' of non-object in /wp-content/plugins/transients-manager/transients-manager.php on line 114
    Plugin Contributor Pippin Williamson

    (@mordauk)

    I’ve looked into how the Dedicated Transients plugin works and, unfortunately, I’m not seeing a way to resolve this conflict.

    The problem is happening because the Edit screen provided by Transients Manager looks up a transient record by its unique ID number. When Dedicated Transients is used, however, that ID number doesn’t match what Transients Manager expects, so Transients Manager is unable to query the proper database record.

    Thread Starter titsmaker

    (@titsmaker)

    In this case it’s rather strange everything works as it should with Dedicated Transients. Thank you for your investigation and efforts to maintain this plugin!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Conflict with Dedicated Transients plugin’ is closed to new replies.