Support

Account

Forum Replies Created

  • It depends how you set everything up. I assume you have the following repository added:

    
    { 
      "type": "package", 
      "package": {  
        "name": "advanced-custom-fields/advanced-custom-fields-pro",
        "version": "5.4.1", 
        "type": "wordpress-plugin",
        "dist": { 
          "type": "zip", 
          "url": "https://connect.advancedcustomfields.com/index.php?p=pro&a=download"
        },
        "require": {
          "philippbaschke/acf-pro-installer": "^1.0", 
          "composer/installers": "^1.0"
        } 
      } 
    }
    

    Please notice that package.dist.url does not contain the version number (acf-pro-installer will add it automatically).

    You definitely need to update the package.version field to the new desired version.

    If you require an exact version like this:

    
    "require": {
        "advanced-custom-fields/advanced-custom-fields-pro": "5.4.1"
      }
    

    then you need to update the version there as well.

    If you just require any version like this:

    
    "require": {
        "advanced-custom-fields/advanced-custom-fields-pro": "*"
      }
    

    you can just leave it like this.

    ACF PRO should be updated when you run composer update now.

    Please let me know if you have any problems when you use this procedure. Please provide the content of your composer.json file to make debugging easier. 🙂

  • @adamtomat Thank you for promoting acf-pro-installer.

    If anyone has questions about it, feel free to ask them here. I will try to help you as good as I can 🙂

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