BAUHAUS FILE CLEANUP FOR TAINACAN
Bauhaus File Cleanup for Tainacan compatibility with REEID Translate
Bauhaus File Cleanup for Tainacan compatibility with REEID Translate is being reviewed using official plugin documentation. Automatically removes uploaded files, attachments, and derivative image sizes from disk when a Tainacan item is permanently deleted. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Bauhaus File Cleanup for Tainacan does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Bauhaus File Cleanup for Tainacan is documented in the Media category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Bauhaus File Cleanup for Tainacan compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Automatically removes uploaded files, attachments, and derivative image sizes from disk when a Tainacan item is permanently deleted.
- Handles cleanup of private items stored in prefixed _x_ folders by reconstructing paths from item and collection IDs rather than relying on potentially out-of-sync attachment metadata.
- Removes the entire dedicated upload folder for an item recursively upon permanent deletion to prevent orphaned files.
- Deletes associated attachment posts (documents, child attachments, thumbnails) forcing real file removal bypassing the WordPress media trash.
- Cleans up the tainacan-items/ directory structure when an entire Tainacan collection is permanently deleted.
- Operates via the before_delete_post hook to ensure consistent cleanup across REST API deletions, bulk edits, admin trash emptying, and WP-CLI commands.
- Provides a settings toggle to disable automatic file deletion while keeping the plugin active, allowing users to temporarily preserve files.
TRANSLATION BOUNDARY
Bauhaus File Cleanup for Tainacan capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
Bauhaus File Cleanup for Tainacan and REEID Translate FAQ.
What does Bauhaus File Cleanup for Tainacan do?
Bauhaus File Cleanup for Tainacan has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Bauhaus File Cleanup for Tainacan have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Bauhaus File Cleanup for Tainacan?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Bauhaus File Cleanup for Tainacan in a multilingual WordPress workflow.
REEID documents Bauhaus File Cleanup for Tainacan functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.