Code Monkey home page Code Monkey logo

wordpress-core's People

Contributors

johnpbloch avatar johnpbloch-bot avatar tyrann0us avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

wordpress-core's Issues

Can't install with composer 2

  - Syncing johnpbloch/wordpress-core (5.5.2) into cache
    Failed to download johnpbloch/wordpress-core from source: The process "git clone --mirror 'https://github.com/johnpbloch/wordpress-core.git' '/home/marcelo/.cache/composer/vcs/https---github.com-johnpbloch-wordpress-core.git/'" exceeded the timeout of 300 seconds.
    Now trying to download from dist

Composer install fails on WordPressCoreInstaller.php:40

Upon deploying my website I run a composer install. This currently results in an error from this line

https://github.com/johnpbloch/wordpress-core-installer/blob/master/src/johnpbloch/Composer/WordPressCoreInstaller.php#L40

Here is the output from Composer with the verbosity turned up.

Reading ./composer.json
Loading config file ./composer.json
Checked CA file /etc/ssl/certs/ca-certificates.crt: valid
Executing command (/srv/www/{{REDACTED}}/releases/20170517162303): git
branch --no-color --no-abbrev -v
Executing command (/srv/www/{{REDACTED}}/releases/20170517162303): git
describe --exact-match --tags
Executing command (/srv/www/{{REDACTED}}/releases/20170517162303): git log
--pretty="%H" -n1 HEAD
Executing command (/srv/www/{{REDACTED}}/releases/20170517162303): hg
branch
Executing command (/srv/www/{{REDACTED}}/releases/20170517162303): fossil
branch list
Executing command (/srv/www/{{REDACTED}}/releases/20170517162303): fossil
tag list
Executing command (/srv/www/{{REDACTED}}/releases/20170517162303): svn
info --xml
Failed to initialize global composer: Composer could not find the config
file: /home/web/.config/composer/composer.json
To initialize a project, please create a composer.json file as described in
the https://getcomposer.org/ "Getting Started" section
Reading /srv/www/{{REDACTED}}/releases/20170517162303/vendor/composer/inst
alled.json
Loading plugin johnpbloch\Composer\WordPressCorePlugin
Loading plugin Composer\Installers\Plugin
Running 1.4.2 (2017-05-17 08:17:52) with PHP 7.0.8-4+deb.sury.org~trusty+1 on
Linux / 3.16.0-45-generic
Reading ./composer.lock
Loading composer repositories with package information
Installing dependencies from lock file
Reading ./composer.lock
Resolving dependencies through SAT
Dependency resolution completed in 0.001 seconds
Analyzed 98 packages to resolve dependencies
Analyzed 135 rules to resolve dependencies
Package operations: 24 installs, 1 update, 0 removals
Installs: advanced-custom-fields/advanced-custom-fields-pro:5.3.9.2,
johnpbloch/wordpress-core:4.7.5, wpackagist-plugin/akismet:3.3.2, wpackagist-
plugin/better-wp-security:6.2.1, wpackagist-plugin/breadcrumb-trail:1.0.0,
wpackagist-plugin/disable-comments:1.6, wpackagist-plugin/duplicate-post:3.2,
wpackagist-plugin/enhanced-media-library:2.4.4, wpackagist-plugin/ewww-image-
optimizer:3.3.1, wpackagist-plugin/force-strong-passwords:1.7, wpackagist-
plugin/location-nav-menu-for-acf:1.1.1, wpackagist-plugin/members:1.1.3,
wpackagist-plugin/posts-to-posts:1.6.5, wpackagist-plugin/relevanssi:3.5.9.1,
wpackagist-plugin/rewrite-rules-inspector:1.2.1, wpackagist-plugin/safe-
redirect-manager:1.7.8, wpackagist-plugin/simple-301-redirects:1.07,
wpackagist-plugin/simple-301-redirects-addon-bulk-uploader:1.0.14,
wpackagist-plugin/stop-user-enumeration:1.3.8, wpackagist-
plugin/stream:3.2.0, wpackagist-plugin/sucuri-scanner:1.8.3, wpackagist-
plugin/user-switching:1.0.9, wpackagist-plugin/wordpress-seo:4.7.1,
wpackagist-plugin/wp-optimize:2.1.1
Updates: composer/installers:v1.3.0
  - Updating composer/installers (v1.2.0 => v1.3.0): Reading /home/web/.cache
