Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • ether1 Friend
    #968145

    In the past we purchased a quickstart package for the JA Sugite template, this works fine and we have experience with using many other Joomla Template quickstart packages with other providers in the past.

    However we have recently come to notice that during an upgrade or migration process the template generates new css files each time. Now if a user like ourselves has modified their css files this presents a problem. Especially in the event that you use the same template to support more than one domain, it just creates additional work for our team.

    Now we have narrowed this down to 3 css files but that’s not the point this shouldn’t really be happening and is bad design unless done deliberately in order to make these processes more difficult for your clients and generate more work for JA. It could just be a bug I may be wrong but we have never had this experience with any other template provider in the past.

    We are considering purchasing a template for a new range of sites which would again require a quick install deployment, however we are concerned whether or not to do this via Joomlart as we do not want to continuously make this process more and more difficult. Please can someone advise on this as we are looking to do this very soon and are considering alternative providors.

    regards Ether

    Pankaj Sharma Moderator
    #968614

    Hi
    Joomla update does not update the template CSS files , It only happens when u update the template the files are overridden by the fresh files .
    If you are making custom changes in the CSS file , I suggest you to use custom.css file to apply the custom changes , this will not be overridden on template updates .
    You have to create the custom.css file in /CSS/ folder of the template and add the custom code .

    Always take backup of site before template/Joomla updates .

    ether1 Friend
    #968665

    Hi Panjak,

    you are completely misunderstanding me. We are not saying that our css files are being overridden, we do have our own css files for unique stylings but we have also modified one of the existing colour shemes and these files are always backed up before any upgrade/migration process.

    The problem we are having in ANY of the following cases, backup,migration OR upgrade is that the template is creating brand new css files dynamically with completely different file names and the templates referencings are also being overridden to point to these new template files.

    Our original files still exist, the template just doesn’t point to them so we have to manually resolve the issue, kind of a bad design flaw.

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

    Pankaj Sharma Moderator
    #968666

    Hi
    may i know the css file in which you are making changes and changes are lost when u migrate or copy the site . Because css were not change except template updated

    ether1 Friend
    #968669
    This reply has been marked as private.
    ether1 Friend
    #968670
    This reply has been marked as private.
    Pankaj Sharma Moderator
    #968675

    Hi
    its look like you are making changes in the T3-assets folder , its cached folder that cache the css style.
    Do not make changes in this folder . You have to apply the changes via custom.css file or directly in css folder present in the template .

    Take backup of site before applying the changes on site .

    ether1 Friend
    #968681

    Hi Panjak, we are using a custom css file for unique styles of our own, however we are also altering the purple theme. We haven’t had much experience with the t3 framework but when using firebug to point to the CSS attributes it points to the files within the t3 directory. So slightly confusing.

    We always take a backup before/after making changes and usually the CSS elements point directly to the templates directory (on other templates), so rightly as you mentioned we make our changes there. We have only made changes via the t3 css directory as this is where firebug/developer tools pointed to.

    We will bare this in mind for future deployments. However this still does not explain the bug with unique css file creation? I assume the t3 framework is attempting to re-create the original css file as the cached version has been altered but surely it shouldn’t override the css file references within the template itself ?

    Pankaj Sharma Moderator
    #968712

    Hi
    When the CSS compression is ON they will be compressed and run through t3-assets folder that will use to store the cached style and js files .
    You have to keep in mind that do Not make changes in this folder because it’s temporary CSS .

Viewing 9 posts - 1 through 9 (of 9 total)

This topic contains 8 replies, has 2 voices, and was last updated by  Pankaj Sharma 7 years, 7 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum