Umbraco 15: No more UmbracoAPIController

[sofietoft]

Update code samples using the obsolete UmbracoAPIController

In Umbraco 15, we are removing the UmbracoAPIController.
This means we should remove all references to the UmbracoAPIController in the documentation.

What needs to be done

In most scenarios, the UmbracoAPIController should be directly swappable with a standard Controller.

Testing is required to ensure the code compiles after making the swap.

Use Umbraco 14, where the UmbracoAPIController is already marked as obsolete.
You can also use the Release Candidate for Umbraco 15.

Follow these steps:

1. Locate a code snippet that uses the UmbracoAPIController
2. Put the code into a project
3. Swap UmbracoAPIController with Controller
4. Run the project to test whether the code compiles

Depending on the result of this test, do the following:

• It compiles - woohoo! 🥳
  • Make a PR for the change and keep the task in this Issue checked ✅
• It doesn't compile 😞
  • Add the relevant information as a comment on this issue, and we'll pick it up for further investigation 🔍

Code snippets that need to be tested

I'll add checkmarks to the articles that have been updated 🙌

• Extending > Database
• Image Cropper
• Block Grid Editor -- Very technical!
• Debugging > Logging
• Unit Testing
• Common Pitfalls: Static references to scoped references
• Mapping
• IoC and Dependency injection
• Cache > Tags
• Relation Service
• Querying > ITagQuery
• Querying > Umbraco Context
• Getting started with Entity Framework (EF) Core

### Tasks