[7.0] Removal of custom DB object from Table class

[Hackwar]

This is the documentation PR for joomla/joomla-cms#47440

It depends on #589

[qodo-code-review]

Review Summary by Qodo

Add Joomla 6.4 to 7.0 migration documentation

📝 Documentation

Walkthroughs

Description

• Add migration documentation for Joomla 6.4 to 7.0 upgrade
• Document removal of custom DB object from Table class
• Create stubs for new features, deprecations, and compatibility plugin
• Provide migration guidance for third-party developers

Diagram

flowchart LR
  A["Joomla 6.4"] -->|"Migration Guide"| B["Joomla 7.0"]
  B --> C["New Features"]
  B --> D["Deprecations"]
  B --> E["Removed Features"]
  B --> F["Compatibility Plugin"]
  E --> G["Table class DB methods removed"]
  G --> H["Use DatabaseAwareTrait instead"]

Loading

File Changes

1. migrations/64-70/index.md 📝 Documentation +10/-0

Create 6.4 to 7.0 migration index page

• Create index page for 6.4 to 7.0 migration documentation
• Set sidebar position to 985 for proper navigation ordering
• Provide overview of upgrade notes structure

migrations/64-70/index.md

---

2. migrations/64-70/new-features.md 📝 Documentation +13/-0

Add new features documentation stub

• Create stub page for new features in Joomla 7.0
• Add developer note about unreleased version status
• Set sidebar position to 1 for first section

migrations/64-70/new-features.md

---

3. migrations/64-70/new-deprecations.md 📝 Documentation +16/-0

Add new deprecations documentation stub

• Create deprecations page for Joomla 7.0
• Document that no deprecations have been introduced yet
• Add developer note about unreleased version status
• Set sidebar position to 2

migrations/64-70/new-deprecations.md

---

View more (2)

4. migrations/64-70/removed-backward-incompatibility.md 📝 Documentation +14/-0

Document Table class DB object removal

• Document removal of custom DB object methods from Table class
• Explain migration path from getDbo() to getDatabase()
• Detail replacement with DatabaseAwareTrait
• Reference PR #47440 for implementation details

migrations/64-70/removed-backward-incompatibility.md

---

5. migrations/64-70/compat-plugin.md 📝 Documentation +28/-0

Add compatibility plugin documentation

• Document new Compatibility Plugin for Joomla 7.0
• Explain replacement of 6.0 plugin with "Behaviour - Backward Compatibility 7"
• Clarify use of behaviour plugin type for backward compatibility
• Add developer and reader notes about plugin status

migrations/64-70/compat-plugin.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX Issues (0)

1. Self-referential docs link 🐞 Bug ≡ Correctness

Description

The “Detailed documentation” callout in the Joomla 7 compatibility plugin page links back to the
same file, so it provides no navigation and likely masks an intended link target. Readers clicking
it will loop to the current page instead of reaching additional documentation.

Code

migrations/64-70/compat-plugin.md[R24-28]

+### Detailed documentation
+
+:::warning[Reader Note]
+  Please read the [Compatibility Plugin 7.0](../64-70/compat-plugin.md) section
+:::

Evidence

In the new Joomla 7 compatibility plugin page, the Markdown link target is
../64-70/compat-plugin.md, which resolves to migrations/64-70/compat-plugin.md (the current
file), making the link a no-op. In prior migration docs, the same “Detailed documentation” pattern
points to a different page (typically the prior major’s compat-plugin page), suggesting this is
unintended.

migrations/64-70/compat-plugin.md[24-28]
migrations/60-61/compat-plugin.md[31-35]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`migrations/64-70/compat-plugin.md` contains a “Detailed documentation” callout whose link target points back to the same page (`../64-70/compat-plugin.md`). This makes the callout effectively useless and likely indicates a copy/paste or placeholder link.

### Issue Context
Other migration docs use this section to link readers to a *different* page for more information (e.g., the prior major’s compat-plugin documentation).

### Fix Focus Areas
- migrations/64-70/compat-plugin.md[24-28]
- migrations/60-61/compat-plugin.md[31-35]

### What to change
- Replace the self-referential link with the intended target page (e.g., a page that actually contains the detailed documentation), or remove the callout until a real target exists.
- If you repoint to a different version’s page for background, also update the link text so it matches the destination (avoid “7.0” text pointing to non-7.0 docs).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more