Global Admin_SmileysController::delete_action ($id, $view): needs some of confirmation
Global arrayToHtmlAttributes (array $attributes): Nested attribute definitions?
Global AssignObject::updateResourcesTemporaryEvents (): the second should be rewritten as prepared statement
Global Container::render (array $variables=[]): Should this really be in the model???
Global Course::userMayAccessRange ($user_id=null): Check permissions
Global Course::userMayAdministerRange ($user_id=null): Check permissions
Global Course::userMayEditRange ($user_id=null): Check permissions
Global DataField::getValue ($field): This should be removed after a while (today is 2015-11-19)
Global DataField::setValue ($field, $value): This should be removed after a while (today is 2015-11-19)
Global Helpbar::ignoreDatabaseContents ($state=true): remove this as soon as the helpbar can handle arbitrary routes
Global HelpTourStep::validate (): Das Model sollte nix Ã¼ber PageLayout wissen, das sollte anders raus transportiert werden
Global HTTP::detect (): Integrate and test HTTP_AUTHORIZATION header authentication
Global Institute::userMayAccessRange ($user_id=null): Check permissions
Global Institute::userMayAdministerRange ($user_id=null): Check permissions
Global Institute::userMayEditRange ($user_id=null): Check permissions
Global Institute_CalendarController::showweek_action ($timestamp=null): der include muss weg
Class Institute_MembersController: test datafields!
Global LegacyWidget::hasLayout (): Really neccessary? Seems to got lost in development
Global OpenGraphURL::fetch (): The combination of FileManager::fetchURLMetadata() and the following request leads to two requests for the open graph data. This should be fixed due to performance reasons.
Global RangeFactory::createRange ($type, $id): Should this be more dynamic in case any more ranges are added?
Global relsize ($size, $verbose=true, $displayed_levels=1, $glue=', ', $truncate=false): Allow "1,3 MB"
Class Response: This is rather ugly and annoying besides the RESTAPI and Trails_Response which basically do the same thing (working with http status, headers and responses). Ideally all of these should use the same PSR-7 compatible HTTP Response object.
Global SelectElement::render (): What should this method actually do?
Namespace studip: using UserManagement class for now, shall be removed afterwards
Global User::patchCourseGroup ($user_id, $course_id): more patchable fields?
Global Widget::hasLayout (): Really neccessary? Seems to got lost in development
Global Widget::listForRange (Range $range, $scope=null): Permission check
Global WidgetAction::hasIcon ($has_icon=null): This seems rather nasty.
Global WidgetInterface::hasLayout (): Really neccessary? Seems to got lost in development
Global ZipArchive::extractToPath ($filename, $path): A little more error checking would be nice.