Meta Box

Composer is not downloading the correct version of AIO

Support › Meta Box AIO › Composer is not downloading the correct version of AIOResolved

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • April 30, 2021 at 11:04 PM #27792
    Georgetown University Web ServicesGeorgetown University Web Services
    Participant

    Hello! I am pulling in Meta Box and Meta Box AIO into my WordPress project repo via Composer. Both are being installed successfully, but I am not getting the correct version of Meta Box AIO. Composer is pulling down version 1.11.19, while I am requesting master, which, according to my account page, should be at 1.13.9.

    I constructed the composer file based on your documentation at https://docs.metabox.io/extensions/composer. This is the relevant snippet of my composer file:

    "require": {
    "meta-box/meta-box-aio": "dev-master",
    "wpackagist-plugin/meta-box": "5.3.*",
    <OTHER NON-METABOX PACKAGES HERE>
    },
    "repositories": [
    {
    "url": "https://wpackagist.org",
    "type": "composer"
    },
    {
    "type": "composer",
    "url": "https://packages.metabox.io/MY_API_KEY_HERE"
    },
    ]
    }
    <code></code>

    Without being able to look at your repo, it seems like master does not have version 1.13.9 of Meta Box AIO. Is that a correct assessment or are we missing something in our composer file?

    Thanks!

    May 4, 2021 at 3:16 PM #27888
    Anh TranAnh Tran
    Keymaster

    Hi,

    I've just tested again with your snippet and see Composer always pull the latest version of Meta Box AIO. Can you please try again?

    May 4, 2021 at 9:32 PM #27904
    Georgetown University Web ServicesGeorgetown University Web Services
    Participant

    Hi Ahn! Thank you for the reply! We actually believe this was a caching issue. We were just only able to pull down the correct version using the --no-cache flag when doing a composer update. Is it possible that your system has your headers set up in a different way that other systems, e.g. GitHub?

    Regardless, busting the cache seems to be the solution for us. Thanks again!

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.