Limited Support
Our support team is currently on holiday from December 25, 2025 to January 7, 2026, and replies may be delayed during this period.
We appreciate your patience and understanding while our team is away. Thank you for being part of the wpForo community!
Merry Christmas and Happy Holidays! 🎄
Hello. When i admin of forums and trying to select a layout, i get:
GET https://www.website.com/wp-content/plugins/wpforo/wpf-includes/wp-color-picker-script.js?ver=4.9.10 404
thanks
Thank you for letting us know. I'm going to ask the developers to check the issue. I'll update topic asap.
Hi @anonymous20,
There is no in wp-color-picker-script.js file in wpForo core /wpforo/wpf-includes/ directory. This is a result of incorrect customization or some other script call. wpForo doesn't have and doesn't use such JS file. There is no any fix from wpForo side, you should search this issue in other codes/plugins.
That CAN'T be possible unless i hugely missunderstand something here. Because i SEE that script in your CODE that i just got from Wordpress:
in wpf-hooks.php
if( $_GET['page'] == 'wpforo-forums' ){
if( !empty($_GET['action']) ){
//Just for excluding 'nav-menu' js loading//
wp_enqueue_script('postbox');
wp_enqueue_script('link');
wp_enqueue_style( 'wp-color-picker' );
wp_enqueue_script( 'wp-color-picker');
wp_enqueue_script( 'wp-color-picker-script-handle', plugins_url('wp-color-picker-script.js', __FILE__ ), array( 'wp-color-picker' ), false, true );
}
else{
wp_enqueue_script('nav-menu');
}
}
In current development version of wpForo it looks like this:
if ( !empty( $_GET['action'] ) ) {
//Just for excluding 'nav-menu' js loading//
wp_enqueue_script( 'postbox' );
wp_enqueue_script( 'link' );
wp_enqueue_style( 'wp-color-picker' );
wp_enqueue_script( 'wp-color-picker' );
wp_enqueue_script( 'wp-color-picker-script-handle');
} else {
wp_enqueue_script( 'nav-menu' );
}
So I didn't find it. You also can change it in your installed version.
Sorry i don't follow. There is a 404 that i see or not ? In wpForo 1.62 ?
Anyways. Just forget it. Apparently there is some bug or error.
I think It depends on WP version, for some WP version this doesn't exist and you see that error. However this error doesn't exist in our websites. So in any case the core was changed to the code I posted above.
