Fatal error when updating to latest version using git tools

  • Resolved isradlt

    (@isradlt)


    7 months, 3 weeks ago

    Hi,

    I get a fatal error after updating the plugin to the latest version:

    Error Details

An error of type E_ERROR was caused in line 184 of the file /public_html/www.example.com/wp-content/plugins/advanced-access-manager/application/Core/Migration.php. Error message: Uncaught UnexpectedValueException: DirectoryIterator::__construct(/public_html/www.example.com/wp-content/plugins/advanced-access-manager/application/Migration): failed to open dir: No such file or directory in /public_html/www.example.com/wp-content/plugins/advanced-access-manager/application/Core/Migration.php:184

    I use git tools to deploy changes to my website, so the problem here is that git does not commit empty directories, which is the case in advanced-access-manager/application/Migration. So I ended up creating an empty .gitkeep file in the Migration directory to get the site working again.

    I just wanted to comment on the issue in case the developer considers leaving an empty file in that directory in future versions, so it doesn’t affect other users deploying with git.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

  • I handle production deployment with git and this issue also bit me. I added a .gitkeep file to the Migration directory just as the OP did, but I expect that won’t survive the next plugin update unless I manually recreate the file.

    The developer adding an empty file to the folder would be one solution. Another could be to short-circuit the migration process if the folder doesn’t exist. If it can be addressed, however it is, that would be great.

    Thank you!

    Same problem, need a solution asap.

    Same problem here, thankfully found this as I couldn’t figure out what was happening. Hoping for a solution!

    vermadeepak

    (@vermadeepak)

    I am also facing same issue while deploying the AAM update from staging to Live. I am not able to reproduce this issue on staging but directly getting it on Live. On staging it is working fine.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error when updating to latest version using git tools’ is closed to new replies.