Tripp★

I had this too, turns out it was @Aiwa's Steam Integration (v3.0.1) which he released on Github. As soon as I removed it; all of a sudden everything went back to normal. Not sure if you have this or not, but if you do - look into it.

Sure; I'll reply to the email tomorrow. Thanks Jim.

Strange; by pressing enter on the URL where I get a permission error; I was able to proceed, and every time it happened, I just proceeded to press enter until it just processed the entire queue. Still need access to find out what caused it in the first place or do you want to call this "Solved"?

I have recently removed a load of inactive clubs on my site; and told it to delete all content. That has resulted in task queue being quite filled up (Especially with a lot of IndexNow requests). So I click on this link 'Alternatively, you can manually run them now and wait until they all complete.' To process them all now and it'll start chugging along. Every now and then however I get 'Sorry, you do not have permission for that!' with the error '1S111/1' And then there is a load of system log entries. I have tried disabling ALL customisations and this event is repeatable. I thought it might have been IndexNow as that seems to be where it kept apparently hanging on, so I also tried to disable IndexNow, but again, the event is repeatable. I've even made sure that there was a text file in my root web folder with the API key for IndexNow in it; and it's still doing it. I'm at an absolute loss here and it's holding the queue up. The error logs say: Type: queue_oore | Message: OutOfRangeException (0) Backtrace: #0 /home/SITE/public_html/system/Content/Item.php(1538): IPS\Patterns\_ActiveRecord::load(150) #1 /home/SITE/public_html/system/Content/Item.php(2796): IPS\Content\_Item->container() #2 /home/SITE/public_html/applications/gallery/sources/Album/Item.php(679): IPS\Content\_Item->delete() #3 /home/SITE/public_html/applications/gallery/sources/Album/Album.php(1058): IPS\gallery\Album\_Item->delete() #4 /home/SITE/public_html/applications/core/extensions/core/Queue/DeleteOrMoveContent.php(94): IPS\gallery\_Album->delete() #5 /home/SITE/public_html/system/Task/Task.php(47): IPS\core\extensions\core\Queue\_DeleteOrMoveContent->run(Array, 0) #6 /home/SITE/public_html/applications/core/modules/admin/system/background.php(87): IPS\_Task::runQueue() #7 /home/SITE/public_html/system/Helpers/MultipleRedirect/MultipleRedirect.php(93): IPS\core\modules\admin\system\_background->IPS\core\modules\admin\system\{closure}(Array) #8 /home/SITE/public_html/applications/core/modules/admin/system/background.php(138): IPS\Helpers\_MultipleRedirect->__construct(Object(IPS\Http\Url\Internal), Object(Closure), Object(Closure)) #9 /home/SITE/public_html/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\system\_background->process() #10 /home/SITE/public_html/applications/core/modules/admin/system/background.php(42): IPS\Dispatcher\_Controller->execute() #11 /home/SITE/public_html/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\system\_background->execute() #12 /home/SITE/public_html/ACP/index.php(13): IPS\_Dispatcher->run() #13 {main} Type: multiredirect | Message: RuntimeException (0) Backtrace: #0 /home/SITE/public_html/applications/core/modules/admin/system/background.php(87): IPS\_Task::runQueue() #1 /home/SITE/public_html/system/Helpers/MultipleRedirect/MultipleRedirect.php(93): IPS\core\modules\admin\system\_background->IPS\core\modules\admin\system\{closure}(Array) #2 /home/SITE/public_html/applications/core/modules/admin/system/background.php(138): IPS\Helpers\_MultipleRedirect->__construct(Object(IPS\Http\Url\Internal), Object(Closure), Object(Closure)) #3 /home/SITE/public_html/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\system\_background->process() #4 /home/SITE/public_html/applications/core/modules/admin/system/background.php(42): IPS\Dispatcher\_Controller->execute() #5 /home/SITE/public_html/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\system\_background->execute() #6 /home/SITE/public_html/ACP/index.php(13): IPS\_Dispatcher->run() #7 {main} There is nothing in the first boxes for either of these errors; only backtraces.

Believe me; I'm painfully aware of this fact.