/composer/files/composer/installers/41f0abb210f1e24fcf418eaec2b2524695cdb5d1.
zip from cache
Loading from cache Extracting archive
    REASON: Required by the root package: Install command rule (install
composer/installers v1.3.0)

  - Installing advanced-custom-fields/advanced-custom-fields-pro (5.3.9.2):
Reading /home/web/.cache/composer/files/advanced-custom-fields/advanced-
custom-fields-pro/0d10b03837e2f9e431d70a26524565f9a08e9845.zip from cache
Loading from cache
 Extracting archive    REASON: Required by the root package: Install command
rule (install advanced-custom-fields/advanced-custom-fields-pro 5.3.9.2)



  [InvalidArgumentException]
  Two packages cannot share the same directory!


Exception trace:
 () at /srv/www/{{REDACTED}}/releases/20170517162303/vendor/johnpbloch
/wordpress-core-
installer/src/johnpbloch/Composer/WordPressCoreInstaller.php:40
 johnpbloch\Composer\WordPressCoreInstaller->getInstallPath() at
phar:///usr/local/bin/composer/src/Composer/Installer/LibraryInstaller.php:83
 Composer\Installer\LibraryInstaller->install() at phar:///usr/local/bin/comp
oser/src/Composer/Installer/InstallationManager.php:173
 Composer\Installer\InstallationManager->install() at phar:///usr/local/bin/c
omposer/src/Composer/Installer/InstallationManager.php:160
 Composer\Installer\InstallationManager->execute() at
phar:///usr/local/bin/composer/src/Composer/Installer.php:584
 Composer\Installer->doInstall() at
phar:///usr/local/bin/composer/src/Composer/Installer.php:223
 Composer\Installer->run() at
phar:///usr/local/bin/composer/src/Composer/Command/InstallCommand.php:119
 Composer\Command\InstallCommand->execute() at
phar:///usr/local/bin/composer/vendor/symfony/console/Command/Command.php:267
 Symfony\Component\Console\Command\Command->run() at
phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:846
 Symfony\Component\Console\Application->doRunCommand() at
phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:191
 Symfony\Component\Console\Application->doRun() at
phar:///usr/local/bin/composer/src/Composer/Console/Application.php:227
 Composer\Console\Application->doRun() at
phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:122
 Symfony\Component\Console\Application->run() at
phar:///usr/local/bin/composer/src/Composer/Console/Application.php:100
 Composer\Console\Application->run() at
