Page MenuHome

Blender 2.8 manual references 2.79 API docs
Closed, ArchivedPublic

Description

System Information
Operating system: Darwin-18.5.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.8.38

Blender Version
Broken: version: 2.80 (sub 51), branch: master, commit date: 2019-03-28 00:40, hash: rBcd92f8ea4626
Worked: (optional)

Short description of error
Blender 2.8 executable and manual reference the 2.79 documentation

Exact steps for others to reproduce the error

Problem with Blender 2.8 executable:

  1. Start Blender
  2. In the top menu try Help->Python API Reference
  3. Observe that you are taken to the 2.79 API reference

Problem with Blender 2.8 Manual:

  1. Start Blender
  2. In the top menu try Help->Manual
  3. Observe that this properly takes you to the 2.8 Manual
  4. In the Manual navigate to: Advanced->Scripting and Extending Blender->General Information
  5. Observe that this takes you to https://docs.blender.org/manual/en/dev/advanced/scripting/introduction.html#general-information
  6. Now hover the mouse over Blender Python API
  7. Notice that the link is to https://www.blender.org/api/current/
  8. Click on Blender Python API
  9. Observe that you have been taken to the 2.79 manual.

I suppose this isn't urgent for a Beta project but it took some hunting to find the 2.8 API docs.

Thanks,
~chuck

Details

Type
Bug

Event Timeline

Brecht Van Lommel (brecht) renamed this task from Blender 2.8 executable and manual reference the 2.79 documentation to Blender 2.8 manual references 2.79 API docs.Mar 29 2019, 6:20 PM
Brecht Van Lommel (brecht) lowered the priority of this task from Needs Triage by Developer to Confirmed, Low.
Brecht Van Lommel (brecht) edited projects, added Documentation; removed BF Blender.
Brecht Van Lommel (brecht) claimed this task.

I fixed the link inside Blender.

The one in the documentation is harder. We don't have a mechanism in place to distinguish between manuals built for master and official releases, so it always just references the latest official release, which is 2.79.

It could be improved, but would not consider it worth the effort. This will resolve itself once 2.80 is released.