Hello is there way how to disable all vqmod cache on opencart 2.0?
I have tried clearing the cache from : vqmod/cache but it doesn't work.
This is why i need to disable all cache .
You can easily disable caching in vQmod though I'm not sure why you'd want to - I've only run into issues with this on sites with 100+ vQmods installed. Generally it's not recommended.
To disable the cache simply edit vqmod/vqmod/php and set:
private static $_devMode = true;
In dev mode, vqmod will parse your xml files in real time which may be a bit slower and it will not use any cache files.
Related
I am working on opencart 3. I have checked that many times working with module I need to clear and refresh modification inside extension in opencart 3. But what modifications exactly do. Can anyone give information for modification tab inside admin in opencart 3. Thanks in advance.
The modification cache is a folder where the PHP code that actually runs is stored. It is created when you install an OCMOD extension. OCMOD extensions are a list of changes that should be made to core files in XML format.
Rather than changing the core files though, OCMOD makes a copy of the files and puts them ni to the modifications folder. This is why you must clear this cache whenever you install or remove an extension.
Is there a way to stop ColdFusion 11 from caching Fusebox circuit.xml.cfm files?
I have to restart the coldfusion service every time I make a change to a fuseaction file and it's getting tiring.
There are 2 settings in play here. One is "trusted cache" - a setting in the CF admin that does not "check" for a modification once a class has been compiled. You can turn trusted cache off and CF will begin to check for modifications.
The second (and more likely) setting is "parsed" setting. This setting actually saves all your include files into a "parsed" directory and compiles the from there. You can try adding the following to your URL:
Fusebox.parseall=true or alternately Fusebox.loadclean=true - one of these might work.
Finally there is a "mode" setting you can modify to "development" from "production" - that will cause the whole thing to be reparsed.
This is from memory - but maybe it will be enough to get you going. good luck! :)
I'm trying to optimize the pagespeed and trying to figure out what does what.
I've managed to merge and compress js/css files, so Google Pagespeed doesn't bother me with that anymore.
Now I still get the message that I can save some bytes by compressing "http://yourpage.com/" which basically means that the html/php-file itself is not compressed (I think)
Any idea how I can solve this?
Some additional information:
Using TYPO3 6.2.21 with the default .htaccess file enabled.
there is an extension for that: https://typo3.org/extensions/repository/view/sourceopt
That works very well. I use it in many projects.
Apparently I had to remove the '<IfModule mod_filter.c>' condition from my .htaccess file, now it's working. I read that my Apache version might be too old.
I'm using django-compressor to compile scss files.
Every time I modify the scss file, django-compressor build a css file in /static/CACHE/css/123456.css.
It's ok for pruduction mode, but when I'm developing on local I have a revision for every change I do.
So, in development mode, how can I force the output to a file with the same name ?
Its not a problem of revison control...
COMPRESS_PRECOMPILERS = (
('text/x-sass', 'sass --compass "{infile}" "{outfile}"'),
('text/x-scss', 'sass --scss --compass "{infile}" "{outfile}"'),
)
The filename for the cached file is actually based on it's contents. From the Django Compressor docs:
Generating the combined file if needed
The file is generated if necessary. All precompilers are called and
all filters are executed, and a hash is determined from the contents.
This in turns helps determine the file name, which is only saved if it
didn’t exist already. Then the HTML output is returned (and also saved
in the cache). And that’s it!
http://django-compressor.readthedocs.org/en/latest/behind-the-scenes/#third-step-generating-the-combined-file-if-needed
I don't think there's any way you can make Django Compressor use a specified name without changing the code.
Your SCSS files still have to go through a matching precompiler before you get a working output for your static assets.
In a properly configured development environment, you'd respect that the static output directory is not located/distributed with your application sources and the resulting CSS files would be tucked away from your sources somewhere on a path that's not under revision control.
EDIT:
Right, so I've missed the correct issue. The only solution is to disable compressor in development, including clearing out the precompiler MIME mappings, and resort to conditionally including client-side compilers in your master template.
This would make it possible to reference the original, unauthored LESS and CoffeeScript sources in development, but sadly I can't find a client-side SASS compiler.
This can be achieved, but it involves a little bit of customisation. I have this exact setup working. I use local dev mode on dev, and in production (heroku) offline compression.
See the bottom of this issue for the code.
https://github.com/django-compressor/django-compressor/issues/226
Today, no matter what I did, my application just would not recognise a change I did to a file I uploaded. I even put a cfabort at the top of the page and it just ignored it.
Now, this is a production server, so there were some things I normally have to do for the fusebox framework to load the new pages. However, all the usual processes failed and I even tried numerous others. Let me list them:
Normal Process:
&fusebox.parseAll=1&fusebox.password=whatever <- Did not work
&fusebox.load=1&fusebox.password=whatever <- Did not work
Other things I tried:
* changed mode from production to development-full-load <- Did not work
* called onApplicationStart to reset app <- Did not work
* changed the application name to reset app <- Did not work
* deleted parsed folder and regenerated <- Did not work
No matter what I did (they may have been more that I just don't recall at present) nothing would refresh the page. The only thing that worked after I was at my wits end, was to stop the Railo server, restart it and then run the thing I tried first again, being:
&fusebox.parseAll=1&fusebox.password=whatever
That worked. So my only assumption can be that somehow, somewhere in the one of the applications, the cached code was being used to regenerate the parsed files instead of the actual updated file.
Has anyone experienced this before and do you have any solutions to avoid this. I can not keep restarting my production application just to update a changed file.
Thanks
From what you've said it sounds like Trusted Caching may be turned on, which is an odd name but basically means "I trust that these files will not change, so don't bother checking" or something like that. The main thing is it doesn't look at your cfm/cfc files for changes, which is faster, but of course very annoying when you make changes.
On Railo, that can happen at the per-mapping level, so first thing is to check all your mappings to see if the "Trusted" option is enabled - unless your site is high enough traffic that it's beneficial, for a Fusebox app it's probably more hassle than it's worth - so for any relevant mappings, unless you specifically need it, go ahead and disable it.
There is also a similar global caching option - in Railo Web Admin, go to Settings>Performance/Caching and most likely you want to have "Inspect Templates" set to "Once". If it is set to "Never", this is same as Trusted cache, which again is faster but not best for a changing site.
However, you may have noticed there is a "Clear template cache" button below - if you prefer to keep it on "Never" you can press this button each time the code changes, and it will rebuild the cache with the latest files.