phar:///usr/local/bin/composer/bin/composer:54
 require() at /usr/local/bin/composer:24

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev]
[--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress]
[--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a
|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--]
[<packages>]...
fatal: [162.13.106.128]: FAILED! => {"changed": true, "cmd": ["composer", "install", "--no-ansi", "--no-dev", "--no-interaction", "--no-progress", "--optimize-autoloader", "--no-scripts", "-vvv"], "delta": "0:00:00.483702", "end": "2017-05-17 16:23:15.931668", "failed": true, "rc": 1, "start": "2017-05-17 16:23:15.447966", "stderr": "Reading ./composer.json\nLoading config file ./composer.json\nChecked CA file /etc/ssl/certs/ca-certificates.crt: valid\nExecuting command (/srv/www/{{REDACTED}}/releases/20170517162303): git branch --no-color --no-abbrev -v\nExecuting command (/srv/www/{{REDACTED}}/releases/20170517162303): git describe --exact-match --tags\nExecuting command (/srv/www/{{REDACTED}}/releases/20170517162303): git log --pretty=\"%H\" -n1 HEAD\nExecuting command (/srv/www/{{REDACTED}}/releases/20170517162303): hg branch\nExecuting command (/srv/www/{{REDACTED}}/releases/20170517162303): fossil branch list\nExecuting command (/srv/www/{{REDACTED}}/releases/20170517162303): fossil tag list\nExecuting command (/srv/www/{{REDACTED}}/releases/20170517162303): svn info --xml\nFailed to initialize global composer: Composer could not find the config file: /home/web/.config/composer/composer.json\nTo initialize a project, please create a composer.json file as described in the https://getcomposer.org/ \"Getting Started\" section\nReading /srv/www/{{REDACTED}}/releases/20170517162303/vendor/composer/installed.json\nLoading plugin johnpbloch\\Composer\\WordPressCorePlugin\nLoading plugin Composer\\Installers\\Plugin\nRunning 1.4.2 (2017-05-17 08:17:52) with PHP 7.0.8-4+deb.sury.org~trusty+1 on Linux / 3.16.0-45-generic\nReading ./composer.lock\nLoading composer repositories with package information\nInstalling dependencies from lock file\nReading ./composer.lock\nResolving dependencies through SAT\nDependency resolution completed in 0.001 seconds\nAnalyzed 98 packages to resolve dependencies\nAnalyzed 135 rules to resolve dependencies\nPackage operations: 24 installs, 1 update, 0 removals\nInstalls: advanced-custom-fields/advanced-custom-fields-pro:5.3.9.2, johnpbloch/wordpress-core:4.7.5, wpackagist-plugin/akismet:3.3.2, wpackagist-plugin/better-wp-security:6.2.1, wpackagist-plugin/breadcrumb-trail:1.0.0, wpackagist-plugin/disable-comments:1.6, wpackagist-plugin/duplicate-post:3.2, wpackagist-plugin/enhanced-media-library:2.4.4, wpackagist-plugin/ewww-image-optimizer:3.3.1, wpackagist-plugin/force-strong-passwords:1.7, wpackagist-plugin/location-nav-menu-for-acf:1.1.1, wpackagist-plugin/members:1.1.3, wpackagist-plugin/posts-to-posts:1.6.5, wpackagist-plugin/relevanssi:3.5.9.1, wpackagist-plugin/rewrite-rules-inspector:1.2.1, wpackagist-plugin/safe-redirect-manager:1.7.8, wpackagist-plugin/simple-301-redirects:1.07, wpackagist-plugin/simple-301-redirects-addon-bulk-uploader:1.0.14, wpackagist-plugin/stop-user-enumeration:1.3.8, wpackagist-plugin/stream:3.2.0, wpackagist-plugin/sucuri-scanner:1.8.3, wpackagist-plugin/user-switching:1.0.9, wpackagist-plugin/wordpress-seo:4.7.1, wpackagist-plugin/wp-optimize:2.1.1\nUpdates: composer/installers:v1.3.0\n  - Updating composer/installers (v1.2.0 => v1.3.0): Reading /home/web/.cache/composer/files/composer/installers/41f0abb210f1e24fcf418eaec2b2524695cdb5d1.zip from cache\nLoading from cache Extracting archive\n    REASON: Required by the root package: Install command rule (install composer/installers v1.3.0)\n\n  - Installing advanced-custom-fields/advanced-custom-fields-pro (5.3.9.2): Reading /home/web/.cache/composer/files/advanced-custom-fields/advanced-custom-fields-pro/0d10b03837e2f9e431d70a26524565f9a08e9845.zip from cache\nLoading from cache\n Extracting archive    REASON: Required by the root package: Install command rule (install advanced-custom-fields/advanced-custom-fields-pro 5.3.9.2)\n\n\n                                                 \n  [InvalidArgumentException]                     \n  Two packages cannot share the same directory!  \n                                                 \n\nException trace:\n () at /srv/www/{{REDACTED}}/releases/20170517162303/vendor/johnpbloch/wordpress-core-installer/src/johnpbloch/Composer/WordPressCoreInstaller.php:40\n johnpbloch\\Composer\\WordPressCoreInstaller->getInstallPath() at phar:///usr/local/bin/composer/src/Composer/Installer/LibraryInstaller.php:83\n Composer\\Installer\\LibraryInstaller->install() at phar:///usr/local/bin/composer/src/Composer/Installer/InstallationManager.php:173\n Composer\\Installer\\InstallationManager->install() at phar:///usr/local/bin/composer/src/Composer/Installer/InstallationManager.php:160\n Composer\\Installer\\InstallationManager->execute() at phar:///usr/local/bin/composer/src/Composer/Installer.php:584\n Composer\\Installer->doInstall() at phar:///usr/local/bin/composer/src/Composer/Installer.php:223\n Composer\\Installer->run() at phar:///usr/local/bin/composer/src/Composer/Command/InstallCommand.php:119\n Composer\\Command\\InstallCommand->execute() at phar:///usr/local/bin/composer/vendor/symfony/console/Command/Command.php:267\n Symfony\\Component\\Console\\Command\\Command->run() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:846\n Symfony\\Component\\Console\\Application->doRunCommand() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:191\n Symfony\\Component\\Console\\Application->doRun() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:227\n Composer\\Console\\Application->doRun() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:122\n Symfony\\Component\\Console\\Application->run() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:100\n Composer\\Console\\Application->run() at phar:///usr/local/bin/composer/bin/composer:54\n require() at /usr/local/bin/composer:24\n\ninstall [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>]...", "stdout": "", "stdout_lines": [], "warnings": []}

