Go to the documentation of this file.
43 $this->doesExist = isset( $_FILES[$key] );
44 if ( $this->doesExist ) {
45 $this->fileInfo = $_FILES[$key];
68 $name = $this->fileInfo[
'name'];
70 # Safari sends filenames in HTML-encoded Unicode form D...
71 # Horrid and evil! Let's try to make some kind of sense of it.
72 $name = Sanitizer::decodeCharReferences(
$name );
73 $name = MediaWikiServices::getInstance()->getContentLanguage()->normalize(
$name );
74 wfDebug( __METHOD__ .
": {$this->fileInfo['name']} normalized to '$name'\n" );
88 return $this->fileInfo[
'size'];
101 return $this->fileInfo[
'tmp_name'];
112 return 0; # UPLOAD_ERR_OK
115 return $this->fileInfo[
'error'];
125 if ( $this->
getError() == UPLOAD_ERR_INI_SIZE ) {
126 # PHP indicated that upload_max_filesize is exceeded
130 $contentLength = $this->
request->getHeader(
'Content-Length' );
132 ini_get(
'post_max_size' ) ?: ini_get(
'hhvm.server.max_post_size' ),
136 if ( $maxPostSize && $contentLength > $maxPostSize ) {
137 # post_max_size is exceeded
getError()
Return the upload error.
__construct( $request, $key)
Constructor.
div flags Integer display flags(NO_ACTION_LINK, NO_EXTRA_USER_LINKS) 'LogException' returning false will NOT prevent logging a wrapping ErrorException create2 Corresponds to logging log_action database field and which is displayed in the UI similar to $comment or false if none Defaults to false if not set multiOccurrence Can this option be passed multiple times Defaults to false if not set this hook should only be used to add variables that depend on the current page request
isIniSizeOverflow()
Returns whether this upload failed because of overflow of a maximum set in php.ini.
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
exists()
Return whether a file with this name was uploaded.
getName()
Return the original filename of the uploaded file.
as see the revision history and available at free of to any person obtaining a copy of this software and associated documentation to deal in the Software without including without limitation the rights to use
Object to access the $_FILES array.
wfDebug( $text, $dest='all', array $context=[])
Sends a line to the debug log if enabled or, optionally, to a comment in output.
Allows to change the fields on the form that will be generated $name
getTempName()
Return the path to the temporary file.
wfShorthandToInteger( $string='', $default=-1)
Converts shorthand byte notation to integer form.
getSize()
Return the file size of the uploaded file.
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency MediaWikiServices