Joomla Templates Club 406,261 posts

[ether1 Friend ether1Join date: February 2016Posts: 20Downloads:3Uploads:2 Thanks: 1]

#968529

Hi guys,

so we purchased the JA SUGITE template some time ago and paid for a quickstart installation service, the site has been working fine however we have noticed recently that if we migrate/upgrade/backup the deployment we have a problem.

Each time the deployment goes through one of the above processes it actually re-generates new css files. This is only the 3 main css files associated with the template, the original files (which we have re-styled) are still fine. However it appears the template re-creates the original css files under new names and then re-references them to the template thus overriding the already existing ones.

This is a silly problem unless it exists purposely to help create more work for the JA team. Now you may be thinking ahh it’s only 3 CSS files, well that may be true but if you think about how many times you upgrade joomla, backup your website or perhaps you use the same template across multiple sites then it’s going to drastically increase your workload time.

Now if you don’t modify the stylings it won’t matter because the original files are re-created, but if you do modify the css in any way you should experience the same problem that we are having.

Please can someone clarify if this is the case for ALL JOOMLART Templates or if this is a bug…. we have A LOT of websites and we cannot be using templates that cause these kind of problems. If it’s a bug great, can you fix it. If not we may have to look at alternative options.

Please advise.

[timtecsa Friend timtecsaJoin date: October 2009Posts: 1382Downloads:86Uploads:327 Thanks: 197 Thanked: 132 times in 34 posts]

#968552

Why is this posted under Teline V ?
Joomla updates should not overwrite JA template CSS files.
Joomlart template updates will overwrite template CSS files.
Best to do CSS mods via a ‘custom.css’ file which does not get overwritten by any update, hopefully 🙂

[Saguaros Moderator SaguarosJoin date: September 2014Posts: 31405Downloads:237Uploads:471 Thanks: 845 Thanked: 5346 times in 4964 posts]

#968628

@ether1

We’re aware of that case when updating our templates so we provide some ways to avoid the lost of custom work on your site:

• Using the ‘custom.css’ file: if this file doesn’t exist, just create it in directory: ROOT/templates/ja_template/css/ and put your custom css into this file

• If you want to override other parts also (layout/less/…), we also provide local folder in template folder, the documentation is already available here: http://www.t3-framework.org/documentation/extend-com-content#isolate-template

We always highly recommend to override in these ways.

[ether1 Friend ether1Join date: February 2016Posts: 20Downloads:3Uploads:2 Thanks: 1]

#968664

Hi all, this was raised twice as we had originally posted to the forum’s however after speaking to JoomlArt support we were asked to post here.

We do have a custom css file, however you are completely misunderstanding the problem. We are not saying that our css files are being overridden in the sense of the CSS file content. We are saying that if we took a copy/backup of the website OR upgraded it, that is that the template is creating BRAND NEW css files dynamically with completely different file names and the template references are also being overridden to point to these new CSS files.

Our original files still exist, the template just doesn’t point to them anymore so we have to manually resolve the issue. We are trying to identify whether this is a common JoomlArt design flaw or if this is something specific to the JA Sugite template/quickstart deployment.

Just to reiterate, whether we backup the website to take a copy OR upgrade in BOTH instances this problem occurs.

Granted when you update the template with a Joomla package it’s obvious that it will override with it’s updated default files, that’s just common sense. However it shouldn’t generating new css files and file names. Also if you were upgrading the template, best practice would assume you would keep the file names the same anyway + you would not expect this problem to occur each time you took a backup of your deployment as that should just be a straight copy. So I would think this is a design flaw/bug.

The additional files seem to be being created within this directory, and in JA Sugite’s case it appears to be 3 CSS files that get generated:
/public_html/t3-assets/css

Please advise

[ether1 Friend ether1Join date: February 2016Posts: 20Downloads:3Uploads:2 Thanks: 1]

#968673

This reply has been marked as private.

[Saguaros Moderator SaguarosJoin date: September 2014Posts: 31405Downloads:237Uploads:471 Thanks: 845 Thanked: 5346 times in 4964 posts]

#969027

The files in ‘t3-assets’ will be created when Development Mode or Optimize CSS option in template manager is turn ON.

It should not related to the update of template. I just tried to migrate template from 1.1.5 to 1.1.6 version but no new file updated in ‘t3-assets’ folder.

This folder holds compressed css files only for site performance purpose.

Again, files in ‘t3-assets’ folder will be created when Development Mode or Optimize CSS option are enabled in template manager section in backend of your site.

[Author]

Posts