Tobias Forkel

Download Magento 1 Extensions after M1 EOL

Magento 1 extensions were removed from https://marketplace.magento.com about a month ago. According to Adobe’s recent blog posts, all extensions will be removed early August from their repository, which causes a lot of frustration on developers who are still in the middle of moving towards Magento 2 or simply need the code to translate it into Magento 2 modules.

July 7, 2020 – Removal of all M1 extension listings from marketplace.magento.com. Extension will be available on repo.magento.com until 8/6/2020.
August 6, 2020 – Removal of M1 extensions from repo.magento.com

1 2	July 7, 2020 – Removal of all M1 extension listings from marketplace.magento.com. Extension will be available on repo.magento.com until 8/6/2020. August 6, 2020 – Removal of M1 extensions from repo.magento.com

Source: https://community.magento.com/t5/Magento-DevBlog/How-Extension-Developers-Can-Prepare-for-M1-End-of-Life/ba-p/446216

We encourage Magento 1 merchants to download the Magento 1 extensions they plan to keep, since Magento 1 extensions will not be available in the Magento Marketplace after July 7, 2020, and will be removed from the Magento repository after August 6, 2020.

1	We encourage Magento 1 merchants to download the Magento 1 extensions they plan to keep, since Magento 1 extensions will not be available in the Magento Marketplace after July 7, 2020, and will be removed from the Magento repository after August 6, 2020.

Source: https://magento.com/blog/magento-news/support-magento-1-software-ends-june-30-2020

So, in order to download an M1 package, you simply have to point to a specific URL. Luckily they didn’t turn off https://connect20.magentocommerce.com yet, but I believe Magento will get rid of it very soon.

https://connect20.magentocommerce.com/community/%extKey%/%version%/%extKey%-%version%.tgz

1	https://connect20.magentocommerce.com/community/%extKey%/%version%/%extKey%-%version%.tgz

I’ve spent a few minutes writing a ” quick and dirty ” PHP script that downloads the most recent version of each extension in https://connect20.magentocommerce.com/community/packages.xml including package details such as name, description, and author. For example https://connect20.magentocommerce.com/community/BankPayment/1.2.0/package.xml

<?xml version="1.0"?>
<package>
    <name>BankPayment</name>
    <version>1.2.0</version>
    <stability>stable</stability>
    <license uri="http://opensource.org/licenses/osl-3.0.php">OSL</license>
    <channel>community</channel>
    <extends/>
    <summary>Vorkasse - Bank Prepayment module which notifies the buyer to which bank account he has to transfer the money.</summary>
    <description>Bank Prepayment module which notifies the buyer to which bank account he has to transfer the money.</description>
    <notes>IBAN ready&#xD;
Allow partial capturing&#xD;
Localization improvements</notes>
    <authors><author><name>Phoenix Media GmbH</name><user>PHOENIX</user><email>bjoern.kraus@phoenix-media.eu</email></author></authors>
    <date>2017-09-05</date>
    <time>11:08:47</time>
    <contents><target name="magecommunity"><dir name="Phoenix"><dir name="BankPayment"><dir name="Block"><dir name="Adminhtml"><file name="BankAccount.php" hash="80df5881081ded22b182ac2bde3b0a3e"/>$
    <compatible/>
    <dependencies><required><php><min>5.2.0</min><max>7.0.22</max></php><extension><name>Core</name><min/><max/></extension></required></dependencies>
</package>

<?xml version="1.0"?>

<name>BankPayment</name>

<stability>stable</stability>

<channel>community</channel>

<summary>Vorkasse - Bank Prepayment module which notifies the buyer to which bank account he has to transfer the money.</summary>

<description>Bank Prepayment module which notifies the buyer to which bank account he has to transfer the money.</description>

<notes>IBAN ready

Allow partial capturing

Localization improvements</notes>

<authors><author><name>Phoenix Media GmbH</name><user>PHOENIX</user><email>bjoern.kraus@phoenix-media.eu</email></author></authors>

<contents><target name="magecommunity"><dir name="Phoenix"><dir name="BankPayment"><dir name="Block"><dir name="Adminhtml"><file name="BankAccount.php" hash="80df5881081ded22b182ac2bde3b0a3e"/>$

</package>

If you download all packages, you will end up with about 1300 extensions.

├── zoe_myzoe
│   ├── Zoe_Myzoe--package.xml
│   └── Zoe_Myzoe-.tgz
├── zoe_myzoe-1.0.0
│   ├── Zoe_Myzoe-1.0.0--package.xml
│   └── Zoe_Myzoe-1.0.0-.tgz
├── zopim_live_chat
│   ├── Zopim_Live_Chat-0.5.4-package.xml
│   └── Zopim_Live_Chat-0.5.4.tgz
└── zubibu
    ├── zubibu-1.0.0-package.xml
    └── zubibu-1.0.0.tgz

1359 directories, 2716 files

├── zoe_myzoe

│ ├── Zoe_Myzoe--package.xml

│ └── Zoe_Myzoe-.tgz

├── zoe_myzoe-1.0.0

│ ├── Zoe_Myzoe-1.0.0--package.xml

│ └── Zoe_Myzoe-1.0.0-.tgz

├── zopim_live_chat

│ ├── Zopim_Live_Chat-0.5.4-package.xml

│ └── Zopim_Live_Chat-0.5.4.tgz

└── zubibu

├── zubibu-1.0.0-package.xml

└── zubibu-1.0.0.tgz

1359 directories, 2716 files

However, it seems the packages.xml file contains a lot of extensions that are actually not available anymore, that leads to a 404.

