Joomla 3.x. Troubleshooter. CSS files are missing in template manager

In some cases, the CSS editor might be missing in the Joomla 3.x admin panel. You may see the list of files, but they cannot be edited.

Checking the Default Theme

To verify this issue, navigate to Extensions → Template Manager → Templates. Choose the default theme (e.g., ThemeXXXX) to check:

Steps to Resolve the Issue

Step 1: Check Database and Table Prefix

Start by identifying the database name and table prefix for the website. From the Joomla Admin Panel, go to System → Global Configuration → Server tab:

Step 2: Access phpMyAdmin

Log into phpMyAdmin and select the appropriate database name for this Joomla website from the left-hand menu:

Step 3: Create a Database Backup

Always create a backup of the database before making any changes. In phpMyAdmin:

• Click the Export tab.
• Click the Go button.
• Save the exported .sql file.

Step 4: Open the SQL Tab

In phpMyAdmin, go to the SQL tab:

Step 5: Execute the Update Query

Insert the following code into the SQL content box:

UPDATE `jos_extensions` 
SET `params` = '{"template_positions_display":"0","upload_limit":"2","image_formats":"gif,bmp,jpg,jpeg,png","source_formats":"txt,less,ini,xml,js,php,css","font_formats":"woff,ttf,otf","compressed_formats":"zip"}' 
WHERE `jos_extensions`.`extension_id` =20;

Ensure that you replace all instances of ‘jos_’ with your specific table prefix identified in Step 1.

Step 6: Apply the Changes

Press the Go button to execute the query:

Step 7: Refresh the Joomla Admin Panel

Log back into the Joomla Admin Panel and navigate to Extensions → Template Manager → Templates → ThemeXXXX. Refresh the page to confirm that the CSS files are now accessible for editing:

Further Notes

By following the steps outlined above, you can resolve the issue of missing CSS editor functionality in Joomla 3.x. Ensure you:

• Verify the correct database and table prefix from the Joomla Admin Panel.
• Back up the database in phpMyAdmin before applying changes.
• Replace the prefix in the SQL query to match your database settings.

If the issue persists, double-check the database settings and permissions or consult our team for additional assistance.