Media Cloud unable to activate extension



  • Hi, i'm getting an error while trying to activate Media Cloud extension :

    There is another version of Media Cloud installed. Please deactivate it before activating this one.

    alt text

    I use Bedrock edition (3.1)

    {
      "name": "yproximite/wordpress",
      "type": "project",
      "license": "proprietary",
      "description": "",
      "homepage": "https://example.com",
      "authors": [
      ],
      "config": {
        "preferred-install": "dist",
        "dropin-installer": "copy"
      },
      "repositories": [
        {
          "type": "composer",
          "url": "https://repo.packagist.com/yproximite/"
        },
        {
          "packagist.org": false
        }
      ],
      "require": {
        "php": ">=7.3",
        "composer/installers": "^1.4",
        "vlucas/phpdotenv": "^3.0",
        "roots/wordpress": "^5.0",
        "oscarotero/env": "^1.1",
        "roots/wp-password-bcrypt": "^1.0",
        "roots/wp-config": "^1.0",
        "wpackagist-plugin/worker": "^4.6",
        "wpackagist-plugin/wp-smushit": "^3.1",
        "wpackagist-plugin/cookie-notice": "^1.2",
        "wpackagist-plugin/post-thumbnail-editor": "^2.4",
        "wpackagist-plugin/regenerate-thumbnails": "^3.0",
        "wpackagist-plugin/wp-mail-smtp": "^1.4",
        "wp-cli/wp-cli-bundle": "^2.0",
        "wpackagist-plugin/classic-editor": "^1.3",
        "deliciousbrains-plugin/wp-migrate-db-pro": "*",
        "deliciousbrains-plugin/wp-migrate-db-pro-cli": "*",
        "deliciousbrains-plugin/wp-migrate-db-pro-media-files": "*",
        "koodimonni-language/fr_fr": "^5.0",
        "wpackagist-plugin/timber-library": "^1.8",
        "ilab/ilab-media-tools": "^3.1",
        "wpackagist-plugin/google-sitemap-generator": "^4.1",
        "wpackagist-plugin/all-in-one-seo-pack": "^3.2",
        "wpackagist-plugin/formidable": "^4.02",
        "wpackagist-plugin/google-analytics-dashboard-for-wp": "^5.3",
        "wpackagist-plugin/elementor": "^2.7",
        "yproximite/elementor-pro": "^2.6"
      },
      "require-dev": {
        "friendsofphp/php-cs-fixer": "^2.14",
        "roave/security-advisories": "dev-master"
      },
      "conflict": {
        "wpackagist-plugin/ml-slider": "*",
        "wpackagist-plugin/nextgen-gallery": "*"
      },
      "extra": {
        "installer-paths": {
          "web/app/mu-plugins/{$name}/": ["type:wordpress-muplugin"],
          "web/app/plugins/{$name}/": ["type:wordpress-plugin"],
          "web/app/themes/{$name}/": ["type:wordpress-theme"]
        },
        "dropin-paths": {
          "web/app/languages/": ["vendor:koodimonni-language"],
          "web/app/languages/plugins/": ["vendor:koodimonni-plugin-language"],
          "web/app/languages/themes/": ["vendor:koodimonni-theme-language"]
        },
        "wordpress-install-dir": "web/wp",
        "paas": {
          "php-config": [
            "opcache.max_accelerated_files=15000"
          ]
        }
      },
      "scripts": {
        "post-root-package-install": []
      }
    }
    


  • @marmorag

    Comment out lines 73-84 in ilab-media-tools.php and let me know if that works.



  • I cannot change code in production the container will be cloned and modification lost just after I disconnect from the container.
    And we don't reproduce the problem on local environment



  • @marmorag

    Well the issue is that Media Cloud is trying to determine if a class it's using currently exists, because I've had support tickets were people have inexplicably had multiple copies/versions of the plugin installed and activated.

    So your option is to fork the repo, make that simple change, send me a PR and use your repo until I can get around to fixing it, which I will try to do in the morning (it's 9:30pm right now).

    I'm 100% that's the issue because when you install via composer, Media Cloud's namespace becomes part of the global namespace, instead of specific to the plugin meaning that test for class existence is always TRUE.



  • Thanks, we will wait for your patch to come.



  • @marmorag It should be fixed in 3.2.2 which is up on github now.



  • Thank you very much @jong !


Log in to reply