Installation Issues
Solutions for problems encountered during extension installation, configuration, and setup.
Table of Contents
Extension Installation Problems
Issue: Extension Not Working After TYPO3 13 Upgrade
Symptoms:
- Extension installed but not functional
- Errors about missing classes
Solution: Ensure correct version compatibility:
{
"require": {
"typo3/cms-core": "^13.4",
"netresearch/rte-ckeditor-image": "^13.0"
}
}
composer update
./vendor/bin/typo3 cache:flush
./vendor/bin/typo3 extension:setup
Warning
TYPO3 13 requires extension version 13.0.0 or higher for compatibility.
Dependency Conflicts
Issue: Style Drop-Down Dependency Error
Symptoms:
- Styles disabled when image selected
- Style changes not applied to images
Cause: Missing GeneralHtmlSupport dependency (fixed in v13.0.0+)
Solution: Ensure you're using extension version 13.0.0 or higher:
composer require netresearch/rte-ckeditor-image:^13.0
The plugin now requires:
static get requires() {
return ['StyleUtils', 'GeneralHtmlSupport']; // Both mandatory
}
Important
The GeneralHtmlSupport dependency is critical for style functionality in v13.0.0+
Issue: JavaScript Dependency Errors
Symptoms:
- Browser console shows "GeneralHtmlSupport is not defined"
- Editor doesn't load properly
Cause: Extension version < 13.0.0
Solution: Update to latest version:
composer update netresearch/rte-ckeditor-image
Permission Problems
Issue: File Browser Empty or Not Loading
Symptoms:
- Modal opens but shows no files
- File browser stuck loading
Causes:
- No file mount configured for backend user
- Missing file permissions
- Empty fileadmin directory
Solution:
# User TSConfig
options.defaultUploadFolder = 1:fileadmin/user_upload/
Verify backend user has file mount in: Backend → User Management → Backend Users → File Mounts
Issue: Processed Images Directory Not Writable
Symptoms:
- Original large images displayed
- No
_processed_/directory created - Slow page load due to large images
Solution: Check directory permissions:
# Ensure _processed_/ is writable
chmod 775 fileadmin/_processed_/
# Verify ownership
chown www-data:www-data fileadmin/_processed_/
Static Template Configuration
Issue: Static Template Not Included
Symptoms:
- Images visible in backend RTE
- Images missing in frontend output
Solution:
-
Include Static Template:
- Go to Template → Info/Modify
- Edit whole template record
- Include
CKEditor Image Supportbefore Fluid Styled Content
- Verify TypoScript:
lib.parseFunc_RTE {
tags.img = TEXT
tags.img {
current = 1
preUserFunc = Netresearch\RteCKEditorImage\Controller\ImageRenderingController->renderImageAttributes
}
}
Warning
Always include the static template BEFORE Fluid Styled Content for proper rendering.
Issue: Click-to-Enlarge Not Working with sys_template Records (TYPO3 v13)
New in version 13.0.0
TYPO3 v13 introduced site sets as a modern alternative to sys_template records. When sys_template records exist, site sets are bypassed, which affects extensions that rely on site set dependencies.
Symptoms:
- Images display correctly in frontend
- Click-to-enlarge functionality doesn't work
- Data attributes still visible in HTML output (
data-htmlarea-zoom,data-htmlarea-file-uid) - Image processing hooks not executed
Cause:
In TYPO3 v13, sys_template records prevent site sets from loading. Legacy installations like the Introduction Package use sys_template records instead of modern site sets. When a sys_template exists on a page, TYPO3 ignores site set dependencies, so the extension's TypoScript configuration is never loaded.
Detection:
Check if your site uses sys_template records:
SELECT uid, pid, title, include_static_file
FROM sys_template
WHERE deleted=0 AND hidden=0;
If records exist and data-htmlarea-* attributes appear in frontend HTML, the extension's
TypoScript is not being loaded.
Solution 1: Manual TypoScript Include (Quick Fix)
Add TypoScript directly to the sys_template record:
- Go to WEB > Template module
- Select page with sys_template record
- Click Edit the whole template record
- In Setup field, add:
# Include RTE CKEditor Image TypoScript
<INCLUDE_TYPOSCRIPT: source="FILE:EXT:rte_ckeditor_image/Configuration/TypoScript/ImageRendering/setup.typoscript">
- Save template
- Clear all caches:
./vendor/bin/typo3 cache:flush
Solution 2: Migrate to Site Sets (Recommended for TYPO3 v13)
Modern TYPO3 v13 approach:
- Remove sys_template records from pages (or set them to deleted/hidden)
- Enable site set dependencies in
config/sites/<site>/config.yaml:
base: 'https://example.com/'
rootPageId: 1
dependencies:
- typo3/fluid-styled-content
- netresearch/rte-ckeditor-image
- Clear caches:
./vendor/bin/typo3 cache:flush
- Verify in frontend - data attributes should be removed and click-to-enlarge should work
Why This Happens:
- Zero-config installation (via
ext_localconf.php) loads TypoScript globally - sys_template records override global TypoScript for their page tree
- Bootstrap Package in sys_template clears
lib.parseFunc_RTEhooks - Site sets are ignored when sys_template exists
Verification:
After applying fix, check frontend HTML:
<!-- Before (BROKEN): -->
<img src="..." data-htmlarea-zoom="true" data-htmlarea-file-uid="2" />
<!-- After (WORKING): -->
<a href="/index.php?eID=tx_cms_showpic&file=2&...">
<img src="..." />
</a>
Important
sys_template records are legacy. TYPO3 v13 prefers site sets for better dependency management and proper load order control. Migrating to site sets is recommended for long-term maintainability.
Issue: Insert Image Button Missing with Bootstrap Package or Other Site Sets
New in version 13.1.0
Site Set dependency ordering ensures proper override behavior.
Symptoms:
- Extension is installed and active
- "Insert image" button missing from RTE toolbar
- Page TSConfig shows
RTE.default.preset = bootstrap(or another third-party preset) - Zero-config installation not working
Cause:
Third-party extensions like bootstrap_package use Site Sets to configure the RTE.
In TYPO3 v13, Site Sets have higher priority than extension page.tsconfig files.
The loading order is:
- Extension
Configuration/page.tsconfig(ourRTE.default.preset = rteWithImages) - Site Set configurations (bootstrap's
RTE.default.preset = bootstrapoverrides ours)
When your site uses a Site Set dependency like bootstrap-package/full, it loads
after our extension's page.tsconfig and overrides our RTE preset.
Detection:
Check the active RTE preset in Page TSConfig module:
- Go to Site Management → Page TSconfig
- Search for
RTE.default.preset - If it shows
bootstrapor another preset (notrteWithImages), you have this issue
Or check your site configuration:
dependencies:
- bootstrap-package/full # This overrides our RTE preset!
Solution: Add Site Set Dependency
Add netresearch/rte-ckeditor-image to your site dependencies after the overriding
package so our preset loads last:
base: 'https://example.com/'
rootPageId: 1
dependencies:
- bootstrap-package/full
- netresearch/rte-ckeditor-image # Must come AFTER bootstrap-package
Clear caches after updating:
./vendor/bin/typo3 cache:flush
Why This Works:
Our Site Set (netresearch/rte-ckeditor-image) declares optionalDependencies on
bootstrap-package, so when both are listed, ours loads after bootstrap and overrides
their RTE preset with rteWithImages.
name: netresearch/rte-ckeditor-image
label: 'CKEditor Image Support'
optionalDependencies:
- bootstrap-package/content-elements
- bootstrap-package/full
Affected Packages:
This issue affects any extension that sets RTE.default.preset via Site Sets:
bootstrap_package(setsRTE.default.preset = bootstrap)- Other theme packages with custom RTE configurations
- Any extension using Site Sets for RTE configuration
Verification:
After adding the dependency:
- Clear all caches
- Go to any content element with an RTE field
- Verify the Insert image button appears in the toolbar
- Check Page TSConfig shows
RTE.default.preset = rteWithImages
Tip
The extension's Site Set is designed to work alongside theme packages. Simply adding it to your site dependencies is the correct solution—no manual TSConfig overrides needed.
Image Processing Configuration
Issue: ImageMagick/GraphicsMagick Not Configured
Symptoms:
- Original large images displayed instead of processed versions
- Image processing test fails
Solution: Verify image processing configuration:
// LocalConfiguration.php
$GLOBALS['TYPO3_CONF_VARS']['GFX'] = [
'processor' => 'ImageMagick', // or 'GraphicsMagick'
'processor_path' => '/usr/bin/',
'processor_enabled' => true,
];
Test Image Processing:
./vendor/bin/typo3 backend:test:imageprocessing
Debugging Installation
Check Extension Installation
# Verify extension is installed
composer show netresearch/rte-ckeditor-image
# Check TYPO3 extension list
./vendor/bin/typo3 extension:list
Verify Configuration Loading
# Page TSConfig - Enable RTE debugging
RTE.default.showButtons = *
RTE.default.hideButtons =
Check Browser Console
- Open browser DevTools (F12)
- Go to Console tab
-
Look for errors related to:
- Plugin loading
- Configuration issues
- Missing dependencies
Monitor Network Requests
- Open browser DevTools
- Go to Network tab
-
Check for failed requests to:
/rte/wizard/selectimage- Backend image info API
Database Issues
Issue: Large Database Size
Symptoms:
- Database growing rapidly
- sys_refindex table very large
Cause: Excessive soft reference entries
Solution: Rebuild reference index:
./vendor/bin/typo3 referenceindex:update
Check References:
-- Find images in RTE content
SELECT uid, bodytext
FROM tt_content
WHERE bodytext LIKE '%data-htmlarea-file-uid%';
Getting Help
If issues persist after troubleshooting:
- Check GitHub Issues: https://github.com/netresearch/t3x-rte_ckeditor_image/issues
- Review Changelog: Look for breaking changes in CHANGELOG.md
- TYPO3 Slack: Join #typo3-cms
- Stack Overflow: Tag questions with
typo3andckeditor
Important
When reporting issues, include:
- TYPO3 version
- Extension version
- PHP version
- Browser console errors
- RTE configuration (sanitized)
- Steps to reproduce