@wouterj - nice detective work :). Yes, I completely agree - looks like symfony.com is perhaps using an older version of the sphinx extensions which are causing these :method: links to render incorrectly.

@weaverryan strangly enough, the :phpmethod: role that I added some weeks ago works correctly on the site.

ping @fabpot @sensio this issue still exists.

ping again @fabpot I think it is important to fix this, as broken links in the documentation is not something people like...

ping @fabpot, this is an urgent bug as nobody likes not working links

ping @fabpot @sensiolabs @...? Could anybody please take a look at the website issues for a day and fix some of them?

Some important issues:

• :method: role creates wrong url #2156
• Configuration blocks too small #3226
• Documentation search #3023
• [website] Broken images in PDF for CMF documentation #1981
• add more published doc formats (pdf, epub) #1029

ping @javiereguiluz this is a very important bug which is open for too long if you ask me :)

@javiereguiluz can you update the submodule on the doc builder ? The symfony-docs repo points to a fixed version of the extension since months, but it looks like the prod has not updated the submodules since a very long time.

ping @javiereguiluz

problem still existing, the submodule points to the fixed version of sphinx-php. Just need a git submodule foreach git pull where the builder is executed?!

what needs to run on the build server is git submodule update to update the submodules to their revision /cc @javiereguiluz

The whole process of generating the documentation will be revisited if I'm correct, so I hope this can be fixed then too.

@fabpot links to API methods look wrong (they are http://...#lorem_ipsum() instead of http://...#method_lorem_ipsum).

The solution could be easy because according to @stof the server is using an outdated version of fabpot/sphinx-php. This error was fixed a long time ago here: fabpot/sphinx-php@a9d5ec5.

@javiereguiluz to be clear, the submodule in the symfony-docs repo points to a working version since several months. But it looks like git submodule update is not launched in the build server. It should be part of the process.

Given that the extension was updated recently, the issue must be something else.

/cc @javiereguiluz @fabpot

@javiereguiluz could it be possible that env.app.config.api_url_pattern is set in the config used when building the doc for real ? If yes, the fix done 8 months ago in the extensions would not fix the prod, given that it affects the default url pattern only.

@stof api_url_pattern was introduced only a few weeks ago: fabpot/sphinx-php@7818747

This is happening again

It's still happening :)

However, the extension existed before the repository existed and this was one of its earlier extensions. Could it be possible that the documentation build process is using the 2 extensions, both the old one and the repository that already exists? Or maybe this was registered somewhere else and when the extensions were open sourced, they forgot to point to the correct file?

@javiereguiluz to check this easily by checking the extensions setting in the conf.py config. Does it point to the sensio.sphinx.phpcode extension? And does that string point to the correct extension path?

Is there really nothing we can do about this?

@wouterj @weaverryan As a last resort, we could use the method_ prefix in the docs itself, but that's a really ugly workaround.

I will take care of this issue and I'll try to provide a definitive answer soon.

@javiereguiluz Thank you very much.

@javiereguiluz do you have an answer already?

@wouterj unfortunately I don't. I have sent several emails about this to the person responsible of fixing it but I never got a response :(

@fabpot @javiereguiluz I don't want to sound harsh, but it really is a pity to have this issue open for so long. Is there anything that we can do to solve this?

@xabbuh this issue may have been finally solved. A change has been deployed and it will be applied the next time the documentation is rebuilt. Let's wait and see.

Woot, great news :) (and just in time, I was planning to ping you on this at the meeting this afternoon 😉 )

You may not believe me, but I really did not read your comments before the meeting. :)

I'm happy to confirm that this error has been fixed and now all the :method: links work as expected 🎉 🎉 🎉

woohoo 👍