I took a look at this yesterday, and was trying to find the right report to merge this into (looks like T64793 is the chosen one), and another report to link that gave the explanation (found it: T72899). Glad @paul szajner (szap) appeared with the explanation and the updated blend!

Thanks for the clarification @paul szajner (szap)!

The main difference between the example and your case is that in the example it take a property of object A to drive object B.
In your case it's a property from object A that drives object A.

I will look into the documentation tomorrow if I get a chance.

In D6612#165063, @Aaron Carlisle (Blendify) wrote:

This can now be committed

This can now be committed

find is a standard bash command.

find is a standard bash command.

Hi! please use code formatting to separate your comments and commands/output. use three backticks ` to start a code block, three to end it.

Marking as documentation TODO.

• Rename cut operator to split

never mind, I overlooked that you have edited the script.

@Tobias Heinke (TobiasH) can you better explain that, you have a double negative and I am not exactly sure what part of this task you are responding to.

@Aaron Carlisle (Blendify) I would say that with rBM6263 we have a good first version of the new fluid manual.

That's all fine with me, the precise naming and syntax I'll leave up to Python and Add-on project maintainers. If we want to rename wiki_url, it can be done in a way that's backwards compatible.

In T74017#876830, @Brecht Van Lommel (brecht) wrote:

The idea with my patch would be to have either a manual_reference or a wiki_url for an add-on info, never both.
[…]
Instead of adding another field, we could keeping using wiki_url

The idea with my patch would be to have either a manual_reference or a wiki_url for an add-on info, never both. When the add-on is loaded, the URL will then be expanded to include the version.

hi, I think this is not a good solution unless it's temporary. Leading up to 2.82 bcon2, I made sure all addons linked to their correct manual pages. Every included addon should have a permanent page on the Manual.
If this only affects i/o addons then we can simply change the bl_info wiki_url to point to the correct manual page leading up to 2.83.
Adding a duplicate field to all addons: wiki_url and the proposed manual_url are the same thing, an internally used name to point addons to their documentation. @Campbell Barton (campbellbarton) what is your opinion here?
@Aaron Carlisle (Blendify)
If this change has broken all 2.82 i/o manual links, it will need to be redirected by the manual until 2.83.
I'm happy to help fix the i/o addons current links in 2.83 master, linking them to the new manual page.

Leaving as a todo to address the URL for 2.83

I have added a redirect so the initial report is fixed. In the future, now that we know can do this, hopefully, create an automated (maybe semi-manual) method to write redirects.

@Aaron Carlisle (Blendify), maybe something like this (untested):

diff --git a/release/scripts/modules/addon_utils.py b/release/scripts/modules/addon_utils.py
index b58c683dc24..aebb465a037 100644
--- a/release/scripts/modules/addon_utils.py
+++ b/release/scripts/modules/addon_utils.py
@@ -506,6 +506,7 @@ def module_bl_info(mod, info_basis=None):
             "location": "",
             "description": "",
             "wiki_url": "",
+            "manual_reference": "",
             "support": 'COMMUNITY',
             "category": "",
             "warning": "",
@@ -527,5 +528,12 @@ def module_bl_info(mod, info_basis=None):
     if not addon_info["name"]:
         addon_info["name"] = mod.__name__

To clarify on Trouble's comment, I meant to automatically adjust the version number from the addon side instead of the server-side.

In T74017#876496, @Aaron Carlisle (Blendify) wrote:

And we should definitely fix the add-ons docs links somehow including dev, it should contain the release number for official releases.

is there a way to add

def manual_version(self, _context):
    if bpy.app.version_cycle in {"rc", "release"}:
        manual_version = "%d.%d" % bpy.app.version[:2]
    else:
        manual_version = "dev"
    return manual_version

to addon_utils.py? so we can

'wiki_url': "https://docs.blender.org/manual/en/' + manual_version + '/addons/import_export/io_scene_gltf2.html",

If not we can manually bump the version with the release but I would rather automate this.

For the moment I am working on a redirect that we can enable for the release

And we should definitely fix the add-ons docs links somehow including dev, it should contain the release number for official releases.

I took a look, and it appears that mod_rewrite stuff should be part of the FileInfo override that we already have in place. So you should be able to patch stuff up in the commits as well.

And we should definitely fix the add-ons docs links somehow including dev, it should contain the release number for official releases.

@Aaron Carlisle (Blendify), I don't agree, this seems like a serious issue.