Currently, the Transfer subcomponent, which provides facilities around managing file uploads and reporting file upload progress, has no written documentation, and needs some.

There is, however, documentation for the ZF1 equivalent, starting with:

• http://framework.zend.com/manual/1.12/en/zend.file.transfer.introduction.html

I recommend whoever takes this on:

• Converts the docbook sources from ZF1 to markdown.
• Updates the markdown sources to refer to the ZF2 namespaces and class names.
• Reviews the code to determine if the documentation matches actual capabilities, updating as required.

Check headers are correct

TLDR; Headers should use the #, ## etc to format different levels of headers, and not be underlines using ===== or ``-----`, or be psuedo header using bold

Check all headers on the documentation - headers should use the hash style of declaration rather then be underlined with equals or dashes. The more hashes, the more of a subheading. Eg:

• # is equal to <h1>
• ## is equal to <h2>
• ### is equal to <h3>
• #### is equal to <h4>
• ##### is equal to <h5>

Headings should be appropriate for their level in the documentation.

Psuedo headers using bold tags ** should be replaced with appropriate level of heading tag.

Check code blocks are correct

TLDR; Check in all files that codeblocks are correct, in PSR-2 format and have PHP syntax highlighting applied.

Code blocks should be in the following format...

```php
 'ZEND-FRAMEWORK');

// No required options
$rendererOptions = array();
$renderer = Barcode::factory(
    'code39', 'image', $barcodeOptions, $rendererOptions
);

```

Note the three backticks then php in the opening fence, and the closing fence is just three backticks. It's common for the opening backticks to have no code type, or something like source.

Code should also have been automatically formatted into PSR-2 format, but sometimes these slip through the net.

Currently, the documentation page for the ClassFileLocator contains nothing but TODO items.

Check headers are correct

TLDR; Headers should use the #, ## etc to format different levels of headers, and not be underlines using ===== or ``-----`, or be psuedo header using bold

Check all headers on the documentation - headers should use the hash style of declaration rather then be underlined with equals or dashes. The more hashes, the more of a subheading. Eg:

• # is equal to <h1>
• ## is equal to <h2>
• ### is equal to <h3>
• #### is equal to <h4>
• ##### is equal to <h5>

Headings should be appropriate for their level in the documentation.

Psuedo headers using bold tags ** should be replaced with appropriate level of heading tag.

Check the tables in a document

TLDR; All tables should be in the format of GHFM using | and - as horizontal and vertical separators respectively

Check all tables are in the correct format. Please don't use leading and trailing | - more information on github flavoured markdown tables can be found here.

Hello,
Since the merge #13 , the param $files of the method receive($files = null) does not work.

In my example code the file MyFile.txt is not moved.

$adp = new Http();
            $adp->setDestination($mydest);
            $adp->receive("MyFile.txt");

In method getFiles the name MyFile.txt is never found (here) because
since the merge #13 was added "MyFile.txt" file name is rename in "phpackXwt_MyFile.txt".

• Update Travis configuration
• Check Travis results

Related to #39

While creating object of Http()
$receiver = new \Zend\File\Transfer\Adapter\Http();
get exception Zend\ServiceManager\Exception\ServiceNotFoundException:

An alias "fileupload" was requested but no service could be found.

seems issue belongs to package zendframework/zend-validator

FilterPluginManager extends from zend-filter/FilterPluginManager and overrides $aliases which causes broken alias rename -> filterename which doesn't exist

Check docs for other problems

TLDR; Cast your eye over the documetation for any problems not covered in the other issues

Things slip through the net, so check the documentation for other problems that have been missed. Common other problems include

• Bullet lists (should be single * then space at the start of line)
• Inline code - should be marked by three backticks at start and finish
• bookdown.json file is correctly formated and has the right escaping
• Links between documentation using RST have been stripped
• Any other RST has been removed correctly
• Anything and everything not covered

If you end up fixing the same problem over and over, please ping Gary Hockin - we may be able to add bespoke issue for that problem, or fix in automated capacity

Check the document for bad blockquoutes

TLDR; Check blockquotes are formatted correctly using > and check headings in blockquotes are using ###

Blockquotes are donated by a single greater than character and then a space. Make sure all the blockquotes in every doc file are correctly formatted. Headings in blockquotes should use ### and not bold.

Any paragraph spacing in blockquotes should be marked using a single greater than, then a space.

Check the document for bad blockquoutes

TLDR; Check blockquotes are formatted correctly using > and check headings in blockquotes are using ###

Blockquotes are donated by a single greater than character and then a space. Make sure all the blockquotes in every doc file are correctly formatted. Headings in blockquotes should use ### and not bold.

Any paragraph spacing in blockquotes should be marked using a single greater than, then a space.

Check the tables in a document

TLDR; All tables should be in the format of GHFM using | and - as horizontal and vertical separators respectively

Check all tables are in the correct format. Please don't use leading and trailing | - more information on github flavoured markdown tables can be found here.

The codebase I'm working on uses Zend\File\Transfer\Adapter\Http to handle uploaded files. I don't know how this came about but it doesn't seem to be they way of doing things today (edit: this seems to be the way it was done pre 2.1). Since this is currently broken (#19) and the recommend way of uploading files uses Zend\Form (http://framework.zend.com/manual/current/en/modules/zend.form.file-upload.html) I was wondering what Zend\File is used for? I don't see any Zend component linking it as a dependency (composer.json) and there is no documentation (http://framework.zend.com/manual/current/en/modules/zend.file.class-file-locator.html).

Thanks in advance!

I found the following documentation about Zend\File\Transfer:

• http://framework.zend.com/manual/2.0/en/modules/zend.file.transfer.introduction.html
• zendframework/zendframework#2439

Check docs for other problems

TLDR; Cast your eye over the documetation for any problems not covered in the other issues

Things slip through the net, so check the documentation for other problems that have been missed. Common other problems include

• Bullet lists (should be single * then space at the start of line)
• Inline code - should be marked by three backticks at start and finish
• bookdown.json file is correctly formated and has the right escaping
• Links between documentation using RST have been stripped
• Any other RST has been removed correctly
• Anything and everything not covered

If you end up fixing the same problem over and over, please ping Gary Hockin - we may be able to add bespoke issue for that problem, or fix in automated capacity

Check code blocks are correct

TLDR; Check in all files that codeblocks are correct, in PSR-2 format and have PHP syntax highlighting applied.

Code blocks should be in the following format...

```php
 'ZEND-FRAMEWORK');

// No required options
$rendererOptions = array();
$renderer = Barcode::factory(
    'code39', 'image', $barcodeOptions, $rendererOptions
);

```

Note the three backticks then php in the opening fence, and the closing fence is just three backticks. It's common for the opening backticks to have no code type, or something like source.

Code should also have been automatically formatted into PSR-2 format, but sometimes these slip through the net.