What's New
- AuthorPosts
Hi, Team,
Prestashop 1.7.6.8
Tx 4.4.9Since a couple of days, I had frequently an 503 error on the back office and the provider TMD switched the php version from 7.1 to 7.2. It seems I got rid of the errors, but another came up.
I cannot acces anymore at the VC module (nor in the products). I get an error 500 and the debug showed my errors (enclosed).Is VC not compatible with php 7.2 or is it another problem?
Thanks for assistance
Attachments:
Hi Team,
I need to come back to this. I did the VC update, error was gone. However, I noticed only yesterday (3 weeks later) that the insight speed of my site went drastically down.VC Carrousel.css and Prettyphoto.css (?) are taking 4.5-6.3 seconds to load! (See attached image)
I use Cloudflare/Litespeed and was always very happy with the results (81/96) before updating VC.I flushed the cache in Prestashop/Cloudflare/Litespeed/Browser, but the ‘slow ccs loading time’ are remaining. Eventually you can look for kingmobilite.com.
For info, I tried to update to 1.7.7.0 this weekend, but the VC codes are on most pages (?) not working anymore. However, the speed went back to normal (logical as both css did not work anymore). I rolled back for the moment to PS 1.7.6.81) Any ideas or parameters to modify to get the speed back or not working with VS anymore?
2) Other embarrassing problem since 2-3 weeks, I have some kind of footer in my back office, in section product and category. See enclosed a picture with F12. Any solution to get rid of that as it covers a big part of the buttons.
Thanks in advance for assistance
Attachments:
Hi,
1. As VC will load a lot of CSS files and js files, that will block a bit of the request and speed down the site, there aren’t good solutions to resolve it. did you enable the CCC?
2. The problem was due to the VC module, it requires to modify the file to remove VC from the products backoffice, please replace the /modules/jscomposer/jscomposer.php file with my attached one.
Beat regards.Attachments:
- AuthorPosts
You must be logged in to reply to this topic.