Custom CSS 1.4.0
Does Custom CSS work with WordPress 6.8.1 and PHP 8.1.12? A smoke test was performed on .
Summary
| 1 | PHP fatal errors |
| 1 | PHP deprecation warnings |
| No JavaScript exceptions | |
| 1 | Page failed to load
|
| No resource errors |
Memory usage: 0 bytes
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
| WordPress version | 6.8.1 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | 8,000+ |
| WordPress.org page | https://wordpress.org/plugins/custom-css-editor/ |
| Badges |
|
Pages 3
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=custom-css-editor%2Ffreshplugin.php&plugin_status=all&paged=1&s&_wpnonce=29b70f2704 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.285 s |
| Memory usage | 4.29 MiB |
| JS errors | None |
| Resource errors | None |
Appearance → Custom Code
| URL | /wp-admin/edit.php?post_type=ff-customcode-item |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.169 s |
| Memory usage | 3.74 MiB |
| JS errors | None |
| Resource errors | None |
WordPress › Error
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 500 |
| Load time | 0.040 s |
| Memory usage | N/A |
| JS errors | None |
| Resource errors | None |
Benchmark
No benchmark data available.
Code Statistics
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| JSON | 44.2% | 24,734 | 0 | 2 | |
| PHP | 40.2% | 22,468 | 8,450 | 304 | |
| JavaScript | 9.4% | 5,252 | 1,544 | 33 | |
| LESS | 5.3% | 2,960 | 242 | 4 | |
| XML | 0.5% | 286 | 0 | 2 | |
| CSS | 0.3% | 166 | 38 | 3 | |
| HTML | 0.1% | 75 | 0 | 2 | |
| Total | 55,941 | 10,274 | 350 | ||
PHP Code Analysis | More results »
| Lines of code | 22,499 |
|---|---|
| Total complexity | 4,861 |
| Median class complexity | 7.0 |
| Median method complexity | 1.0 |
| Most complex class | ffWPLayer |
| Most complex function | ffConditionalLogicEvaluator::_postExtra() |
| Classes | 342 |
|---|---|
| Methods | 3,022 |
| Functions | 3 |
Additions
Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.
Custom Post Types 2
| ID | Name |
|---|---|
| ff-customcode-item | Custom Code |
| ff-options | Options |
PHP Error Log 13 lines
[01-May-2025 16:04:30 UTC] PHP Deprecated: Optional parameter $name declared before required parameter $oneSectionFactory is implicitly treated as a required parameter in /wp-content/plugins/custom-css-editor/fresh-framework/framework/options/dataHolders/class.ffOneStructure.php on line 33
[01-May-2025 16:04:31 UTC] PHP Fatal error: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /wp-content/plugins/custom-css-editor/bootstrap/pluginClass.php:132
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): ffPluginFreshCustomCodeLite->afterSetupTheme()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-settings.php(705): do_action()
#4 /wp-config.php(191): require_once('...')
#5 /wp-load.php(50): require_once('...')
#6 /wp-blog-header.php(13): require_once('...')
#7 /index.php(17): require('...')
#8 {main}
thrown in /wp-content/plugins/custom-css-editor/bootstrap/pluginClass.php on line 132