| ||||||||||
![]() |
Shopping cart software Solutions for online shops and malls | |||||||||
![]() |
![]() |
|
#181
|
|||||||||
|
|||||||||
![]()
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
#182
|
|||||||
|
|||||||
![]() How do i install this on LOCALHOST without the annoying message.
Do i really have to open ports and firewall etc. Yes i know its been a long time. I am still working with a very old x-cart version. LOL A lot has changed meanwhile i see. |
|||||||
#183
|
|||||||||
|
|||||||||
![]() Another serious bug in 4.4.2, which I assume is also present in all 4.4.x and 4.3.x. Using Flyout menus with cache the url for images for categories will save in the cache image path as regulat http url which will result in security warning under https (if you choose to show the thumbs). If you are using cache for Flyout menus the html code is like this if thumbs are shown
HTML Code:
Turn off the Flyout cache and the image url changes when protocol changes. Now the question here is: Why these images have absolute url in the first place? Is there a reason for the images not to use relative url? How to fix it? There are few places where image url is constructed as Code:
The $current_location has to go. There is no need for it. This is in func.files.php, func.image.php, in a few function. I am not sure why this was done like this, so QT please provide a fix asap, as I am not sure if I take out $current_location it won't break something else. I don't see the reason anything at all to be referenced with absolute url.
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
|
#184
|
|||||||||
|
|||||||||
![]() Another bug in 4.4.2 OPC - see this
https://bugtracker.qtmsoft.com/view.php?id=39242 Man, that was supposed to be bug free version a year ago...
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
#185
|
|||||||
|
|||||||
![]() Quote:
Who are you hosting your website with (www.party-wholesale.com)? Thanks
__________________
x cart 4.4.2 |
|||||||
#186
|
|||||||||
|
|||||||||
![]() Ok this is not exactly a bug but it has to be fix and fast. Why on Earth 4.4.x was designed to load every single css file available no matter if the module is in use or not, for active modules? What is the login behind loading OPC css file(s) on site front page or products list page? What is the login behind loading Upsell products css file(s) on checkout pages? QT - PLEASE, an answer.
service_css.tpl loads on every single page and has the following code in it Code:
Code:
Who was the bright mind behind all this? Did we really needed more bloated css? 4.4x. was suppose to be clean, css driven, up to the standards cart. Do you think Google likes to see 15+ different css files loading without even a single line from them being used? WOW. I have to revise the first line - this is a BUG, a huge one. And by the way almost same applies to the js files loading with every page load. Lots of them and at least half of them are needed on specific pages only. To somehow reduce that load make sure you turn off every module you don't need/use.
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
|
#187
|
|||||||||
|
|||||||||
![]() Steve you need a medal. Please report it in bugracker.
Quote:
__________________
X-Cart Next: Business 5.2 (learning and testing) X-Cart Classic: Gold and Gold Plus 4.7 Lots of Modules and Customizations OS in use: Red Hat Enterprise, Fedora, CentOS, Debian, Ubuntu, Linux Mint, Kali Linux Ideas for Server configuration (basicaly): Nginx/Pound (reverse proxy), Apache/Nginx (webserver), Squid/Varnish (cache server), HHVM or (PHP-FPM + PHP 5.6 + opcache), MariaDB/Percona MySQL Server, Redis (storing sessions) You can catch my ideas here: http://ideas.x-cart.com |
|||||||||
#188
|
|||||||||
|
|||||||||
![]() Reported it already. I can't believe what they have done sometimes
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
#189
|
|||||||||
|
|||||||||
![]() Probably, their intended method is to amalgamate all the css and javascipt with the intent being that on a production site, the css and javascript speed-up tools will be used. The problem is, after all the initial reported bugs associated with the speed-up tools, it is unclear if they are dependable for production yet. For example - the method in drupal has individual css files being loaded for many addons and themes used, so you can end up with many small, focused css files depending on what you have enabled in your configuration. But, when you are ready to go to production, there are effective tools to aggregate and compress the css. QT appears to want to use a similar method for performance enhancement, but they are starting with css from previous versions that is not designed modularly, and the speed up tool appears to not be trusted by many users yet - so the css architecture is actually worse than on previous versions.
---
__________________
X-CART (4.1.9,12/4.2.2-3/4.3.1-2/4.4.1-5)-Gold (CDSEO, Altered-Cart On Sale, BCSE Preorder Backorder, QuickOrder, X-Payments, BCSE DPM Module) |
|||||||||
#190
|
|||||||||
|
|||||||||
![]() Even if speedup tool works ok why load all unused css files and js scripts. Just makes the load bigger for no reason.
__________________
Steve Stoyanov CFLSystems.com Web Development |
|||||||||
|
|||
X-Cart forums © 2001-2020
|