Hi guys
Im not sure if something wrong with my setup or what the reason is behind this very weird thing..
my installation is calling the file:
/administrator/components/com_virtuemart/assets/css/toolbar_images.css?vmver=fe582afe
in the backend. This file takes FOREVER to load.
The server runs some kind of fcgi php setup with php 7.1
[Tue Oct 09 12:14:52.807906 2018] [fastcgi:error] [pid 20861] [client xxxxxxxxxxxx:64683] FastCGI: comm with server "/etc/cgi-bin/customer_129381_php-settings" aborted: idle timeout (240 sec)
[Tue Oct 09 12:14:52.808019 2018] [fastcgi:error] [pid 20861] [client xxxxxxxxxxxx:64683] FastCGI: incomplete headers (0 bytes) received from server "/etc/cgi-bin/customer_129381_php-settings"
J! 3.8.12
Vm 3.4.2
I also had the problem with 3.4
This is a totally new installation (clean joomla without sample) + virtuemart
i've installed a frontend template from joomshaper (helix3) - but this should be of any concern in this matter
Im not sure what to do but seems weird that a CSS file is taking so long to load?!
So i went into the directory to see if i could find the file and view it... well.. turns out there was NO FILE..
so apparantly it was doing some kind of looping which explains why the fastCGI server was called..
anyway.. hope someone knows how to fix it?
UPDATE:
Well..i made a workaround by not allowing VM to handle 404 errors
Enable VirtueMart 404 error handling - NOT CHECKED
com_virtuemart.3.4.2.9966_package_or_extract
Yes the file is not there.
Also not to be found in the installation pack maybe toolbar_images.css is really the menu_images.css.
Anyway I just downloaded menu_images.css renamed the file and uploaded it again via FTP to the position
/administrator/components/com_virtuemart/assets/css/toolbar_images.css?vmver=3d25c33f
Alternative upload an empty toolbar_images.css file to get rid of the 404
Now my backend loads as normal and I not see any errors.
Correct. The forever loading was caused by a forever loop where VM would handle the 404 and also joomla/template would handle it
This ment that it made the whole server loop out of control, with the vhost using all its ressources.
/administrator/components/com_virtuemart/assets/css/toolbar_images.css was incl. in older VM ~ 3.0.x so upgrades will not see this error
missing in 3.4 but still called
Max notified
It got accidently removed by the installer script.
Hi All, glad i found this thread because this forever loading in admin in a development environment got me crazy...
After re-installing the latest stable i also got these 404 errors:
404 /administrator/components/com_virtuemart/assets/css/toolbar_images.css?vmver=303fbd80
here is the code:
\administrator\components\com_virtuemart_allinone\script.vmallinone.php
Line 103: $file = 'components/com_virtuemart/assets/css/toolbar_images.css';
administrator\components\com_virtuemart\assets\css\admin.styles.css
here is the code:
Line 31: .vm_thumb_image{background:url(../images/admin_ui/toolbar_background.png)
404 /administrator/components/com_virtuemart/assets/images/admin_ui/toolbar_background.png
Kind regards.
Still don't understand why a simple case of a missing file causes such delays?
(it doesn't on my servers .. is just treated as a 404 and moves on)
Is fixed I think in VM3.4.3 and will be definitely in 3.4.4
Quote from: GJC Web Design on November 02, 2018, 09:51:40 AM
Still don't understand why a simple case of a missing file causes such delays?
(it doesn't on my servers .. is just treated as a 404 and moves on)
Is fixed I think in VM3.4.3 and will be definitely in 3.4.4
The problem is that VM has an internal 404 handling, which causes problems with Joomla's own 404 handling. This creates a redirect cycle that never ends. When it doesnt end the webserver waits for php execution timeout before it can serve the next client.
but that can't be right .. the only place if (VmConfig::get('handle_404',1)) is used is in the FE cat and detail views and the FE root virtuemart.php...
not sure if my setup has anything to do with this.
i had a category view as my index.
when reaching for a 404 - a index.php-based file is read, since all joomla files goes through this file.
Im not sure if helix 3 template had anything to do with it, but this caused it to spin out of control.
turning 404 handling off in VM solved it for me.
Quote from: design609 on October 10, 2018, 00:05:45 AM
Anyway I just downloaded menu_images.css renamed the file and uploaded it again via FTP to the position
/administrator/components/com_virtuemart/assets/css/toolbar_images.css?vmver=3d25c33f
Thanks