• Resolved jurasjo

    (@jurasjo)


    Hi
    After updating to version 3.16.7 there are some PHP Notices in Course Builder (they happens when adding lesson maybe somewhere else)

    [09-Feb-2018 06:24:53 UTC] PHP Notice:  Undefined index: id in /home/suomikac/public_html/testy/wp-content/plugins/lifterlms/includes/admin/class.llms.admin.builder.php on line 757
    [09-Feb-2018 06:24:53 UTC] PHP Notice:  Undefined index: id in /home/suomikac/public_html/testy/wp-content/plugins/lifterlms/includes/admin/class.llms.admin.builder.php on line 761
    [09-Feb-2018 06:24:53 UTC] PHP Notice:  Undefined index: id in /home/suomikac/public_html/testy/wp-content/plugins/lifterlms/includes/admin/class.llms.admin.builder.php on line 769
    [09-Feb-2018 06:24:53 UTC] PHP Notice:  Undefined index: id in /home/suomikac/public_html/testy/wp-content/plugins/lifterlms/includes/admin/class.llms.admin.builder.php on line 776
Viewing 5 replies - 1 through 5 (of 5 total)
  • Hmmm,

    Working on recreating this but I’m not seeing this happen… in fact, I really can’t even figure out how this could possibly happen.. When a new quiz is created it’s automatically assigned an ID which would mean that the quiz your builder is trying to save doesn’t have an id… I’m trying to figure out how that could happen but I cannot…

    You have support access via lifterlms.com/my-account/my-tickets, right? Can you submit a support ticket about this there so I can take a closer look into this by exchanging some credentials.

    Thanks,

    Thread Starter jurasjo

    (@jurasjo)

    I have no access to tickets now.

    It is about existing course (made couple months ago) with section/lessons and existing/attached quiz.
    When I click “New lesson” button (to add new lesson to some section) it fires those notices.
    Maybe it is about last update.

    • This reply was modified 8 years, 3 months ago by jurasjo.
    Thread Starter jurasjo

    (@jurasjo)

    In version 3.16.8 notices persists.

    @jurasjo,

    This is on my backlog to work on recreating… I’ve been very busy and currently PHP notices (which clog up logs and do need to be fixed but do not actually break functionality) are falling to the bottom of my backlog as non-emergencies.

    I haven’t tried to fix it yet which is more than likely why 3.16.8 didn’t fix it.

    Thanks for your patience,

    @jurasjo,

    I believe I’ve resolved these notices in various updates over the past few weeks. If you’re still seeing them would you please let me know!

    Thanks for your patience

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

The topic ‘PHP Notice: Undefined index:’ is closed to new replies.