Jump to content
  • [Beta 11] The admin cannot sign in as member from ACP.


    The admin cannot sign in as member from ACP. The page opens with the admin account and gives this error.

     

    Error: Call to a member function parseLogData() on null in /home/Beats23/beta.my_site/system/Member/History.php:161
    Stack trace:
    #0 /home/Beats23/beta.my_site/system/Helpers/Table/Db.php(473): IPS\Member\History->IPS\Member\{closure}('[]', Array)
    #1 /home/Beats23/beta.my_site/system/Helpers/Table/Table.php(531): IPS\Helpers\Table\Db->getRows(Array)
    #2 /home/Beats23/beta.my_site/static/templates/core_admin_memberprofile.php(2571): IPS\Helpers\Table\Table->__toString()
    #3 /home/Beats23/beta.my_site/system/Theme/SandboxedTemplate.php(68): IPS\Theme\class_core_admin_memberprofile->history(Object(IPS\Member), Object(IPS\Member\History), Array)
    #4 /home/Beats23/beta.my_site/applications/core/modules/admin/members/members.php(1351): IPS\Theme\SandboxedTemplate->__call('history', Array)
    #5 /home/Beats23/beta.my_site/system/Dispatcher/Controller.php(128): IPS\core\modules\admin\members\members->view()
    #6 /home/Beats23/beta.my_site/system/Dispatcher/Dispatcher.php(169): IPS\Dispatcher\Controller->execute()
    #7 /home/Beats23/beta.my_site/admin/index.php(15): IPS\Dispatcher->run()
    #8 {main}
    
    
    #0 /home/Beats23/beta.my_site/system/Member/History.php(165): IPS\Log::log('Error: Call to ...', 'member_history')
    #1 /home/Beats23/beta.my_site/system/Helpers/Table/Db.php(473): IPS\Member\History->IPS\Member\{closure}('[]', Array)
    #2 /home/Beats23/beta.my_site/system/Helpers/Table/Table.php(531): IPS\Helpers\Table\Db->getRows(Array)
    #3 /home/Beats23/beta.my_site/static/templates/core_admin_memberprofile.php(2571): IPS\Helpers\Table\Table->__toString()
    #4 /home/Beats23/beta.my_site/system/Theme/SandboxedTemplate.php(68): IPS\Theme\class_core_admin_memberprofile->history(Object(IPS\Member), Object(IPS\Member\History), Array)
    #5 /home/Beats23/beta.my_site/applications/core/modules/admin/members/members.php(1351): IPS\Theme\SandboxedTemplate->__call('history', Array)
    #6 /home/Beats23/beta.my_site/system/Dispatcher/Controller.php(128): IPS\core\modules\admin\members\members->view()
    #7 /home/Beats23/beta.my_site/system/Dispatcher/Dispatcher.php(169): IPS\Dispatcher\Controller->execute()
    #8 /home/Beats23/beta.my_site/admin/index.php(15): IPS\Dispatcher->run()
    #9 {main}

     


    User Feedback

    Recommended Comments

    Daniel F

    Posted

    Was this an upgrade? Sounds like you have (once again) some left over data in the database from an 3rd party application.

    beats23

    Posted (edited)

    Yes upgrade from v4 to v5 beta 11. I have another install v4 to v5 beta 6 to beta 11 and I don't have this issue on that install. 

    Edited by beats23
    Marc

    Posted

    Do you have different 3rd party applications/plugins on each?

    beats23

    Posted (edited)

    No, both install are from the same copy of the live website. Later I'll try the update on a different v4 copy. I'll manually uninstall all plugins and uninstall all apps except for the few apps that I need that stores records in the database. I have a few apps that I don't want to manually uninstall before the update as I don't want to loose the information those apps collected over the years. If I move those apps to a different folder before the update, do you think that will help with the update not corrupting files due to those apps?

    Edited by beats23
    Daniel F

    Posted

    2 minutes ago, beats23 said:

    If I move those apps to a different folder before the update, do you think that will help with the update not corrupting files due to those apps?

    No because the data are still in the database.

    Try to run this DB query to find all the apps which logged something to the member history, maybe we can narrow it down this way.

    select log_app from core_member_history group by log_app

     

    That said, it's still also something what we could/should fix in our code to prevent 3rd party apps from breaking the core.

    beats23

    Posted

    This was the response.

    Error
    SQL query: Copy Documentation
    
    
    select log_app from core_member_history group by log_app LIMIT 0, 25
    MySQL said: Documentation
    
    #1146 - Table 'site_db.core_member_history' doesn't exist

     

    Daniel F

    Posted

    Do you use a table prefix? If yes add it to the database name.

    Adriano Faria

    Posted

    2 hours ago, Daniel F said:

    it's still also something what we could/should fix in our code to prevent 3rd party apps from breaking the core.

    You will get the same error with a disabled IPS app too. That’s not a 3rd-party issue; it’s just not checking if the app is enabled.

    Daniel F

    Posted

    9 minutes ago, Adriano Faria said:

    You will get the same error with a disabled IPS app too. That’s not a 3rd-party issue; it’s just not checking if the app is enabled.

    thanks, I have passed this information to our internal bug report.

    teraßyte

    Posted

    There's a similar issue with achievement rules, but there should already be a v4 bug report about that. 🙄

    beats23

    Posted

    Is the database table core_member_history installed by the IPS software, or is it a third party table? I deleted all third party apps except for 5 that I need, but this table is still in the data base. Can database data cause issues?

    teraßyte

    Posted

    It's a table installed by the core (System) application. It's a default one.

    Every table uses the prefix of the application it comes from:

    • forums_topics
    • calendar_events
    • etc
    beats23

    Posted

    Just now, teraßyte said:

    It's a table installed by the core (System) application. It's a default one.

    Every table uses the prefix of the application it comes from:

    • forums_topics
    • calendar_events
    • etc

    Ok. thanks. 

    beats23

    Posted

    This issue for cannot sign in as member is no longer there after I delete all apps and plugins before I upgraded to v5.

    One issue is now down and a few more left to go 👍 🙂.


×
×
  • Create New...