0
Welcome Guest! Login
0 items Join Now

SOLVED Invalid extension update when updating to 4.1.10

  • Re: SOLVED Invalid extension update when updating to 4.1.10

    Posted 11 years 6 months ago
    • I got a successful update using 3.1.1 but with the following "Warnings" Why did this happen?

      Warning
      Failed deleting index.html

      Failed to delete /home/websitefolder/public_html/websitefoldername/libraries/gantry/admin

      Failed deleting gantry.config.php

      Failed to delete /home/websitefolder/public_html/websitefoldername/libraries/gantry/gantry.config.php

      Failed deleting phpQuery.php

      Failed to delete /home/websitefolder/public_html/websitefoldername/libraries/gantry/libs

      Failed deleting gantrymenuformatter.class.php

      Failed to delete /home/websitefolder/public_html/websitefoldername/libraries/gantry/facets

      Failed deleting belatedpng.php

      Failed to delete /home/websitefolder/public_html/websitefoldername/libraries/gantry/features

      Failed deleting browser-engines.js

      Failed to delete /home/websitefolder/public_html/websitefoldername/libraries/gantry/js


      and then it said....

      Message
      Update plugin was successful.

      Gantry Library installation was successful
      Gantry Component update was successful
      Gantry System Plugin update was successful

      Everything seems to be working but these warnings are a little scary. Do I need to do anything manually?
    • DanG's Avatar
    • DanG
    • Preeminent Rocketeer
    • Posts: 36750
    • Thanks: 3229
    • Custom work done

    Re: SOLVED Invalid extension update when updating to 4.1.10

    Posted 11 years 6 months ago
    • Triplicate wrote:
      I got a successful update using 3.1.1 but with the following "Warnings" Why did this happen?

      Warning
      Failed deleting index.html

      Everything seems to be working but these warnings are a little scary. Do I need to do anything manually?
      It's probably that in your last go around those files might not have been on the server anymore but somehow still in your DB.
      If you have any concerns at all, I would simply re-install 4.1.10 manually and see if there are any further error messages.
      You can safely install the same version over itself with no issues.

Time to create page: 0.050 seconds