This website has existed for a while and this error has only just started happening. I've already jumped through the usual hoops of upgrading to the meta wordpress packages since you changed the way your packages worked but this has had no effect.

Here is my composer.json. Is there anything obviously wrong in the way that you can see I'm using your packages?

{
  "name": "roots/bedrock",
  "type": "project",
  "license": "MIT",
  "description": "A modern WordPress stack",
  "homepage": "https://roots.io/bedrock/",
  "authors": [
    {
      "name": "Scott Walkinshaw",
      "email": "[email protected]",
      "homepage": "https://github.com/swalkinshaw"
    },
    {
      "name": "Ben Word",
      "email": "[email protected]",
      "homepage": "https://github.com/retlehs"
    }
  ],
  "keywords": [
    "bedrock", "roots", "wordpress", "stack", "composer", "vagrant", "wp"
  ],
  "support": {
    "issues": "https://github.com/roots/bedrock/issues",
    "forum": "https://discourse.roots.io/category/bedrock"
  },
  "config": {
    "preferred-install": "dist"
  },
  "repositories": [
    {
      "type": "composer",
      "url": "https://wpackagist.org"
    },
    {
      "type": "package",
      "package": {
        "name": "advanced-custom-fields/advanced-custom-fields-pro",
        "version": "5.3.9.2",
        "type": "wordpress-plugin",
        "dist": {
          "type": "zip",
          "url": "https://connect.advancedcustomfields.com/index.php?{{REDACTED}}"
        }
      }
    }
  ],
  "require": {
    "php": ">=5.5",
    "composer/installers": "~1.2.0",
    "vlucas/phpdotenv": "^2.0.1",
    "oscarotero/env": "^1.0",
    "roots/wp-password-bcrypt": "1.0.0",
    "wpackagist-plugin/akismet": "^3.0",
    "wpackagist-plugin/safe-redirect-manager": "^1.7",
    "wpackagist-plugin/duplicate-post": "^3.1",
    "wpackagist-plugin/disable-comments": "^1.2",
    "wpackagist-plugin/stream": "^3.0",
    "wpackagist-plugin/sucuri-scanner": "*",
    "wpackagist-plugin/rewrite-rules-inspector": "^1.2",
    "advanced-custom-fields/advanced-custom-fields-pro": "^5.3.9.2",
    "wpackagist-plugin/wp-optimize": "^2.1",
    "wpackagist-plugin/posts-to-posts": "^1.6",
    "wpackagist-plugin/wordpress-seo": "^4.4",
    "wpackagist-plugin/user-switching": "^1.0.9",
    "wpackagist-plugin/ewww-image-optimizer": "*",
    "wpackagist-plugin/members": "^1.1.1",
    "wpackagist-plugin/relevanssi": "^3.5.8",
    "wpackagist-plugin/breadcrumb-trail": "^1.0.0",
    "wpackagist-plugin/location-nav-menu-for-acf": "*",
    "wpackagist-plugin/force-strong-passwords": "*",
    "jjgrainger/wp-custom-post-type-class": "dev-master",
    "wpackagist-plugin/better-wp-security": "^6.1.0",
    "wpackagist-plugin/enhanced-media-library": "^2.4",
    "wpackagist-plugin/simple-301-redirects": "^1.07",
    "wpackagist-plugin/simple-301-redirects-addon-bulk-uploader": "^1.0",
    "wpackagist-plugin/stop-user-enumeration": "^1.3",
    "johnpbloch/wordpress-core-installer": "^0.2.1",
    "johnpbloch/wordpress-core": "^4.7"
  },
  "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"]
    },
    "wordpress-install-dir": "web/wp"
  },
  "scripts": {
    "test": [
      "vendor/bin/phpcs --ignore=web/wp/,vendor/ -n -s ."
    ]
  }
}