It's been mentioned several times; with some actually decent suggestions. I share the sentiment expressed by the original poster. While the ignore feature is a step in the right direction, it seems to lack effectiveness, as posts still appear in activity feeds and similar areas. There has been a longstanding feedback about this concern, and I've personally expressed my thoughts on the matter for quite some time as well.

Okay, that's completely fair. Cheers Adriano. 🙂

Bank Interest still doesn't seem to work and it's been a problem now for over two years. Will it ever be addressed?

@Makoto Under the latest version of IPS all deactivation requests from the User's end are failing. The stack trace in the ACP is: OutOfBoundsException: Request (0) #0 /home/SITE/public_html/applications/deactivation/modules/front/request/request.php(106): IPS\Helpers\Form\_Editor->__construct('reason', NULL, false, Array) #1 /home/SITE/public_html/applications/deactivation/modules/front/request/request.php(327): IPS\deactivation\modules\front\request\_request->_confirmationForm(0) #2 /home/SITE/public_html/system/Dispatcher/Controller.php(107): IPS\deactivation\modules\front\request\_request->confirmationForm() #3 /home/SITE/public_html/applications/deactivation/modules/front/request/request.php(201): IPS\Dispatcher\_Controller->execute() #4 /home/SITE/public_html/system/Dispatcher/Dispatcher.php(153): IPS\deactivation\modules\front\request\_request->execute() #5 /home/SITE/public_html/index.php(13): IPS\_Dispatcher->run() #6 {main} #0 /home/SITE/public_html/init.php(1038): IPS\_Log::log('OutOfBoundsExce...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(OutOfBoundsException)) #2 {main}

A massive thank you for this Makoto. Top notch stuff. Can't wait for it to appear on the Marketplace! Much appreciation.

Were these problems ever fixed in the end? The first issue seemed to be fixed when I manually set the column `expire_time_date` from INT to BIGINT or something like that. But that always felt like a hacky work-around and as for the second issue: I've had interest disabled site wide ever since and not sure if it's okay to re-enable it or not.

@Makoto Is there any progress to this update? I ask because I am getting a similar problem now when trying to download PII data from my site, with this application. It also seems to revolve around IP addresses, and again, only seems to affect accounts that used to be deactivated (IE: They have a record in the Deactivation Request's area) Error: Call to a member function getTimestamp() on int (0) #0 /home/SITENAME/public_html/system/Member/Member.php(2371): IPS\deactivation\extensions\core\IpAddresses\_Requests->findByMember(Object(IPS\Member)) #1 /home/SITENAME/public_html/applications/core/extensions/core/MemberExportPersonalInformation/Main.php(69): IPS\_Member->ipAddresses() #2 /home/SITENAME/public_html/system/Member/Member.php(6277): IPS\core\extensions\core\MemberExportPersonalInformation\_Main->getData(Object(IPS\Member)) #3 /home/SITENAME/public_html/applications/core/modules/front/system/settings.php(770): IPS\_Member->getPiiData() #4 /home/SITENAME/public_html/system/Dispatcher/Controller.php(107): IPS\core\modules\front\system\_settings->downloadPiiData() #5 /home/SITENAME/public_html/applications/core/modules/front/system/settings.php(49): IPS\Dispatcher\_Controller->execute() #6 /home/SITENAME/public_html/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\front\system\_settings->execute() #7 /home/SITENAME/public_html/index.php(13): IPS\_Dispatcher->run() #8 {main} As soon as the record is removed from ModCP -> Deactivation Requests, it works absolutely fine.

How do I turn this off? I already have a third party application that deals with account deactivation and deletion - which suits my needs far better than this and apparently the data download feature doesn't work either. (Error: Call to a member function getTimestamp() on int (0)) Or something of the like.

I appreciate the suggestion, but the last time I rebuilt the achievements it took days and drove the CPU at maximum until it finished. There has been more content since then, won't it just take days-to-a-week every time I rebuild them? Or does it rebuild everything from the last time it was rebuilt?

Well that's depressing. It's unfortunate to see such longstanding issues persist. I understand that addressing them might not be a priority in the current 4.X version, however, it's disheartening to learn that this matter has been lingering for quite some time without a resolution. IPS Staff: It would be reassuring to know if there are any plans or considerations for addressing these concerns in future updates. Kind regards.