PHP Warning:  file_get_contents(https://connect20.magentocommerce.com/community/SUMOHeavy_Coupons/1.1.0/SUMOHeavy_Coupons-1.1.0.tgz): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found
 in /var/www/extensions/index.php on line 41
PHP Warning:  file_get_contents(https://connect20.magentocommerce.com/community/SUMOHeavy_Coupons/1.1.0/package.xml): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found
 in /var/www/extensions/index.php on line 50

PHP Warning: file_get_contents(https://connect20.magentocommerce.com/community/SUMOHeavy_Coupons/1.1.0/SUMOHeavy_Coupons-1.1.0.tgz): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found

in /var/www/extensions/index.php on line 41

PHP Warning: file_get_contents(https://connect20.magentocommerce.com/community/SUMOHeavy_Coupons/1.1.0/package.xml): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found

in /var/www/extensions/index.php on line 50

Another good resource is https://packages.firegento.com or http://freegento.com/ddl-magento-extension.php to download M1 extensions.

<?php
/**
 * Connect20
 *
 * @category    Connect20
 * @author      Tobias Forkel (http://tobias.forkel.me)
 * @license     http://opensource.org/licenses/osl-3.0.php Open Software License (OSL 3.0)
 */

$packagesUrl = 'https://connect20.magentocommerce.com/community/packages.xml';
$releasesUrl = 'https://connect20.magentocommerce.com/community/%extKey%/releases.xml';
$packageUrl = 'https://connect20.magentocommerce.com/community/%extKey%/%version%/package.xml';
$downloadUrl = 'https://connect20.magentocommerce.com/community/%extKey%/%version%/%extKey%-%version%.tgz';
$packages = implode('/', [dirname(__FILE__), 'packages.xml']);

// Cache packages.xml file
if (!file_exists($packages)) {
    file_put_contents($packages, file_get_contents($packagesUrl));
}

$packages = simplexml_load_file($packages);

foreach ($packages as $data) {

    $extKey = (string)$data->n;
    $stable = (string)$data->r->s;
    $beta = (string)$data->r->b;

    $version = (!empty($stable)) ? $stable : $beta;

    if (empty($version)) {

        echo sprintf('Skipped ( %s )', $extKey);
        echo PHP_EOL;
        
        continue;
    }

    $folder = implode('/', [dirname(__FILE__), 'data', strtolower($extKey)]);

    // Create extension folder
    if (!file_exists($folder)) {
        mkdir($folder, 0777, true);
    }

    $download = str_replace(['%extKey%', '%version%'] ,[$extKey, $version], $downloadUrl);
    $downloadPath = implode('/', [$folder, basename($download)]);

    // Skip downloaded files
    if (file_exists($downloadPath)) {
        continue;
    }

    // Download the *.tgz file ( stable or beta )
    if (file_put_contents($downloadPath, file_get_contents($download))) {

        echo $download;
        echo PHP_EOL;
    }

    // Download content ( e.g description, author etc. ) from package.xml
    $package = str_replace(['%extKey%', '%version%'] ,[$extKey, $version], $packageUrl);

    if (file_put_contents(implode('/', [$folder, $extKey . '-' . $version . '-' . basename($package)]), file_get_contents($package))) {

        echo $package;
        echo PHP_EOL;
    }
}

?>

<?php

/**

* Connect20

* @category Connect20

* @author Tobias Forkel (http://tobias.forkel.me)

* @license http://opensource.org/licenses/osl-3.0.php Open Software License (OSL 3.0)

$packagesUrl = 'https://connect20.magentocommerce.com/community/packages.xml';

$releasesUrl = 'https://connect20.magentocommerce.com/community/%extKey%/releases.xml';

$packageUrl = 'https://connect20.magentocommerce.com/community/%extKey%/%version%/package.xml';

$downloadUrl = 'https://connect20.magentocommerce.com/community/%extKey%/%version%/%extKey%-%version%.tgz';

$packages = implode('/', [dirname(__FILE__), 'packages.xml']);

// Cache packages.xml file

if (!file_exists($packages)) {

file_put_contents($packages, file_get_contents($packagesUrl));

}

$packages = simplexml_load_file($packages);

foreach ($packages as $data) {

$extKey = (string)$data->n;

$stable = (string)$data->r->s;

$beta = (string)$data->r->b;

$version = (!empty($stable)) ? $stable : $beta;

if (empty($version)) {

echo sprintf('Skipped ( %s )', $extKey);

echo PHP_EOL;

continue;

}

$folder = implode('/', [dirname(__FILE__), 'data', strtolower($extKey)]);

// Create extension folder

if (!file_exists($folder)) {

mkdir($folder, 0777, true);

}

$download = str_replace(['%extKey%', '%version%'] ,[$extKey, $version], $downloadUrl);

$downloadPath = implode('/', [$folder, basename($download)]);

// Skip downloaded files

if (file_exists($downloadPath)) {

continue;

}

// Download the *.tgz file ( stable or beta )

if (file_put_contents($downloadPath, file_get_contents($download))) {

echo $download;

echo PHP_EOL;

}

// Download content ( e.g description, author etc. ) from package.xml

$package = str_replace(['%extKey%', '%version%'] ,[$extKey, $version], $packageUrl);

if (file_put_contents(implode('/', [$folder, $extKey . '-' . $version . '-' . basename($package)]), file_get_contents($package))) {

echo $package;

echo PHP_EOL;

}

Feel free to change or share the code.

Octopus – Couldn’t find a valid ICU package installed on the system

This morning I created a new ECS environment and tried to deploy a Laravel project on it.

   __|  __|  __|
   _|  (   \__ \   Amazon Linux 2 (ECS Optimized)
 ____|\___|____/

For documentation, visit http://aws.amazon.com/documentation/ecs
4 package(s) needed for security, out of 18 available

__| __| __|

_| ( \__ \ Amazon Linux 2 (ECS Optimized)

____|\___|____/

For documentation, visit http://aws.amazon.com/documentation/ecs

4 package(s) needed for security, out of 18 available

So far so good, until one of the deployment steps got stuck in Octopus because of the following error.

Process terminated. Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.

1	Process terminated. Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.

While looking for a solution, I’ve noticed that I forgot to install the package libicu on the new ECS machine that was required during the deployment process.

$ sudo yum install libicu
Loaded plugins: priorities, update-motd, upgrade-helper
Package libicu-50.2-4.amzn2.x86_64 already installed and latest version

$ sudo yum install libicu

Loaded plugins: priorities, update-motd, upgrade-helper

Package libicu-50.2-4.amzn2.x86_64 already installed and latest version

After installing the missing package, I was able to deploy again without errors.

Magento 2.3.x – Unit Tests with ScopeConfigInterface

Imagine you have a helper class that is responsible for downloading and processing JSON files. This is something you don’t want to test manually all the time. I didn’t implement many unit tests in the past, simply because it wasn’t necessary or just not scoped in a project. However, there are cases where you actually save a lot of valuable time with just a few simple unit tests.

In this article I would like to show you how to inject store configurations ( ScopeConfigInterface ) to your mocked classes which are necessary to test multiple scenarios. In the following example I am going to test a helper class and make sure the following scenarios are working as expected.

Is the module enabled in Stores > Configuration > General?
Is a URL defined?
Does the URL return a correct HTTP response?
Is the downloaded content a valid JSON string?

$this->assertEquals($this->isEnabled, $curlHelper->isEnabled());
$this->assertNotContains('No file URL set', $curlHelper->getFileUrl());
$this->assertEquals($this->statusCode, $statusCode);
$this->assertEquals($this->isJson, $isJson);

$this->assertEquals($this->isEnabled, $curlHelper->isEnabled());

$this->assertNotContains('No file URL set', $curlHelper->getFileUrl());

$this->assertEquals($this->statusCode, $statusCode);

$this->assertEquals($this->isJson, $isJson);

Here is how my module looks like. I basically created a new helper Helper\Curl.php and a unit test file Test\Unit\Helper\CurlTest.php.

.
├── Helper
│   └── Curl.php
├── README.md
├── Test
│   └── Unit
│       └── Helper
│           └── CurlTest.php
├── composer.json
├── etc
│   ├── adminhtml
│   │   └── system.xml
│   ├── config.xml
│   └── module.xml
└── registration.php

6 directories, 8 files

├── Helper

│ └── Curl.php

├── README.md

├── Test

│ └── Unit

│ └── Helper

│ └── CurlTest.php

├── composer.json

├── etc

│ ├── adminhtml

│ │ └── system.xml

│ ├── config.xml

│ └── module.xml

└── registration.php

6 directories, 8 files

I’ve added some basic methods to the helper, such as isEnabled(), getFileUrl(), getStatusCode(), isJson() and downloadFile(). Nothing fancy, just a helper that can download a file.

<?php
/**
 * Magenizr UnitTest
 *
 * @category    Magenizr
 * @package     Magenizr_UnitTest
 * @copyright   Copyright (c) 2020 Magenizr (https://www.magenizr.com)
 */

namespace Magenizr\UnitTest\Helper;

use Magento\Framework\App\Config\ScopeConfigInterface;
use Magento\Framework\App\Helper\AbstractHelper;
use Magento\Framework\App\Helper\Context;
use Magento\Store\Model\ScopeInterface;
use Exception;

/**
 * Class Filesystem
 *
 * @package Magenizr\UnitTest\Helper
 */
class Curl extends AbstractHelper
{
    const XML_PATH_GENERAL_ENABLED = 'magenizr_unittest/general/enabled';
    const XML_PATH_FILE_URL = 'magenizr_unittest/file/url';

    protected $json;
    protected $statusCode;
    protected $fileUrl;

    /**
     * Config constructor.
     *
     * @param \Magento\Framework\App\Helper\Context $context
     * @param \Magento\Framework\App\Config\ScopeConfigInterface $scopeConfig
     */
    public function __construct(
        Context $context,
        ScopeConfigInterface $scopeConfig
    ) {
        parent::__construct($context);

        $this->scopeConfig = $scopeConfig;
    }

    /**
     * Check if module is enabled
     *
     * @return bool
     */
    public function isEnabled()
    {
        return $this->scopeConfig->isSetFlag(self::XML_PATH_GENERAL_ENABLED, ScopeInterface::SCOPE_STORE);
    }

    /**
     * Return file url.
     *
     * @return mixed
     */
    public function getFileUrl()
    {
        $this->fileUrl = $this->scopeConfig->getValue(self::XML_PATH_FILE_URL, ScopeInterface::SCOPE_STORE);

        if (empty($this->fileUrl)) {

            throw new Exception(__('No file URL set in System > Configuration.'));
        }

        return $this->scopeConfig->getValue(self::XML_PATH_FILE_URL, ScopeInterface::SCOPE_STORE);
    }

    /**
     * Return HTTP status code.
     *
     * @return mixed
     */
    public function getStatusCode()
    {
        return $this->statusCode;
    }

    /**
     * Set HTTP status code.
     *
     * @param $statusCode
     * @return mixed
     */
    public function setStatusCode($statusCode)
    {
        return $this->statusCode = $statusCode;
    }

    /**
     * Check if a string is a valid json string.
     *
     * @return bool
     */
    public function isJson()
    {
        json_decode($this->json);

        return (json_last_error() == JSON_ERROR_NONE);
    }

    /**
     * Set JSON string.
     *
     * @return bool
     */
    public function setJson($json)
    {
        $this->json = $json;
    }

    /**
     * Download a specific file.
     *
     * @throws \Exception
     */
    public function downloadFile()
    {
        if (empty($this->isEnabled())) {

            throw new Exception(__('The module is not enabled in Stores > Configuration.'));
        }

        $ch = curl_init();
        curl_setopt($ch, CURLOPT_URL, $this->getFileUrl());
        curl_setopt($ch, CURLOPT_HEADER, 0);
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);

        if (curl_errno($ch)) {
            throw new Exception(curl_error($ch));
        }

        $output = curl_exec($ch);

        $statusCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);

        $this->setJson($output);
        $this->setStatusCode($statusCode);

        curl_close($ch);

        return $this;
    }
}

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

<?php

/**

* Magenizr UnitTest

* @category Magenizr

* @package Magenizr_UnitTest

namespace Magenizr\UnitTest\Helper;

use Magento\Framework\App\Config\ScopeConfigInterface;

use Magento\Framework\App\Helper\AbstractHelper;

use Magento\Framework\App\Helper\Context;

use Magento\Store\Model\ScopeInterface;

use Exception;

/**

* Class Filesystem

* @package Magenizr\UnitTest\Helper

class Curl extends AbstractHelper

{

const XML_PATH_GENERAL_ENABLED = 'magenizr_unittest/general/enabled';

const XML_PATH_FILE_URL = 'magenizr_unittest/file/url';

protected $json;

protected $statusCode;

protected $fileUrl;

/**

* Config constructor.

* @param \Magento\Framework\App\Helper\Context $context

* @param \Magento\Framework\App\Config\ScopeConfigInterface $scopeConfig

public function __construct(

Context $context,

ScopeConfigInterface $scopeConfig

) {

parent::__construct($context);

$this->scopeConfig = $scopeConfig;

}

/**

* Check if module is enabled

* @return bool

public function isEnabled()

{

return $this->scopeConfig->isSetFlag(self::XML_PATH_GENERAL_ENABLED, ScopeInterface::SCOPE_STORE);

}

/**

* Return file url.

* @return mixed

public function getFileUrl()

{

$this->fileUrl = $this->scopeConfig->getValue(self::XML_PATH_FILE_URL, ScopeInterface::SCOPE_STORE);

if (empty($this->fileUrl)) {

throw new Exception(__('No file URL set in System > Configuration.'));

}

return $this->scopeConfig->getValue(self::XML_PATH_FILE_URL, ScopeInterface::SCOPE_STORE);

}

/**

* Return HTTP status code.

* @return mixed

public function getStatusCode()

{

return $this->statusCode;

}

/**

* Set HTTP status code.

* @param $statusCode

* @return mixed

public function setStatusCode($statusCode)

{

return $this->statusCode = $statusCode;

}

/**

* Check if a string is a valid json string.

* @return bool

public function isJson()

{

json_decode($this->json);

return (json_last_error() == JSON_ERROR_NONE);

}

/**

* Set JSON string.

* @return bool

public function setJson($json)

{

$this->json = $json;

}

/**

* Download a specific file.

* @throws \Exception

public function downloadFile()

{

if (empty($this->isEnabled())) {

throw new Exception(__('The module is not enabled in Stores > Configuration.'));

}

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, $this->getFileUrl());

curl_setopt($ch, CURLOPT_HEADER, 0);

curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);

if (curl_errno($ch)) {

throw new Exception(curl_error($ch));

}

$output = curl_exec($ch);

$statusCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);

$this->setJson($output);

$this->setStatusCode($statusCode);

curl_close($ch);

return $this;

}

Usually if you want to use system variables from core_config_data you have to inject the ScopeConfigInterface in your constructor. In unit tests it is quite similar. First, you have to create a mockup of the ScopeConfigInterface.

$this->scopeConfigMock = $this->getMockBuilder(ScopeConfigInterface::class)->getMockForAbstractClass();

1	$this->scopeConfigMock = $this->getMockBuilder(ScopeConfigInterface::class)->getMockForAbstractClass();

Next, you need a mockup of the Context, but this is not always the case.

// Context Mock
$this->contextMock = $this->getMockBuilder(Context::class)->disableOriginalConstructor()->getMock();

1 2	// Context Mock $this->contextMock = $this->getMockBuilder(Context::class)->disableOriginalConstructor()->getMock();

Now you can inject these two mockups to the helper by using setConstructorArgs like in the below example.

// Curl Helper Mock
$this->curlHelperMock = $this->getMockBuilder(CurlHelper::class)->setConstructorArgs([
            'context' => $this->contextMock,
            'scopeConfig' => $this->scopeConfigMock,
        ])->getMock();

// Curl Helper Mock

$this->curlHelperMock = $this->getMockBuilder(CurlHelper::class)->setConstructorArgs([

'context' => $this->contextMock,

'scopeConfig' => $this->scopeConfigMock,

])->getMock();

Now you can define values for the scope configuration. This allows you to enable or disable your module or set random values and see how your code behaves. In the below example, I simply enable the module ( $isEnabled ) and set the file url ( $fileUrl ) to https://raw.githubusercontent.com/ljharb/json-file-plus/master/package.json which I will test with assertEquals and assertNotContains.

<?php
/**
 * Magenizr UnitTest
 *
 * @category    Magenizr
 * @package     Magenizr_UnitTest
 * @copyright   Copyright (c) 2020 Magenizr (https://www.magenizr.com)
 */

namespace Magenizr\UnitTest\Test\Unit\Helper;

use Magenizr\UnitTest\Helper\Curl as CurlHelper;
use Magento\Framework\App\Config\ScopeConfigInterface;
use Magento\Framework\App\Helper\Context;
use PHPUnit\Framework\TestCase;

class CurlTest extends TestCase
{
    protected $isEnabled = true;
    protected $statusCode = 200;
    protected $isJson = true;
    protected $fileUrl = 'https://raw.githubusercontent.com/ljharb/json-file-plus/master/package.json';

    protected $curlHelperMock;
    protected $contextMock;
    protected $scopeConfigMock;

    public function setUp()
    {
        // Core Config Data
        $this->scopeConfigMock = $this->getMockBuilder(ScopeConfigInterface::class)->getMockForAbstractClass();
        $this->scopeConfigMock->expects($this->any())->method('isSetFlag')->with(CurlHelper::XML_PATH_GENERAL_ENABLED)->willReturn($this->isEnabled);
        $this->scopeConfigMock->expects($this->any())->method('getValue')->with(CurlHelper::XML_PATH_FILE_URL)->willReturn($this->fileUrl);

        // Context Mock
        $this->contextMock = $this->getMockBuilder(Context::class)->disableOriginalConstructor()->getMock();

        // Curl Helper Mock
        $this->curlHelperMock = $this->getMockBuilder(CurlHelper::class)->setConstructorArgs([
            'context' => $this->contextMock,
            'scopeConfig' => $this->scopeConfigMock,
        ])->getMock();
    }

    /**
     * Test if enabled flag is defined in the table core_config_data.
     */
    public function testCurlDownloadIfModuleIsEnabled()
    {
        // Pass content and scopeConfig to CurlHelper
        $curlHelper = new CurlHelper($this->contextMock, $this->scopeConfigMock);

        $file = $curlHelper->downloadFile();

        $statusCode = $file->getStatusCode();
        $isJson = $file->isJson();

        $this->assertEquals($this->isEnabled, $curlHelper->isEnabled());
        $this->assertNotContains('No file URL set', $curlHelper->getFileUrl());
        $this->assertEquals($this->statusCode, $statusCode);
        $this->assertEquals($this->isJson, $isJson);
    }
}

<?php

/**

* Magenizr UnitTest

* @category Magenizr

* @package Magenizr_UnitTest

namespace Magenizr\UnitTest\Test\Unit\Helper;

use Magenizr\UnitTest\Helper\Curl as CurlHelper;

use Magento\Framework\App\Config\ScopeConfigInterface;

use Magento\Framework\App\Helper\Context;

use PHPUnit\Framework\TestCase;

class CurlTest extends TestCase

{

protected $isEnabled = true;

protected $statusCode = 200;

protected $isJson = true;

protected $fileUrl = 'https://raw.githubusercontent.com/ljharb/json-file-plus/master/package.json';

protected $curlHelperMock;

protected $contextMock;

protected $scopeConfigMock;

public function setUp()

{

// Core Config Data

$this->scopeConfigMock = $this->getMockBuilder(ScopeConfigInterface::class)->getMockForAbstractClass();

$this->scopeConfigMock->expects($this->any())->method('isSetFlag')->with(CurlHelper::XML_PATH_GENERAL_ENABLED)->willReturn($this->isEnabled);

$this->scopeConfigMock->expects($this->any())->method('getValue')->with(CurlHelper::XML_PATH_FILE_URL)->willReturn($this->fileUrl);

// Context Mock

$this->contextMock = $this->getMockBuilder(Context::class)->disableOriginalConstructor()->getMock();

// Curl Helper Mock

$this->curlHelperMock = $this->getMockBuilder(CurlHelper::class)->setConstructorArgs([

'context' => $this->contextMock,

'scopeConfig' => $this->scopeConfigMock,

])->getMock();

}

/**

* Test if enabled flag is defined in the table core_config_data.

public function testCurlDownloadIfModuleIsEnabled()

{

// Pass content and scopeConfig to CurlHelper

$curlHelper = new CurlHelper($this->contextMock, $this->scopeConfigMock);

$file = $curlHelper->downloadFile();

$statusCode = $file->getStatusCode();

$isJson = $file->isJson();

$this->assertEquals($this->isEnabled, $curlHelper->isEnabled());

$this->assertNotContains('No file URL set', $curlHelper->getFileUrl());

$this->assertEquals($this->statusCode, $statusCode);

$this->assertEquals($this->isJson, $isJson);

}

I also define an expected value for the CURL httpStatus and an expected return value of isJson(). Okay, lets run the test and see what happens.

bash-4.4# php vendor/phpunit/phpunit/phpunit -c dev/tests/unit/phpunit.xml.dist app/code/Magenizr/UnitTest/Test
PHPUnit 6.5.14 by Sebastian Bergmann and contributors.

.                                                                   1 / 1 (100%)

Time: 1.13 seconds, Memory: 8.00MB

OK (1 test, 4 assertions)

bash-4.4# php vendor/phpunit/phpunit/phpunit -c dev/tests/unit/phpunit.xml.dist app/code/Magenizr/UnitTest/Test

PHPUnit 6.5.14 by Sebastian Bergmann and contributors.

. 1 / 1 (100%)

Time: 1.13 seconds, Memory: 8.00MB

OK (1 test, 4 assertions)

All assertions within the test have succeeded. Let’s see what happens when I change the URL slightly. It should return a 404.

protected $fileUrl = 'https://raw.githubusercontent.com/ljharb/master/package.json';

1	protected $fileUrl = 'https://raw.githubusercontent.com/ljharb/master/package.json';

Yes, the test fails because I’ve received a status code 404 instead of 200.

$this->assertEquals($this->statusCode, $statusCode);

1	$this->assertEquals($this->statusCode, $statusCode);

There was 1 failure:

1) Magenizr\UnitTest\Test\Unit\Helper\CurlTest::testCurlDownloadIfModuleIsEnabled
Failed asserting that 404 matches expected 200.

/var/www/src/app/code/Magenizr/UnitTest/Test/Unit/Helper/CurlTest.php:60

FAILURES!
Tests: 1, Assertions: 3, Failures: 1.

There was 1 failure:

1) Magenizr\UnitTest\Test\Unit\Helper\CurlTest::testCurlDownloadIfModuleIsEnabled

Failed asserting that 404 matches expected 200.

/var/www/src/app/code/Magenizr/UnitTest/Test/Unit/Helper/CurlTest.php:60

FAILURES!

Tests: 1, Assertions: 3, Failures: 1.

That’s it. If you have questions or need help, please let me know in the comments.

Octopus – Basic ” Staging First ” Lifecycle

In this post, I am going to show you how to prevent a release from being deployed directly to production if it hasn’t been deployed to staging. Octopus has a great feature called ( Lifecycles ) that allows you to create advanced deployment workflows for any type of project.

This way you are able to force your team to follow a strict deployment process that will definitely improve your test routine and the way how you deploy code changes. No more untested code changes on production!

Okay, let’s start. Here is how you can create a custom Lifecycle.

From the Lifecycle page, click on the ADD LIFECYCLE button.
Give the Lifecycle a name and add a description. For example ” Project X “.
You can leave the Retention Policy unchanged ( Keep all ) for now.

Scroll down and continue with the next tab.

Click ADD PHASE, to explicitly define the phases of the lifecycle.
Give the phase a name. For example ” Staging ” because I want you deploy and review your changes on staging first.
Click ADD ENVIRONMENT to define which environments can be deployed to during this phase of the lifecycle. Choose your staging environment from the dropdown list.

If you haven’t add an environment yet, you must create at least two ( staging, production ). Learn more about Environments.

Scroll up again and save the new Lifecycle. Now go back to your project and click the link Process in the left sidebar. Next, hit the button Change on the right-hand side and select the Lifecycle that you’ve just created and save the changes.

After that, try to deploy a new release. You will see that there is no option to deploy on production. Just must deploy your code successfully to your staging environment first in order to be able to push changes to production.

This is just one of many examples of how you can improve your deployment routine with Octopus.

Octopus – How to fix ” Missing deployment buttons “

I saw a few comments on Stackoverflow where people ask how to setup or re-enable deployment buttons for staging or production. The answer is not quite straightforward, because you have to review a few things. Here is a quick checklist that may help you to identify the cause of missing deployment buttons.

1. Process

Make sure you have selected the right Lifecycle in Projects > Your Client > Deployments > Process.

2. Lifecycles

If you believe one Phase / Environment missing, go to Library > Lifecycles and try to add the missing environment in the Phases section.

3. Environments

In order to be able to add a new phase, make sure all required environments are listed in Infrastructure > Environments.

Learn more about Environments.

October CMS – Execute Console Commands Sequentially

In this tutorial, I am going to show you how to execute long running PHP processes sequentially in October CMS from anywhere of your code.

First, you must define a default driver, which is pretty much a handler for managing how to run a queued job, identifying whether the jobs succeeded or failed, and trying the job again. In October CMS, the driver settings are located in the file in ./config/queue.php.

<?php

return [

    /*
    |-------------------------------------------------------------------------
    | Default Queue Driver
    |-------------------------------------------------------------------------
    |
    | The Laravel queue API supports a variety of back-ends via an unified
    | API, giving you convenient access to each back-end using the same
    | syntax for each one. Here you may set the default queue driver.
    |
    | Supported: "null", "sync", "database", "beanstalkd",
    |            "sqs", "iron", "redis"
    |
    */

    'default' => 'database',

<?php

return [

|-------------------------------------------------------------------------

| Default Queue Driver

|-------------------------------------------------------------------------

| The Laravel queue API supports a variety of back-ends via an unified

| API, giving you convenient access to each back-end using the same

| syntax for each one. Here you may set the default queue driver.

| Supported: "null", "sync", "database", "beanstalkd",

| "sqs", "iron", "redis"

'default' => 'database',

If you are new to this, I recommend to start with the database driver. This driver is good enough to execute your console commands synchronously in the background without slowing down your PHP calls. As a next step, you have to register a custom console command in your Plugin.php file. For example company.pluginname.

/**
 * Register console commands
 */
public function register() {

    $this->registerConsoleCommand('company.pluginname', 'Company\Pluginname\Console\Test');
}

/**

* Register console commands

public function register() {

$this->registerConsoleCommand('company.pluginname', 'Company\Pluginname\Console\Test');

}

For test purposes, I created a console command company.pluginname which will execute the method backupList.

bash-4.4# php artisan company:pluginname 123 --customer=list
Parameter ID 123 passed.

1 2	bash-4.4# php artisan company:pluginname 123 --customer=list Parameter ID 123 passed.

<?php namespace Company\Pluginname\Console;

use Illuminate\Console\Command;
use Symfony\Component\Console\Input\InputOption;
use Symfony\Component\Console\Input\InputArgument;

class Test extends Command
{
    /**
     * @var string The console command name.
     */
    protected $name = 'company:pluginname';

    /**
     * @var int
     */
    protected $customerId = 0;

    /**
     * @var string
     */
    protected $description = 'No description provided yet...';

    /**
     *
     */
    public function backupList()
    {
        $this->output->writeln(sprintf('Parameter ID %s passed.', $this->customerId));
        
        // Call API
        // Compress response and save on disk
        // Write information into Log table
    }

    /**
     * Execute the console command.
     * @return void
     */
    public function handle()
    {
        $this->customerId = $this->argument('customerId');

        $option = $this->option('customer');

        $args = explode(',', $option);

        if (in_array('list', $args)) {
            $this->backupList();
        }
    }

    /**
     * Get the console command arguments.
     * @return array
     */
    protected function getArguments()
    {
        return [
            ['customerId', InputArgument::REQUIRED, '(Required) Customer Id']
        ];
    }

    /**
     * Get the console command options.
     * @return array
     */
    protected function getOptions()
    {
        return [
            ['customer', null, InputOption::VALUE_REQUIRED, 'An example option.', null],
            ['queue', null, InputOption::VALUE_OPTIONAL, 'An example option.', null]
        ];
    }
}

<?php namespace Company\Pluginname\Console;

use Illuminate\Console\Command;

use Symfony\Component\Console\Input\InputOption;

use Symfony\Component\Console\Input\InputArgument;

class Test extends Command

{

/**

* @var string The console command name.

protected $name = 'company:pluginname';

/**

* @var int

protected $customerId = 0;

/**

* @var string

protected $description = 'No description provided yet...';

/**

public function backupList()

{

$this->output->writeln(sprintf('Parameter ID %s passed.', $this->customerId));

// Call API

// Compress response and save on disk

// Write information into Log table

}

/**

* Execute the console command.

* @return void

public function handle()

{

$this->customerId = $this->argument('customerId');

$option = $this->option('customer');

$args = explode(',', $option);

if (in_array('list', $args)) {

$this->backupList();

}

/**

* Get the console command arguments.

* @return array

protected function getArguments()

{

return [

['customerId', InputArgument::REQUIRED, '(Required) Customer Id']

];

}

/**

* Get the console command options.

* @return array

protected function getOptions()

{

return [

['customer', null, InputOption::VALUE_REQUIRED, 'An example option.', null],

['queue', null, InputOption::VALUE_OPTIONAL, 'An example option.', null]

];

}

Let’s assume you have a front-end controller http://yourpage.dev/customer/list that calls an API, creates a list and saves it on disk. Executing all these steps can be time-consuming and simply slow down your controller. Instead, you can run such processes in the background with Artisan::queue.

<?php namespace Company\Pluginname\Controllers;

use Illuminate\Routing\Controller;
use Illuminate\Support\Facades\Artisan;

class Customer extends Controller
{
    public function list($id)
    {
        Artisan::queue('company:pluginname', [
            'customerId' => 123,
            '--customer' => 'list',
            '--queue' => 'default'
        ]);
    }
}

<?php namespace Company\Pluginname\Controllers;

use Illuminate\Routing\Controller;

use Illuminate\Support\Facades\Artisan;

class Customer extends Controller

{

public function list($id)

{

Artisan::queue('company:pluginname', [

'customerId' => 123,

'--customer' => 'list',

'--queue' => 'default'

]);

}

As soon as you hit the controller, artisan will queue a new record in the table jobs and wait until a queue worker executes the job. You just have to make sure that a Queue Worker is running in the background, otherwise jobs won’t get executed.

bash-4.4# php artisan queue:work --tries=3
[2020-04-14 04:11:52] Processing: Illuminate\Foundation\Console\QueuedCommand
[2020-04-14 04:11:54] Processed:  Illuminate\Foundation\Console\QueuedCommand
[2020-04-14 04:11:54] Processing: Illuminate\Foundation\Console\QueuedCommand
[2020-04-14 04:11:55] Processed:  Illuminate\Foundation\Console\QueuedCommand
[2020-04-14 04:11:55] Processing: Illuminate\Foundation\Console\QueuedCommand
[2020-04-14 04:12:14] Processed:  Illuminate\Foundation\Console\QueuedCommand

bash-4.4# php artisan queue:work --tries=3

[2020-04-14 04:11:52] Processing: Illuminate\Foundation\Console\QueuedCommand

[2020-04-14 04:11:54] Processed: Illuminate\Foundation\Console\QueuedCommand

[2020-04-14 04:11:54] Processing: Illuminate\Foundation\Console\QueuedCommand

[2020-04-14 04:11:55] Processed: Illuminate\Foundation\Console\QueuedCommand

[2020-04-14 04:11:55] Processing: Illuminate\Foundation\Console\QueuedCommand

[2020-04-14 04:12:14] Processed: Illuminate\Foundation\Console\QueuedCommand

I recommend to start a queue worker with Supervisor which is well explained on https://medium.com/@rohit_shirke/configuring-supervisor-for-laravel-queues-81e555e550c6

October CMS – How To Use Models In Custom Components

Components in October CMS can be used for custom output, such as JavaScript snippets, dynamic content from a web service or models. Components can also handle AJAX requests or other incoming data. In this tutorial, I will simply show you how to register a new component and output a list with records from the users table.

First of all, you have to register a new component in your Plugin.php file. For example, users.

<?php namespace Playground\Sandbox;

use System\Classes\PluginBase;
use System\Classes\SettingsManager;

class Plugin extends PluginBase
{

    /**
     * Register Component
     *
     * @return array
     */
    public function registerComponents()
    {
        return [
            'Playground\Sandbox\Components\Users' => 'users'
        ];
    }
}

<?php namespace Playground\Sandbox;

use System\Classes\PluginBase;

use System\Classes\SettingsManager;

class Plugin extends PluginBase

{

/**

* Register Component

* @return array

public function registerComponents()

{

return [

'Playground\Sandbox\Components\Users' => 'users'

];

}

Create the following structure within the components folder which must contain the file Users.php and users/default.htm.

.
└── playground
    └── sandbox
        ├── Plugin.php
        ├── components
        │   ├── Users.php
        │   └── users
        │       └── default.htm

└── playground

└── sandbox

├── Plugin.php

├── components

│ ├── Users.php

│ └── users

│ └── default.htm

Below you will find the content for the default.htm file which will basically output a list of all users.

<div class="list-users">
    {% for person in __SELF__.getPeople %}
        {{ person.username }} {{ person.email }}
    {% endfor %}
</div>

{% for person in __SELF__.getPeople %}

{% endfor %}

</div>

The Users.php file only requires a method getPeople and a reference to the new model, called UsersModel.

<?php namespace Playground\Sandbox\Components;

use Cms\Classes\ComponentBase;
use Playground\Sandbox\Models\Users as UsersModel;

class Users extends ComponentBase
{
    /**
     * Define component details.
     *
     * @return array
     */
    public function componentDetails()
    {
        return [
            'name' => 'playground.sandbox::lang.plugin.name',
            'description' => 'playground.sandbox::lang.plugin.description'
        ];
    }

    public function getPeople()
    {
        return (new UsersModel())->getPeople();
    }
}

<?php namespace Playground\Sandbox\Components;

use Cms\Classes\ComponentBase;

use Playground\Sandbox\Models\Users as UsersModel;

class Users extends ComponentBase

{

/**

* Define component details.

* @return array

public function componentDetails()

{

return [

'name' => 'playground.sandbox::lang.plugin.name',

'description' => 'playground.sandbox::lang.plugin.description'

];

}

public function getPeople()

{

return (new UsersModel())->getPeople();

}

In order to access a model, you must create one within the models folder.

├── models
│   └── Users.php

1 2	├── models │ └── Users.php

For test purposes, I simply return all records from the users table.

<?php namespace Playground\Sandbox\Models;

use Model;

/**
 * Class Users
 * @package Playground\Sandbox\Models
 */
class Users extends Model
{
    /**
     * @var string The database table used by the model.
     */
    public $table = 'users';

    /**
     * Return all records from users table.
     *
     * @return mixed
     */
    public function getPeople()
    {
        return self::all();
    }
}

<?php namespace Playground\Sandbox\Models;

use Model;

/**

* Class Users

* @package Playground\Sandbox\Models

class Users extends Model

{

/**

* @var string The database table used by the model.

public $table = 'users';

/**

* Return all records from users table.

* @return mixed

public function getPeople()

{

return self::all();

}

Now you can use the new component anywhere in your template files. I recommend to use [users] in your parent template file, because it will allow you to use the component in your child templates.

description = "Default layout"

[users]
==
<!doctype html>
<html lang="en">
<head>
</head>
<body>

<section id="body">
    <div class="wrapper">
        {% component 'users' %}
    </div>
</section>

{% scripts %}
{% framework extras %}
</body>

</html>

description = "Default layout"

[users]

<!doctype html>

<head>

</head>

<body>

{% component 'users' %}

</div>

</section>

{% scripts %}

{% framework extras %}

</body>

</html>

After a page reload, should you immediately see the list.

For more information, check out https://octobercms.com/docs/cms/components. The source code of this tutorial can be found on https://github.com/tobias-forkel/october-cms-playground

Octopus – How to fix ” There must be at least one enabled healthy machine to deploy “

I am pretty new to Octopus and just started implementing a deployment process for a new PHP project. After creating a new machine in Infrastructure > Deployment Targets I went back to Projects > My Project > Create Release and tried to start a deployment to our dev environment which caused the following error.

There must be at least one enabled healthy machine to deploy to in the environment, or the Project Deployment Target settings must be set to allow deployments to empty environments. Once you have corrected these problems you can try again. If the problem is related to a variable you will need to update the variables for this release or recreate the release for the changes to take effect. If the problem is related to the deployment process you will need to create a new release for the changes to take effect.

There must be at least one enabled healthy machine to deploy to in the environment, or the Project Deployment Target settings must be set to allow deployments to empty environments. Once you have corrected these problems you can try again. If the problem is related to a variable you will need to update the variables for this release or recreate the release for the changes to take effect. If the problem is related to the deployment process you will need to create a new release for the changes to take effect.

As you can see in the below screenshot, I tried to deploy a new release to the target Development.

The error message was strange because the target status of my Deployment Target was flagged as healthy. After comparing the settings I noticed that the environment Development in my deployment target settings was simply missing.

After adding the target Development to the list of Environments, I was able to proceed with the above deployment.

October CMS – Add Menu Item And Store Backend Settings

At some point you probably want to make your custom plugin for October CMS configurable and allow backend users to make changes within the plugin space. October CMS has a simple and intuitive backend navigation, which you can easily extend in no-time. Let’s assume you have a custom plugin that calls an external API. Here is how you can store API credentials by using the Settings Manager.

First of all, you must register the settings in your Plugin.php file.

<?php namespace Playground\Sandbox;

use System\Classes\PluginBase;
use System\Classes\SettingsManager;

class Plugin extends PluginBase
{

    /**
     * Register Settings
     *
     * @return array
     */
    public function registerSettings()
    {
        return [
            'settings' => [
                'label'       => 'playground.sandbox::lang.settings.label',
                'description' => 'playground.sandbox::lang.settings.description',
                'icon'        => 'icon-flask',
                'category'    => SettingsManager::CATEGORY_SYSTEM,
                'class'       => 'Playground\Sandbox\Models\Settings',
                'keywords'    => 'playground sandbox other keyswords',
            ]
        ];
    }
}

<?php namespace Playground\Sandbox;

use System\Classes\PluginBase;

use System\Classes\SettingsManager;

class Plugin extends PluginBase

{

/**

* Register Settings

* @return array

public function registerSettings()

{

return [

'settings' => [

'label' => 'playground.sandbox::lang.settings.label',

'description' => 'playground.sandbox::lang.settings.description',

'icon' => 'icon-flask',

'category' => SettingsManager::CATEGORY_SYSTEM,

'class' => 'Playground\Sandbox\Models\Settings',

'keywords' => 'playground sandbox other keyswords',

]

];

}

After that you must create a Settings.php file with the following content inside your models folder.

<?php namespace Playground\Sandbox\Models;

use Model;

/**
 * Class Settings
 * @package Playground\Sandbox\Models
 */
class Settings extends Model
{
    /**
     * @var array
     */
    public $implement = ['System.Behaviors.SettingsModel'];

    /**
     * @var string
     */
    public $settingsCode = 'playground_sandbox_settings';

    /**
     * @var string
     */
    public $settingsFields = 'fields.yaml';

    // Set defaults
    public function initSettingsData()
    {
        $this->enabled = 0;
        $this->api_key = '';
    }
}

<?php namespace Playground\Sandbox\Models;

use Model;

/**

* Class Settings

* @package Playground\Sandbox\Models

class Settings extends Model

{

/**

* @var array

public $implement = ['System.Behaviors.SettingsModel'];

/**

* @var string

public $settingsCode = 'playground_sandbox_settings';

/**

* @var string

public $settingsFields = 'fields.yaml';

// Set defaults

public function initSettingsData()

{

$this->enabled = 0;

$this->api_key = '';

}

If you define default values inside the method initSettingsData, make sure the above fields match with the definitions inside the fields.yaml file.

tabs:
    fields:
        enabled:
            label: playground.sandbox::lang.settings.enabled
            comment: playground.sandbox::lang.settings.enabled_comment
            tab: playground.sandbox::lang.settings.tab_default
            type: checkbox
        api_key:
            label: playground.sandbox::lang.settings.api_key
            comment: playground.sandbox::lang.settings.api_key_comment
            tab: playground.sandbox::lang.settings.tab_default
            type: text

tabs:

fields:

enabled:

label: playground.sandbox::lang.settings.enabled

comment: playground.sandbox::lang.settings.enabled_comment

tab: playground.sandbox::lang.settings.tab_default

type: checkbox

api_key:

label: playground.sandbox::lang.settings.api_key

comment: playground.sandbox::lang.settings.api_key_comment

tab: playground.sandbox::lang.settings.tab_default

type: text

Once the fields.yaml file is created, you should see a new form within the new tab.

Now you can access the settings values within your controller, console or component by implementing the following model.

use Playground\Sandbox\Models\Settings;

1	use Playground\Sandbox\Models\Settings;

For test purposes, I created a new controller and implemented the above model to get access to the API key.

<?php namespace Playground\Sandbox\Controllers;

use Illuminate\Routing\Controller;
use Playground\Sandbox\Models\Settings;

class Swing extends Controller
{
    /**
     * @var Plugin settings
     */
    protected $settings;

    /**
     * Sandbox constructor.
     */
    public function __construct()
    {
        $this->settings = Settings::instance();
    }

    /**
     * @param $params
     */
    public function index($params)
    {
        try {

            $enabled = $this->settings->enabled;

            if ($enabled) {
                
                // Use settings values
                var_dump($this->settings->api_key);
            }
        }

        catch (\Exception $ex) {
            $ex->getMessage();
        }
    }
}

<?php namespace Playground\Sandbox\Controllers;

use Illuminate\Routing\Controller;

use Playground\Sandbox\Models\Settings;

class Swing extends Controller

{

/**

* @var Plugin settings

protected $settings;

/**

* Sandbox constructor.

public function __construct()

{

$this->settings = Settings::instance();

}

/**

* @param $params

public function index($params)

{

try {

$enabled = $this->settings->enabled;

if ($enabled) {

// Use settings values

var_dump($this->settings->api_key);

}

catch (\Exception $ex) {

$ex->getMessage();

}

Here you go.

The entire source code can be found on https://github.com/tobias-forkel/october-cms-playground.

Laravel – Carbon and Queries

Carbon is probably the most effective way to handle DateTime strings flawlessly and implement PHP code that everybody can easily extend or debug.

echo Carbon::now()->subMinutes(2)->diffForHumans(); // '2 minutes ago'

1	echo Carbon::now()->subMinutes(2)->diffForHumans(); // '2 minutes ago'

In the following example, I would like to demonstrate how you can filter a collection in Laravel by using Carbon. As you can see, the below example will simply return all People who have registered in the past two weeks.

$from = Carbon::now()->subWeeks(2);
$to = Carbon::now();

$people = (new People())
    ->whereBetween('registered_at', [$from, $to])
    ->orderBy('registered_at', 'desc')
    ->get();

$from = Carbon::now()->subWeeks(2);

$to = Carbon::now();

$people = (new People())

->whereBetween('registered_at', [$from, $to])

->orderBy('registered_at', 'desc')

->get();

The method subWeeks() will do all the work for you and return a valid DateTime string from 14 days ago which can be used for the whereBetween query method. If you prefer using days, you can simply use subDays() instead.

One possible use case could be a front-end controller that handles AJAX requests.

<?php namespace Your\Plugin\Controllers\Frontend;

use Illuminate\Routing\Controller;
use Your\Plugin\Models\People;
use Response;
use Carbon\Carbon;

class Work extends Controller
{

    public function index($weeks)
    {
        try {

            $from = Carbon::now()->subWeeks($weeks);
            $to = Carbon::now();

            $people = (new People())
                ->whereBetween('registered_at', [$from, $to])
                ->orderBy('registered_at', 'desc')
                ->get()
                ->toArray();

            return Response::json($people, 200)->send();
        }

        catch (\Exception $ex) {
            $ex->getMessage();
        }
    }
}

<?php namespace Your\Plugin\Controllers\Frontend;

use Illuminate\Routing\Controller;

use Your\Plugin\Models\People;

use Response;

use Carbon\Carbon;

class Work extends Controller

{

public function index($weeks)

{

try {

$from = Carbon::now()->subWeeks($weeks);

$to = Carbon::now();

$people = (new People())

->whereBetween('registered_at', [$from, $to])

->orderBy('registered_at', 'desc')

->get()

->toArray();

return Response::json($people, 200)->send();

}

catch (\Exception $ex) {

$ex->getMessage();

}