add possibility to install own theme

now it could be handled by composer hooks, but it looks ugly.

    "scripts": {
        "pre-install-cmd": [
            "mv wordpress/wp-content/themes/custom-theme temp-custom-theme"
        ],
        "post-install-cmd": [
            "mv temp-custom-theme wordpress/wp-content/themes/custom-theme"
        ],
        "pre-update-cmd": [
            "mv wordpress/wp-content/themes/custom-theme temp-custom-theme"
        ],
        "post-update-cmd": [
            "mv temp-custom-theme wordpress/wp-content/themes/custom-theme"
        ]
    }

some themes missing from wp-content when installed with composer

Hello, I noticed there are some themes which previously lived in wp-content and are no longer there in the latest version. I see all the twenty* theme directories on github but when I install with composer I only get twentyfifteen and up:

$ ls -l web/wp/wp-content/themes/
total 16
-rw-r--r-- 1 ubuntu adm   28 May 16 18:48 index.php
drwxr-xr-x 6 ubuntu adm 4096 May 16 18:48 twentyfifteen/
drwxr-xr-x 5 ubuntu adm 4096 May 16 18:48 twentyseventeen/
drwxr-xr-x 7 ubuntu adm 4096 May 16 18:48 twentysixteen/

Did I do something wrong, or what happened?

We had been using 4.7.3 and upgraded to 4.7.5. I normally do this by composer remove the old package and then composer require the new one. This time for the first time I got an error Two packages cannot share the same directory! which I solved after some googling by running composer install once after removing, then again after requiring. I'm not sure if that's related.

Here is the wordpress require line in our composer.json: https://github.com/mlaa/commons/blob/master/composer.json#L274

No Sync in over a Month

It seems the repository hasn't been synced with WordPress in over a month. The last change is from October 11.

#16 is probably connected to this.

Updating delete all WP files

Hi I use your wp-core package in composer with other packagist plugins to update WP via composer.
Today If I do an usual composer update it states: "Upgrading johnpbloch/wordpress-core (6.4.3 => 6.5.0)"
After that my wp site is like reinstalled all themes files and plugins are erased
Please assist

License

Hi,

I would like to ask you, we would like to use wordpress, but the project and company can't to use it under GPL-2.0.
May I do it this way? That we will license it under LGPL license or not?

This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

Package without wp-content

Do you plan to generate a package that does not include wp-content?

https://wordpress.org/wordpress-4.9.8-no-content.zip

Clean up tag branches

This issue is to track the efforts to clean up all of the tag-* branches as mentioned by @Seldaek in #18.

  • Merge tags into release branches
  • Delete tag branches
  • Update build repo to always build tags in release branches

From `wordpress` to `wordpress-core`

Just chimed in to clarify whether this repo/package change is permanent and we should switch from johnpbloch/wordpress to johnpbloch/wordpress-core in our composer.json requirements?

Call to undefined function get_home_path()

