I am trying to design a Gantry template for Joomla with less. It doesn´t work. No updates.
I´ve tried every solution i've found on the internet now.
My less changes doesn´t work/updates.
This is what I done/do:
In Joomla: Turned off all Joomla cache functions in configuration and plug-ins. I clear cache both in Joomla configuration and Gantry Theme after updates. I also use NoNumber Cache Cleaner plug-in. In my index.php header I have entered: [header("Cache-Control: no-cache, must-revalidate");] and [header("Pragma: no-cache");]
In files: I use Gantrys file naming [menu.less -> menu-custom.less]. The files "Modified" time stamp on the remote server are right/updated. The code are right in those files.
But when I check the code with Firebug the old code is still there.
Browser: Private Browsning in Firefox
Nothing works. Updates doesn´t show up.
What more can I do?
Best regards
/Magnus
Related
Am creating a custom property editor for Umbraco 7. Had a a typo in the controller.js and despite what I do to clear the cache the croken code keeps showing up in the cached Dependency Handler so far I've tried:
Restarting application in IIS
Republishing Umbraco site Change
Clearing Browser cache
Change Debug="false" to Debug="true" in web.config - This worked while in debug but went
back to broken cached version when I put it back to false.
Modify ClientDependancy.config to exclude .js from fileDependencyExtensions - Again this worked while .js was excluded but went back to broken code when I added it back again.
Remove the reference to the controller from the property editors manifest. - This allowed the page to load again, but obviously the the property editor then had no controller.
Have removed datatype and and all references, restarted application and recreated it.
There has to be an easy to do this. Any suggestions?
Umbraco use the ClientDependency framework to cache the backoffice assets. CDF works by caching based on the version number in the ~/Config/ClientDependency.config file. As soon as you change the version number (just make it 1 higher or lower) the caches will be regenerated and the querystrings that automatically get added to all the backoffice assets changes.
This should bust the browser cache as well, but some browsers (Chrome especially) are very aggressive in caching assets, so on rare occasions it will also be necessary to clear your browser cache.
I've successfully installed Fishpig's Magento WordPress Integration extension. I followed the instructions where you install via Magento Connect and had no problems. This is by the way all on the development server which does not have Caching or Compiling enabled.
The Magento cart is installed in the webroot directory and WordPress is in subdirectory "wp" as stated in Fishpig's instructions. The Full Integration blog path is /blog.
PROBLEM:
When I visit the blog's page it is not using the Magento theme. I even set it to use the same layout (same as CMS's homepage) We have a custom Magento theme. Maybe there is something we are doing incorrectly Magento theme wise for Fishpig's extension not to work. Screenshots to come eventually but the host (DataGram) is down due to the flooding Downtown. Should be back hopefully today.
To clarify... WordPress is using its own database. In the Shop's admin panel->WordPress tab I setup Full Integration and set the path to "wp" and the blog path is blog.
So, now if I visit for example... example.com you are in the shop and if you visit example.com/blog you are in the fully integrated blog.
Bottom line is it seems to be configured fine in the admin panel. I am not requesting the blog page from the wp directory (I.E: example.com/wp) but from the fully integrated page (example.com/blog).
Our problem could be similar to what this person is experiencing:
Magento - FishPig Integration - Not getting correct template for /blog
Have a great weekend all!
Best Regards,
George
Huzzah looks like I got things working :-)
The culprit was that this file:
"app/design/frontend/default/eboost/layout/wordpress.xml"
^^ was pointing to the wrong template filename. Corrected and was good to go. Modified line was number 66.
Funny thing is that on the top of that XML file it states:
"
Option 1 - local.xml (recommended)
Create a file named local.xml in your custom theme's layout folder. You can then make changes to the layout there by
using the relevant layout handle. This allows you to leave this file intact and recieve new features
when upgrading the extension.
Option 2 - copy this file
Copy this file and it's contents to a new file in your custom theme's layout folder named wordpress.xml.
Each time you upgrade, you will need to check with your copy of the file and
the copy in app/design/frontend/base/default/layout/wordpress.xml for changes and merge any you find"
Now, as stated in my Original Posting I installed FishPig extension using their instructions: http://fishpig.co.uk/wordpress-integration/docs/installation-and-configuration.html
^^ Therefore I don't know why it is setup using Option 2. That wordpress.xml is in our theme's layout directory.
.
.
.
I feel I should also state the other changes I did even though it doesn't seem like it contributed to making it work. Just doing for completeness:
-- Renamed the subdirectory /wp to /wordpress and changed all references to dev.eboost.com/wp to dev.eboost.com/wordpress within the DataBase using http://interconnectit.com/124/search-and-replace-for-wordpress-databases/
-- Removed .htaccess from /wordpress folder
So bottom line is looks like it is working normally. We are now set for working on redesign for site.
--George
Have a look at this.
http://www.wellicious.com/gbren/wellblog
I also used Fishpig and it is working.
What do you mean by visiting the blog page? Do you request the blog page from the wordpress directory?
If so, it doesn't change its design.
You have to request the blog within your shop.
In Moodle 2.2.3, after 10-12 seconds TinyMCE (TinyMCE HTML editor; editor_tinymce; Standard; 2012030300) buttons will show up (loads very slowly). Where problem lies? Can't figure out how to speed up TinyMCE HTML editor loading time.
I have Moodle 2.2.3+ (Build: 20120519).
I found a solution. The cause, why it was slow, was because it was in estonian. I had to change whole user language into english and it fixed it.
I met the same problem: on my project tinymce loaded about 10 seconds. Solution to speed it up was to disable plugins, which I don't need.
For example:
at default config plugins option was:
plugins: "visualblocks,visualchars,pagebreak,layer,table,save,jbimages,link,emoticons,insertdatetime,preview,media,searchreplace,print,paste,directionality,fullscreen,noneditable,visualchars,nonbreaking,template",
After remove unused plugins it was:
plugins: "jbimages,link",
and editor loading became 2 seconds.
P.S. jbimages is a plugin to upload images.
Look at your caching. The tinyMCE JS files ought to be kept by the browser and recycled, but sometimes this doesn't happen. Use Firebug or Chrome developer tools to see if they are being loaded from cache or from the server. If from the server, you may need to tweak your web server settings so that JS files have an expires header.
RESOLVED
Unbeknownst to me, Cloudflare defaults to caching all css/js files for 4 hours.
Scenario:
I add this to our front page:
<span class="test">hullo!</span>
and this to our css file:
.test { font-size:2.0em; }
I do a web deploy, OR full publish to Azure and the span appears on the front page, but not the styling. The css file for some reason does not get updated. FF, IE, Chrome and Safari all confirm it. However, after a seemingly arbitrary time, the css file get updated.
Even when I remote into the Azure VM and restart the app, the styling is unchanged. The app is running on one instance, one role. No Azure Caching is setup. Adding a querystring param to the css file link does not help. Seems like a caching issue but no clue how to resolve.
Any ideas?
"We are using Cloudflare which has a default set up to cache all CSS and JS files. It purges the cache every 4 hours which resulted in the arbitrary updates. So, even though I was adding a new query string to the end of the css file, Cloudflare still cached the old one"
Just a quick note that you should go to CloudFlare Development Mode when making changes to the static content files on your site. You can get to Development Mode to bypass the cache by going to: settings->Development Mode. You also have the option of purging your cache as an additional option, which we would only recommend if you really want to purge everything.
Looks like it's cached by your browser. Can you please try navigate to your site and press Ctrl+F5.
Maybe you can use Fiddler to see if the CSS had been cached, or not updated, or some error when download.
This issue is resolved.
We are using Cloudflare which has a default set up to cache all CSS and JS files. It purges the cache every 4 hours which resulted in the arbitrary updates. So, even though I was adding a new query string to the end of the css file, Cloudflare still cached the old one.
I have dealt with this and I will tell you that from my experience in Chrome you can set a setting that disables the cache in the developer tools, however, I've noticed that unless you have the dev tools window open when you hit Ctrl+F5 it doesn't reload the cache. In IE there is a global setting in the dev tools that will make it redownload everything every time. In Firefox there is also a setting in the dev tools that will require it to download and not use the cache.
One way that you can test this, and how I test this, is by running Fiddler and watching if it does a full download of all your files or if it's caching.
From what I've experienced is that this is truly a browser caching issue and not anything to do with Azure.
It looks like IE7 doesn't reload the latest version of my stylesheet each time I upload a new version on the server.
This is annoying as I am debugging my .css file to make it work on IE...
Tried to empty the browser cache but still not working.
Thanks for your help.
Ctrl-F5 - forcible way to reload in IE
Include your version number in the file name. myfile_v1234.css
When testing, every time you do an update you can just wite "stylesheet.css?r=98123"
As long as the query string is different, it'll be downloaded again.
If you need, you can use javascript to append Math.random(), to get the random number. Not required on production though, when updates would be stable.
2 Questions:
Does IE eventually load with the newer stylesheet?
How are you saving the changes to the server (SSH, Web Interface, etc.)?
I ask because I ran into an issue with a web-based file management system a while back where one browser would show the CSS just fine, the other wouldn't, and we noticed the issue of which browser played nicely depended on which browser we used to upload the CSS.
The reason turned out to be that IE gave the CSS file a different MIME type than Firefox. If you continue to notice the issue even when you've cleared the cache, check the MIME type of the file using Firefox by going to Tools > Page Info.
Also, if it is simply a caching issue, consider turning caching off in IE. I believe this should be an Advanced Option under Internet Options.
Also, you may want to try creating a special developer environment for IE (if it comes down to it.) Perhaps have another machine with IE7 and no caching and any other features turned off (A kiosk mode, perhaps), and then previewing the page on that machine.
Thanks to you all!
I did manage to solve my problem with the "stupid" Ctrl+F5, and by changing the Internet Parameters of Windows to reload content every new visit.