0
Welcome Guest! Login
0 items Join Now

[ANSWERED] Update Gantry broke site

    • Luke Douglas's Avatar
    • Luke Douglas
    • Hero Rocketeer
    • Posts: 322
    • Thanks: 15
    • Another Old Hack!

    [ANSWERED] Update Gantry broke site

    Posted 11 years 3 months ago
    • When I updated the Gantry template, it broke one of my client sites where we had added some additional positions.

      When updating Gantry, if the 'index.php' template file is set to 'read-only' / '444', will that stop the entire Gantry update or just disregard / skip the 'index.php' file?
    • Last Edit: 11 years 3 months ago by Luke Douglas.
    • Just another old hacker!
    • David Goode's Avatar
    • David Goode
    • Preeminent Rocketeer
    • Posts: 17058
    • Thanks: 890
    • Web Designer and Host

    Re: [ANSWERED] Update Gantry broke site

    Posted 11 years 3 months ago
    • Hi there,

      If I recall correctly it will just skip the file.

      What version of gantry template did you update from and to?

    • Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information
    • Luke Douglas's Avatar
    • Luke Douglas
    • Hero Rocketeer
    • Posts: 322
    • Thanks: 15
    • Another Old Hack!

    Re: [ANSWERED] Update Gantry broke site

    Posted 11 years 3 months ago
    • David,

      Typical update: 4.1.19 to 4.1.20.

      This is one of two sites out of about 100+ sites that I have direclty modified the template to add some additional positions. I have set the index.php, templateDetails.xml and the template-options.xml to '444' read-only so they won't be overwritten in the future. I did have backups so it was a quick recovery and, to be sure, I did cross-check of the original template files to ensure there were no changes in these two versions.
    • Just another old hacker!

Time to create page: 0.061 seconds