Jump to content

jlow99

Clients
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

1,654 profile views

jlow99's Achievements

  1. Hello, I'm on a self hosted setup. Upon upgrading to 4.7.2.1, I'm suddenly getting these System Logs messages now: "An app contains a hook that extends \IPS\nexus\Package\Item but it's associated file (xxx/xxx)/applications/nexus/sources/Package/Item/Item.php could not be found." The backtrace for the system log entry is this: #0 /var/www/xxx/xxx/system/Application/Scanner.php(1438): IPS\_Log::log() #1 /var/www/xxx/xxx/system/Application/Scanner.php(1025): IPS\Application\_Scanner::log() #2 /var/www/xxx/xxx/system/Application/Scanner.php(754): IPS\Application\_Scanner::scanHooks() #3 /var/www/xxx/xxx/applications/core/modules/admin/support/support.php(519): IPS\Application\_Scanner::scanCustomizationIssues() #4 /var/www/xxx/xxx/applications/core/modules/admin/support/support.php(228): IPS\core\modules\admin\support\_support->_showBlockHookscanner() #5 /var/www/xxx/xxx/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\support\_support->getBlock() #6 /var/www/xxx/xxx/applications/core/modules/admin/support/support.php(48): IPS\Dispatcher\_Controller->execute() #7 /var/www/xxx/xxx/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\support\_support->execute() #8 /var/www/xxx/xxx/admin/index.php(13): IPS\_Dispatcher->run() #9 {main} This is from the hook scanner apparently. Perhaps this was there all along and is just now reporting it with the upgrade? Note I was on 4.7.1 prior and this message wasn't present. How should I safely fix it?
  2. I think I'm experiencing the same thing Daniel F is reporting, I have experienced this twice when logging into an expired session with the login logs in view. This is what appears in the System Logs of IPS: "The log entry was triggered by a guest" Error: Call to a member function inGroup() on array (0) #0 /var/www/html/hvportal/init.php(442) : eval()'d code(26): IPS\loginlogs_hook_logs->log('GUEST', Array) #1 /var/www/html/hvportal/applications/core/modules/admin/system/login.php(52): IPS\loginlogs_hook_logs->authenticate() #2 /var/www/html/hvportal/system/Dispatcher/Controller.php(96): IPS\core\modules\admin\system\_login->manage() #3 /var/www/html/hvportal/system/Dispatcher/Dispatcher.php(129): IPS\Dispatcher\_Controller->execute() #4 /var/www/html/hvportal/admin/index.php(13): IPS\_Dispatcher->run() #5 {main} Backtrace: #0 /var/www/html/hvportal/init.php(506): IPS\_Log::log('Error: Call to ...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(Error)) #2 {main}
  3. I did the upgrade from IP.Board 3.4.9 to 4.1.14.3 last night and can confirm that the old version v1.1 can be left as is through the upgrade. I did not deactivate or remove v1.1. Once the IPS4 was completed sorting itself out I installed v2 of the Login Logs by simply uploading the tar file and it took care of converting the data and removing it's old v1.1 remnant bits. This was nice to carry over the old data because I have login trends that are good to use for helping folks and backing up known issues or patterns of not remembering some types of credentials. I could have easily just removed the v1.1 instance prior to the upgrade but would have lost that history.
  4. Hello, I'd like to confirm what to do to keep the logs when upgrading from IP.Board 3.4 to IPS 4. I seems like I can just leave the Login Logs 1.1 installed on the IP.Board 3.4 instance and then after upgrading to IPS 4 I just simply install the new version of Login Logs 2.x? Is it really that easy? I don't have to remove the incompatible old version after or anything? My experience in the past with test upgrades from IP.Board 3.4 to 4.x is that it disables the v1.1 Log In Logs application. What I did was just remove the Login Logs application prior to upgrading to IPS V4. I can't recall but maybe there is a preserve data question but I can't remember prior to removing the app. Anyhow, I'm just hoping to see if the old app can be left during the upgrade of IPS to V4 and to simply install this v2.x of the Login Logs.
×
×
  • Create New...