Fatal error with version 4.9.6 : Call to undefined function get_home_path()

There is a problem for all my wordpress sites.
I use composer with Bedrock and I have to rollback to your version 4.9.5.

Please fix this bug

Can't install with Composer (1.10.20 or 2.0.11)

PHP: 7.4.11
Composer: 2.0.11 (tried already 1.10.20 originally)

I'm trying to install wordpress via composer with the simplest setup possible

{
  "repositories": [
    {
      "type": "composer",
      "url": "https://wpackagist.org"
    }
  ],
  "require": {
    "johnpbloch/wordpress": "^5.6"
  }
}

But I'm getting the follow error

Loading composer repositories with package information
Updating dependencies
Lock file operations: 3 installs, 0 updates, 0 removals
  - Locking johnpbloch/wordpress (5.6.2)
  - Locking johnpbloch/wordpress-core (5.6.2)
  - Locking johnpbloch/wordpress-core-installer (2.0.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 3 installs, 0 updates, 0 removals
  - Installing johnpbloch/wordpress-core-installer (2.0.0): Extracting archive
Plugin initialization failed (include(/home/vagrant/code/my-website/vendor/johnpbloch/wordpress-core-installer/src/johnpbloch/Composer/WordPressCorePlugin.php): failed to open stream: No such file or directory), uninstalling plugin
  - Removing johnpbloch/wordpress-core-installer (2.0.0)
    Install of johnpbloch/wordpress-core-installer failed


  [RuntimeException]
  Could not delete /home/vagrant/code/my-website/vendor/johnpbloch/wordpress-core-installer/src:

I can navigate to the folder and I see that file there

vagrant@homestead:~/code/my-website/vendor/johnpbloch/wordpress-core-installer/src/johnpbloch/Composer$ pwd & ll
[1] 12443
/home/vagrant/code/my-website/vendor/johnpbloch/wordpress-core-installer/src/johnpbloch/Composer
total 8
drwxrwxrwx 1 vagrant vagrant    0 Apr 16  2020 ./
drwxrwxrwx 1 vagrant vagrant    0 Apr 16  2020 ../
-rwxrwxrwx 1 vagrant vagrant 3614 Apr 16  2020 WordPressCoreInstaller.php*
-rwxrwxrwx 1 vagrant vagrant 1560 Apr 16  2020 WordPressCorePlugin.php*
[1]+  Done                    pwd
vagrant@homestead:~/code/my-website/vendor/johnpbloch/wordpress-core-installer/src/johnpbloch/Composer$

p.s I have no problem installing other packages via composer (e.g. Laravel)

Any ideas?

Missing themes ?

Hi @johnpbloch,

I'm using your project to manage a simple Wordpress with Composer and I just found a strange thing :
My installation seems to have only the last 3 official themes, instead of the 11 ones from the official repo

If you look at the 5.6 branch, you can see all the themes :
https://github.com/johnpbloch/wordpress-core/tree/5.6/wp-content/themes
but if you look at the 5.6.0 tag, there is only the 3 latest ones :
https://github.com/johnpbloch/wordpress-core/tree/5.6.0/wp-content/themes

Is there a reason for this ?
I will now require my missing "wpackagist-theme/twentyseventeen", but I would like to understand why all the default themes are not provided with your repo.
Thanks in advance

composer install wpackagist theme in wrong folder

Hi all,

I'm testing metabolism/wordpress-bundle-demo (latest issue with johnpbloch/wordpress-core: 5.8), and trying to install plugins and themes with composer.
For plugins, it will be installed in public/wp-bundle/plugins, as configured in the composer.json file. But for the themes, I will create a new folder at the root of the project 'wp-content/themes / ...' with the new theme.
I am under linux (Ubuntu 21.04 desktop edition) and to have the good behavior in the administration area, I must make a symbolic link to have the same operation as on the wordpress site.
where I had to do:
1 / I copy the wp-content/themes folder to public/edition/wp-content/themes
2 / delete the themes folder in wp-content/ and replace it with a symbolic link from public/edition/wp-content/themes
3 / I copy the content of public/wp-bundle/plugins in public/edition/wp-content/plugins, and after deleting the plugins folder in public/wp-bundle
4 / create 2 symbolic links in public/wp-bundle from public/edition/ wp-content/plugins and public/edition/wp-content/themes
Then everything works fine, but it's so much work to get this result.

  • Is it possible to configure the right folder for installing themes by composer, and by wordpress too?
  • Which folder between public/edition/wp-content/plugins and public/wp-bundle/plugins is the correct one in your installation? Can we then have the correct settings?
  • Why in the administration area, in the Appearance menu, we do not find the management of themes (present in the sources public/edition/wp-admin/themes.php), like the customization of the active theme (present in the sources public/edition/wp-admin/customize.php)

Thank you in advance for your answer

Celtic34fr
Beziers - France

Updating

Hi, Just wondering how hard this has been to keep up-to-date?

I'm considering something similar for https://github.com/idno/known to help with a single-click deploy to heroku without trying to be too opinionated in the upstream.

It would be great to know what challenges someone else treading similar ground has faced.

Could not parse version constraint refs/heads/5.3.x-dev: Invalid version string "refs/heads/5.3.x-dev"

Hi, I use this package to include wordpress in my vendor folder, mainly for autocomplete when developing themes. I tried to run composer update today and found the following error:

composer update
    1/2:        http://repo.packagist.org/p/provider-latest$347a0865883f89580e0ac54b09a94e846178ab395e5cd7bef91a7a54aa76d2ec.json
    2/2:        http://repo.packagist.org/p/provider-2020-07$667dfc61948aa480aa46421f7c2e9724fc764f9f5b1e1f7db3f0d8ccd6a101b1.json
    Finished: success: 2, skipped: 0, failure: 0, total: 2
Loading composer repositories with package information
Updating dependencies (including require-dev)

                                                                                                                                                                  
  [RuntimeException]                                                                                                                                              
  Could not load package johnpbloch/wordpress-core in http://repo.packagist.org: [UnexpectedValueException] Could not parse version constraint refs/heads/5.3.x-  
  dev: Invalid version string "refs/heads/5.3.x-dev"                                                                                                              
                                                                                                                                                                  

                                                                                                          
  [UnexpectedValueException]                                                                              
  Could not parse version constraint refs/heads/5.3.x-dev: Invalid version string "refs/heads/5.3.x-dev"  
                                                                                                          

update [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--lock] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-su
ggest] [--with-dependencies] [--with-all-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore
-platform-reqs] [--prefer-stable] [--prefer-lowest] [-i|--interactive] [--root-reqs] [--] [<packages>]...

