Home › Forums › Basel support forum › Uncaught Error js_composer
Uncaught Error js_composer
- This topic has 20 replies, 2 voices, and was last updated 9 months, 1 week ago by Artem Temos.
-
AuthorPosts
-
January 22, 2024 at 10:26 pm #532422
TuomoParticipantHi there,
I am getting js_composer errors and I guess this is related to WPBakery Page Builder:
2024-01-20T11:49:40+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home2/sukkianet/public_html/wp-content/plugins/js_composer/include/classes/settings/class-vc-license.php’ (include_path=’.:/opt/alt/php80/usr/share/pear:/opt/alt/php80/usr/share/php:/usr/share/pear:/usr/share/php’) in /home2/sukkianet/public_html/wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php:750
Stack trace:
#0 /home2/sukkianet/public_html/wp-content/plugins/js_composer/include/helpers/helpers_factory.php(70): Vc_Manager->license()
#1 /home2/sukkianet/public_html/wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php(249): vc_license()
#2 /home2/sukkianet/public_html/wp-includes/class-wp-hook.php(324): Vc_Manager->init()
#3 /home2/sukkianet/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#4 /home2/sukkianet/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#5 /home2/sukkianet/public_html/wp-settings.php(643): do_action()
#6 /home2/sukkianet/public_html/wp-config.php(231): require_once(‘/home2/sukkiane…’)
#7 /home2/sukkianet/public_html/wp-load.php(50): require_once(‘/home2/sukkiane…’)
#8 /home2/sukkianet/public_html/wp-blog-header.php(13): require_once(‘/home2/sukkiane…’)
#9 /home2/sukkianet/public_html/index.php(17): require(‘/home2/sukkiane…’)
#10 {main}
thrown tässä /home2/sukkianet/public_html/wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php rivillä 750I was having issues with LiteSpeed Cache plugin, because it was growing so fast in cpanel and I asked about this problem from my hosting server. After this I looked the woocommerce logs and I found the upper uncaught error.
I got this answer for the LiteSpeed Cache problem from my hosting provider:
The web hosting seems to accumulate extra content in the path public_html/wp-content/litespeed/js, which seems to be caused by some problem between the site and Litespeed’s Javascript optimization. If necessary, that JS optimization can be disabled if the cause or cause of it is not clear.I guess the problem lies in the js_composer?
Best Regards,
Tuomo NurkkalaJanuary 22, 2024 at 10:31 pm #532424
TuomoParticipantI found this uncaught error as well:
2024-01-17T10:52:49+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home2/sukkianet/public_html/wp-content/themes/basel/inc/options/controls/border/class-border.php’ (include_path=’.:/opt/alt/php80/usr/share/pear:/opt/alt/php80/usr/share/php:/usr/share/pear:/usr/share/php’) in /home2/sukkianet/public_html/wp-content/themes/basel/inc/classes/Theme.php:282
Stack trace:
#0 /home2/sukkianet/public_html/wp-content/themes/basel/inc/classes/Theme.php(217): BASEL_Theme->_include_files()
#1 /home2/sukkianet/public_html/wp-content/themes/basel/functions.php(38): BASEL_Theme->__construct()
#2 /home2/sukkianet/public_html/wp-settings.php(611): include(‘/home2/sukkiane…’)
#3 /home2/sukkianet/public_html/wp-config.php(231): require_once(‘/home2/sukkiane…’)
#4 /home2/sukkianet/public_html/wp-load.php(50): require_once(‘/home2/sukkiane…’)
#5 /home2/sukkianet/public_html/wp-admin/admin-ajax.php(22): require_once(‘/home2/sukkiane…’)
#6 {main}
thrown tässä /home2/sukkianet/public_html/wp-content/themes/basel/inc/classes/Theme.php rivillä 282January 23, 2024 at 10:29 am #532522
Artem TemosKeymasterHello,
Could you please clarify how to reproduce and see these errors on your website?
Kind Regards
January 23, 2024 at 11:18 am #532555
TuomoParticipantHi Artem,
I can’t find any reason for this. I can only see that the cPanel is growing very fast.
Some time ago I had woocommerce and other plugins updates and this started happening. This problem has never happened before.Attachments:
You must be logged in to view attached files.January 23, 2024 at 11:26 am #532564
TuomoParticipantIn the frontend I can find jqmigrate problem, but I don’t know does this have anything to do with this specific problem.
Attachments:
You must be logged in to view attached files.January 23, 2024 at 1:29 pm #532627
Artem TemosKeymasterSorry, but we don’t understand how the second issue is related to PHP error you shown initially. And the last reply is about a totally different problem.
Where we can see the PHP error you sent in the first message?January 23, 2024 at 1:55 pm #532645
TuomoParticipantOkay. I am just sending all the problems from my website that I am finding. 😀
I am not an expert on these things so… :/
The first problem you can find from Sukat.com -> WooCommerce -> Logs -> fatal-errors-2024-01-20.January 23, 2024 at 2:02 pm #532650
TuomoParticipantI opened one of these JS files from Litespeed which are qrowing fast and here are some code of it.
Maybe this can help to find the problem or not:`
January 23, 2024 at 2:05 pm #532655
TuomoParticipantI wasn’t able to send the file in the first message because it was too big.
Now I am sending this JS file in two different files.Attachments:
You must be logged in to view attached files.January 23, 2024 at 2:06 pm #532657January 23, 2024 at 2:07 pm #532659
TuomoParticipantI sent the wrong one in the previous message.
Attachments:
You must be logged in to view attached files.January 23, 2024 at 5:58 pm #532777
Artem TemosKeymasterWe checked your website logs and see that those errors have not appeared for the last three days.
As for the litespeed issue, we don’t quite understand how it is related to the theme. You need to consult with the plugin developers for help on this matter.
January 23, 2024 at 7:31 pm #532818
TuomoParticipantThe reason that this hasn’t occurred might be from the reason that I have cleared the LiteSpeed database and Purged cache many times a day. This is not a good thing to do, but my site then wont break. I could just shut down the LiteSpeed Cache JS settings, but this is not the solution for the problem.
January 24, 2024 at 11:28 am #533020
Artem TemosKeymasterThese errors are not related to Litespeed cache. Next time you see them in your logs, don’t touch anything and let us check the issue for you.
January 24, 2024 at 1:26 pm #533072
TuomoParticipantBut my sites are live, so if I don’t do anything then my site looks like a chinese site, because all of the icons turns to chinese letters or empty boxes. :/
But okay, I will let you know.January 24, 2024 at 2:52 pm #533090
TuomoParticipantBtw I got this message about the increasing Litespeed JS:
It’s normal, but you can limit it: https://docs.litespeedtech.com/lscache/lscwp/ts-optimize/#disk-space-filling-fast
https://wordpress.org/support/topic/litespeed-js/January 25, 2024 at 11:56 am #533416
Artem TemosKeymasterOK, anyway, it is still not related to the PHP error you mentioned initially. It is a different problem which is not related to the theme itself.
January 25, 2024 at 1:08 pm #533462
TuomoParticipantHi Artem,
Okay.
I left Litespeed JS properties on and the cPanel qrew over 100%.
The site started crashing, but I didn’t get any PHP errors anymore.Best Regards,
Tuomo NurkkalaJanuary 26, 2024 at 10:09 am #533770
Artem TemosKeymasterHello,
It looks like a Litespeed issue. You need to consult with its developers for help on this matter.
Kind Regards
January 26, 2024 at 1:44 pm #533845
TuomoParticipantHi Artem,
Okay, now I found the issue.
I had in LiteSpeed Cache -> Page Optimization -> JS Settings -> JS Combine External and Inline -> ON.
This was making maybe 100 files for each site in /wp-content/litespeed/js/ .
Now I turned this JS Combine External and Inline -> OFF and it is making only 6 files for each site.Yes I have told LiteSpeed Cache about this issue.
Best Regards,
Tuomo NurkkalaJanuary 26, 2024 at 3:25 pm #533882
Artem TemosKeymasterGreat, we are glad that you sorted it out! Feel free to contact us if you have any further questions.
-
AuthorPosts
The topic ‘Uncaught Error js_composer’ is closed to new replies.
- You must be logged in to create new topics. Login / Register