Daniel F

This application is broken and inserts duplicate entries into the deletion log which literally is going to break your board. If you're using this app, I would suggest to disable it until the author releases a new version.

@TAMAN My merry Christmas weekend suggestion: Either update/delete such data when a forum is deleted, or wrap your code always into a try-catch block:) To make it easier for the admin to see what's going on, you could e.g. use IPS\Log::log() to log an error inside the catch block, or with 4.4 you could also use our new admin notification system ( ) to send a notification to the admin to notify him about the deleted node which is used in the footer..

It's just the pages app with some custom templates and js code.

Sorry, that's not correct:) We check in accordance with our guidelines, but it is not certifying that the resource is bug free. We ensure that it won't break anything in the core, we ensure that it moves uploaded files if the file storage changes, we ensure that it follows the rules from our guides like that you have to call the parent method and such stuff, but it's not our responsibility to test the functionality of MP submissions. We stopped this a while ago because some people abused the MP and the MP moderators as their free testers.

That's already possible in IPS since IPS 4.3 ?

Please submit a ticket so that we can take a look at this ?

You can still do this! We have only changed the way how and where they're stored and how the changes are presented in the ACP. The presentation on the frontend profile and also all the permissions wasn't changed.

@TheJackal84 Is this a custom flashmessage? If yes, take a look at my 4.3 changes post If not, I’ll be happy to take a look at your issue No‘

NOPE, please not! For the record, I'm not talking about your use case, only about your hook... Just a minor suggestion, please use IPS\Application: convertLegacyParameters() instead of overriding the session class. This would be the "official" place for such redirect, this definitely doesn't belong into the session object! You can see some examples in the core or forums app:)

This was a bug which I have fixed for IPS 4.3 ( The report and reportComment Form page returned response code 404 instead of 403 )

Please change the error in the modules/admin/manage controller. You really shouldn't throw a logged exception If the admin has no permission to award somebody throw new \Exception( \IPS\Member::loggedIn()->language()->get( 'awards_others_err' ) ); Same with throw new \Exception( \IPS\Member::loggedIn()->language()->get( 'awards_obtainable_err' ) )

There's a bug in the winners task Only subclasses of Dispatcher can be instantiated #0 /home/ing/public_html/forum/system/Theme/Theme.php(727): IPS\_Dispatcher::i() #1 /home/ing/public_html/forum/system/Theme/Theme.php(824) : eval()'d code(886): IPS\_Theme->getTemplate('global', 'core') #2 /home/ing/public_html/forum/system/Theme/SandboxedTemplate.php(56): IPS\Theme\class_raffles_front_view->memberRow(Object(IPS\raffles\Raffle), Object(IPS\Member), Array, 1) #3 /home/ing/public_html/forum/system/Theme/Theme.php(824) : eval()'d code(1730): IPS\Theme\_SandboxedTemplate->__call('memberRow', Array) #4 /home/ing/public_html/forum/system/Theme/SandboxedTemplate.php(56): IPS\Theme\class_raffles_front_view->raffleWinners(22, Array) #5 /home/ing/public_html/forum/system/Theme/Theme.php(824) : eval()'d code(720): IPS\Theme\_SandboxedTemplate->__call('raffleWinners', Array) #6 /home/ing/public_html/forum/system/Theme/SandboxedTemplate.php(56): IPS\Theme\class_raffles_front_submit->updateTopicWithWinners(22, 'giveaway', Array) #7 /home/ing/public_html/forum/applications/raffles/tasks/Winners.php(160): IPS\Theme\_SandboxedTemplate->__call('updateTopicWith...', Array) #8 /home/ing/public_html/forum/applications/raffles/tasks/Winners.php(104): IPS\raffles\tasks\_Winners->updateTopicWithResult(Object(IPS\raffles\Raffle), Array) #9 /home/ing/public_html/forum/system/Task/Task.php(248): IPS\raffles\tasks\_Winners->execute() #10 /home/ing/public_html/forum/system/Task/Task.php(217): IPS\_Task->run() #11 /home/ing/public_html/forum/applications/core/interface/task/task.php(60): IPS\_Task->runAndLog() #12 {main}

There's no setting for this. If you have permissions to edit the tile you can longpress on the title till an input box appears.

That's a core feature.

Hi, Your app contains several language strings with the same key, as present in the core application, which is causing translation issues . At a quick glance, I've noticed "delete","quote", "guest". I would suggest to add an app specific prefix to the key or to reuse the existing langstrings from the core to avoid such issues in the future

Thanks for bringing this to our attention. I have fixed this for the next release:)

This seems to be a bug in IPS 4.2. You could disable and re-enable the "Enable template disk caching" setting on the Advanced Settings Page to fix this temporary

That's a bug in your app... The extensions class name is Image and you're using Images in view.php \IPS\Output::i()->metaTags['og:image'] = \IPS\File::get( 'raffles_Images', $this->raffle->thumb )->url;

It's part of the converter app.

I'll still reply, maybe it's useful to other people if the application / plugin was uninstalled, you should drop the column. If the application / plugin data should remain in the database, I would suggest to just set a default value for this field.

We have an internal topic about this, because it's not a simple fix which requires us to change almost the whole FURL system

There's a bug in this application which is causing a 500 error page caused by this line in your hook: public function log( $status, $member ) { if( \IPS\Dispatcher::i()->controllerLocation === 'front' AND \IPS\Settings::i()->llogs_groups == '*' OR $member->inGroup( explode( ',', \IPS\Settings::i()->llogs_groups ) ) ) { you're not checking if $member is null or an instance of \IPS\Member which results in following fatal error: [22-Sep-2016 10:07:32 UTC] PHP Fatal error: Call to a member function inGroup() on array in /home/zzzz/public_html/init.php(442) : eval()'d code on line 37 So each time somebody tries to login with a not existing account, it results in a 500 error page