I'm not sure if this is related to the "refs/heads/5.3.x" branch name? I've been pulling my hair out (that's a lie, its already gone) trying to figure out why its happening exactly and what I can do about it. Is anyone else having this issue with this package?

Composer issue

Hi,

When I tried to update the package with composer just now, I got the following error:

[InvalidArgumentException]                                                                          
  Two packages (johnpbloch/wordpress-core and johnpbloch/wordpress) cannot share the same directory!

Alpha releases since 5.1

Since the 5.1 version there are a lot of alpha and beta builds marked as releases:

image

Is this something that can (and should) be controlled from this repository?

option to disable wordpress-core to overwrite/remove existing files?

Say in your composer.json, you have the following packages:

Say in your composer.json, you have the following packages:

{
    "name": "test/composer-install-order",
    "type": "project",
    "repositories": [
    { "type": "composer", "url": "https://wpackagist.org" }
    ],
    "require": {
        "php": ">=7.2",
        "composer/installers": "~1.6.0",
        "johnpbloch/wordpress": "^4.9",
        "wpackagist-plugin/better-search-replace": "*",
        "wpackagist-plugin/bugherd": "*",
        "wpackagist-plugin/disable-emojis": "*"
    },
    "extra": {
    "installer-paths": {
        "public_html/wp-content/plugins/{$name}/": ["type:wordpress-plugin"],
        "public_html/wp-content/themes/{$name}/": ["type:wordpress-theme"]
    },
    "wordpress-install-dir": "public_html"
    },
    "config": {
        "preferred-install": "dist",
        "optimize-autoloader": true,
        "sort-packages": true
    }
}

The composer.json above says you required 3 plugins: better-search-replace, bugherd, and disable-emojis

But when you hit composer install:

➜  temp1 composer install
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 7 installs, 0 updates, 0 removals
- Installing composer/installers (v1.6.0): Loading from cache
- Installing johnpbloch/wordpress-core-installer (1.0.0.2): Loading from cache
- Installing wpackagist-plugin/better-search-replace (1.3.2): Loading from cache
- Installing wpackagist-plugin/bugherd (1.0.0.0): Loading from cache
- Installing johnpbloch/wordpress-core (4.9.8): Loading from cache
- Installing johnpbloch/wordpress (4.9.8): Loading from cache
- Installing wpackagist-plugin/disable-emojis (1.7.2): Loading from cache
Writing lock file
Generating optimized autoload files
➜  temp1

You'll only get 1 plugin inside wp-content/plugins folder. The reason for this is because when you check the print above, the 2 plugins better-search-replace and bugherd where installed first BEFORE the Wordpress core files johnpbloch/wordpress. So even composer extracted those 2 plugin packages to its correct folder, the johnpbloch/wordpress has removed them because it overwrote the wp-content/plugins folder.

The only way for this to work is if I install johnpbloch/wordpress first before the plugins, but I do not know if its possible since composer install via the composer.lock content.

Hopefully there's an option to disable wordpress-core to overwrite/remove existing files?

P.S. I only opened this issue as it was recommended in StackOverflow

Regards,

Add branch alias feature

It would be great if one could specify for example ^5.3 before it is released and point it against the master branch using Composer's branch alias feature.

This way developers may use the master branch as 5.3 until the 5.3 tag has been released. When the stable version of 5.3 has been released, Composer will use that tag instead.

It is done by specifying a branch-alias field under extra in the composer.json file:

"extra": {
    "branch-alias": {
        "dev-master": "5.3-dev"
    }
}

I would gladly open a pull request adding this feature but I need some guidance. I'm guessing this could be added via the johnpbloch/build-wp repository?

Out of date assets

Some of the compress JavaScript assets in this repo are slightly different from the originals.

That causes security scanners like VaultPress to recognize them as a security thread.

The differences are minimal, but should be resolved.

wp-emoji.min.js from this repo:
https://raw.githubusercontent.com/johnpbloch/wordpress-core/master/wp-includes/js/wp-emoji.min.js

WordPress SVN:
https://core.svn.wordpress.org/tags/4.7.4/wp-includes/js/wp-emoji.min.js

WordPress Git:
https://github.com/WordPress/WordPress/blob/4.7.4/wp-includes/js/wp-emoji.min.js

Install of johnpbloch/wordpress-core failed, Could not delete wordpress/wp-content/uploads

Hi,

I'm trying to insall wordpress-core on a Platform.sh project with DDEV.

When I run ddev composer install I get the following error :

Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Package operations: 5 installs, 0 updates, 0 removals

  • Installing johnpbloch/wordpress-core (6.5.3): Extracting archive
    Install of johnpbloch/wordpress-core failed
  • Installing wpackagist-plugin/akismet (5.3.2): Extracting archive
  • Installing wpackagist-theme/twentytwentyone (1.9): Extracting archive
  • Installing wpackagist-theme/twentytwentythree (1.4): Extracting archive
  • Installing wpackagist-theme/twentytwentytwo (1.7): Extracting archive
    4/4 [============================] 100%
    In Filesystem.php line 332:

Could not delete wordpress/wp-content/uploads:

install [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--download-only] [--dev] [--no-suggest] [--no-dev] [--no-autoloader] [--no-progress] [--no-install] [--audit] [--audit-format AUDIT-FORMAT] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [...]

Composer [install] failed, composer command failed: exit status 1. stderr=

Thanks for your help.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.