I'm halfway though this project I've set up in MAMP and all of the sudden it doesn't show any of the changes I make anymore.
The site is showing but it doesn't show the latest changes (even big HTML changes).
It seems like a caching issue. I've deleted the cache in my browser, did hard refreshes, changed the MAMP preferences to an older version of PHP (7.2.21) and commented [OPcache] out in the php.ini file (as suggested on this thread).
This problem seems to occur more often with php5. But since my version of MAMP is only running php 7 I can't find a solution.
Any ideas?
As silly as it sounds, the only one way I found to get away from that issue was by adding any text on the view that I wanted to be refreshed and re-loading the page. MAMP was detecting that update on the view and loaded the correct version instead of the cached version. The OPcache fix did not work for me either.
Related
I recently updated a website, removing an old CMS and converting the website to static html files and changing the hosting server.
Everything is working fine, except that my client tells me that everyone at his office is getting the error : INET_E_DOWNLOAD_FAILURE
They all use Internet Explorer 11.
I cannot reproduce it, I've tried loading on IE on my side but I cannot get the error. After some googling, I've seen that this is probably due to cache/cookies.
I understand that we cannot force browsers to remove cache, but is there a way to fix this without telling the client that he has to delete the temporary files on all their computers?
Hi for the last two days I have been upgrading my magento site gradually from 1.4.0.0 to see if I can get this to the latest stable version 1.8.0.0 and I have come across an error that I can't seem to get past. the error is:
a:4:{i:0;s:56:"Mage registry key "_resource_helper/core" already exists";i:1;s:1414:"
I have been following a process to upgrading I have started from 1.4.0.0 backing up the directory and the database so I do have a working copy, then copied the new files in made sure they work on the frontend and the backend, then i clear the caches within the admin page then create a backup and then do the process again i got up to 5.1.0.0 with out any problems then i try to go to 1.6.2.0 and this error pops up. i have tried clearing the cache and this has not helped.
I just have a few questions that I would like to ask and see if anybody has any answers.
1) Has this happened because I have gone from 1.5.1.0 to 1.6.2.0 straight away instead of going to 1.6.0.0 and then 1.6.2.0.
2) Is there a way to fix this problem or would it be best to restore the site from my backup and then upgrade to 1.6.0.0 or a secondary way
3) Is it something in my database that I can change or something in one of my files that I need to edit.
I fixed my problem within a few steps of it breaking i restored my database and root directory back to the working version of 1.5.1.0 and then I downloaded 1.6.0.0 and then went through the steps I had previously done this then created another error about having problems with renaming a certain file i then went to this directory C:\inetpub\wwwroot\magento\app\code\core\Mage\Reports\sql\reports_setup\ and deleted its contents. then i deleted the cache of the magento and also the browser then my site was working again and i can access the admin panel and everything is working there. I then backed everything up and repeated the process with 1.6.1.0 and this worked as well so now i have currently got a working version of magento 1.6.1.0 thanks for the help and suggestions
I'm a total newbie with Joomla.
I'm the new man in charge of a website and they want a full redesign.
I have already downloaded everything by ftp into my WampServer and exported the BD.
I changed the configuration.php to point my new BD.
I could access the web but I got lots of Deprecated Errors so I turned off the display_errors in the php.ini
Now I can finally see te content of the web but with no templates and no style.
Any idea what's happening?
(I'm not sure what version of Joomla it was working with.)
Well, the first thing I would do is wipe out what you have moved. Then go download and install Akeeba backup. Take a full site backup, then use that to install on localhost. Doing this will make your life a lot easier when it comes to moving the site easily. If the site has issues after moving it this way, then you can pretty much bet it's a server configuration issue and not a Joomla issue.
Next thing you need to do is determine what version of Joomla you have. The 1.5.x series should have the version in the admin in the top right. The 1.6/1.7/2.5 series will have it in the admin in the footer. You can probably check the source on the front end and it will tell you in the meta generator tag. Unless you are on 2.5.2, then you will want to start planning for a migration to the newest version. 1.5 reaches end of life next month and 1.6/1.7 are no longer supported.
This is related to my problem here:
Editing velocity template of Liferay changes not showing or takes a while
I've tried to investigate the caching problem and tried different things. Here's what I found out.
I just found out that my css is also delayed in showing the updates. I tweak my css file adding comment and testing it on my browser. Now just requesting it on the URL it will just give me an older version of the file. now if i put a query asking for version, (eg. mystyle.css?v2) it will pull the latest file and it records it. I can even see different version, eg. (mystyle.css?v1) or (mystyle.css?v2. I've cleaned my cache so it's definitely on the server side (i think).
Is there a way I can clear my cache?
Thank You!
you can activate Liferay's developer setting by including the properties that are in ROOT/WEB-INF/classes/portal-developer.properties.
Explanation: Liferay minifies and caches CSS and Javascript - once this is done it will not examine those for changes. The developer settings will disable that.
However, you don't want this setting active in production as this will mean that you'll have to load dozens of files instead of very few combined+minified, well cached, files.
I assume you are using this for development, not in production.
If you're having these problems in production, you should rather work with a proper theme plugin and redeploy that.
I took a backup of my live Magento site yesterday (zipped up the files and took a DB dump then created the site from those dumps).
Oddly though, on my local machine I get a firebug error that states "$ is not a function" and this error occurs every 500ms or so. So after a minute or 2 I have thousands of errors in the console all the same.
The site is an exact replica of my live site and I don't get the error on that so I'm stumped!
Usually I would think this is a prototype/jquery conflict, but it only seems to happen on my local machine.
Any one have a clue what might be going on?
Thanks
Load a page where you see the error.
View the source of the page.
Find the line that's supposed to load prototype.js by searching for the string prototype.js.
ex. http://magento.example.com/js/prototype/prototype.js
Discover that, for one of myriad reasons, the file isn't loading. (wrong URL, permissions, corrupt file, etc.)
Address problem discovered above.
Ok so this was the problem:
The reason it worked on live and not dev was because I had merge JS enabled on live and not on dev. Live was therefore looking at an old cached bunch of js. Disabling merge js on live highlighted that the problem did in fact occur on the live site.
This knowledge allowed me to debug further and I discovered that the problem lay with my jquery.hove.intent.js file. I updated this to the latest version and it solved everything! :)
Thanks all for your help and input though.