[Components] [Filesystem] Fix the directory structure across versions

[xabbuh]

Currently, you cannot switch to the master branch of the filesystem documentation. The reason is that the filesystem.rst file was split into several files in the filesystem/ subdirectory.

However, there is an entry in the redirection map which should ensure that old links don't break. Thus doesn't work at all (probably that's good since it would otherwise be triggered on all versions before 2.6 as well).

To solve this issue, we have to re-add the old filesystem.rst file for master again with some basic contents which links to the new filesystem component index. We also have to remove the entry from the redirection map.

[weaverryan]

Your solution sounds perfect :).

[wouterj]

As I said on IRC, we should do something like http://symfony.com/doc/current/cookbook/form/use_virtuals_forms.html

[stof]

@javiereguiluz couldn't it be possible to handle the redirection map on a per-version basis, allowing to have different redirections in the different versions of the doc ?

[javiereguiluz]

Fabien worked a lot recently to improve the documentation generator of symfony.com. Now the following URL works as expected: http://symfony.com/doc/master/components/filesystem/introduction.html

Is this enough to solve the problem or are you thinking about something else? Thanks!

[xabbuh]

Hm, on http://symfony.com/doc/current/components/index.html we now have a reference to http://symfony.com/doc/current/components/filesystem.html which is redirected to http://symfony.com/doc/current/components/filesystem/introduction.html which doesn't work.

[javiereguiluz]

is redirected to http://symfony.com/doc/current/components/filesystem/introduction.html which doesn't work

After the recent doc changes, that URL works for me. If it also works for you, we could close this issue as fixed.

[wouterj]

@javiereguiluz does this mean redirection maps are now different for each version? That would be great news!

(btw, can de cmf have jt's own redirection map too?)

[xabbuh]

I'm closing here since the issue seems to be fixed. Thanks @javiereguiluz!