To counter this, I use LOAD DATA directly via the command line. I logged in with the command line using mysql -u root and selected the database. I ran:

mysql> LOAD DATA INFILE '/data.csv' INTO TABLE data;

I got an error:

ERROR 1290 (HY000): The MySQL server is running with the --secure-file-priv option so it cannot execute this statement

Then I ran it with LOCAL and series of errors & solutions I tried.

mysql> LOAD DATA LOCAL INFILE '/data.csv' INTO TABLE data;
ERROR 3948 (42000): Loading local data is disabled; this must be enabled on both the client and server sides
mysql> set global local_infile=true;
mysql> LOAD DATA LOCAL INFILE '/data.csv' INTO TABLE data;
ERROR 2068 (HY000): LOAD DATA LOCAL INFILE file request rejected due to restrictions on access.

This meant that I had to change how I logged in to the shell.

mysql -u root  --local_infile=1

Then the data import worked successfully (and FAST!)

mysql> LOAD DATA LOCAL INFILE '/data.csv' INTO TABLE data;
Query OK, 1767 rows affected, 8835 warnings (0.07 sec)

Now the CSV format was not being considered, so I had to split up the columns.

LOAD DATA LOCAL INFILE '/data.csv' INTO TABLE data FIELDS TERMINATED BY ',' ENCLOSED BY '"' LINES TERMINATED BY '\r\n' IGNORE 1 LINES;

2023-04-07 10:48:49 [07-Apr-2023 08:48:49] NOTICE: Failed implicitly binding to ::, retrying with 0.0.0.0
2023-04-07 10:48:49 [07-Apr-2023 08:48:49] NOTICE: Failed implicitly binding to ::, retrying with 0.0.0.0
2023-04-07 10:48:49 [07-Apr-2023 08:48:49] ERROR: unable to bind listening socket for address '9000': Address already in use (98)
2023-04-07 10:48:49 [07-Apr-2023 08:48:49] ERROR: unable to bind listening socket for address '9000': Address already in use (98)
2023-04-07 10:48:49 [07-Apr-2023 08:48:49] ERROR: FPM initialization failed
2023-04-07 10:48:49 [07-Apr-2023 08:48:49] ERROR: FPM initialization failed

To identify the cause, I ran a command on Powershell to find which process is running on this port.

 Get-Process -Id (Get-NetTCPConnection -LocalPort 9000).OwningProcess

Which gave me this result

Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName
-------  ------    -----      -----     ------     --  -- -----------
   1926     168  3334352    1776924     821.08  14252   1 phpstorm64

On looking up online, turns out PHPStorm runs its own debugging server on port 9000 by default. I went to settings, searched for built in server and changed the port number. This issue could have been caused by the latest upgrade to PHPStorm 2023.1.

To do this, you will need to install Laravel pint:

composer require laravel/pint --dev

Then, go to your root directory, find .git/hooks and create a copy of the pre-commit.sample hook file. I named mine as pre-commit and made it executable using chmod +x pre-commit

Open that pre-commit file on your editor and paste this:

#!/bin/sh
files=$(git diff --cached --name-only --diff-filter=ACM -- '*.php');
vendor/bin/pint $files

This fetches the list of files that have been Added, Copied or Modified (ACM in diff-filter) and passes that as the argument for pint to format only those files.

If you want to include files that were renamed, you can use the additional flag R in diff-filter. Additionally, if you want to disable the output of pint, you can pass in the flag -q for quiet output like this:

vendor/bin/pint $files -q

When you create a new Controller using php artisan make:controller IndexController , you get this default stub.

<?php
 
namespace App\Http\Controllers;
 
use Illuminate\Http\RedirectResponse;
use Illuminate\Http\Request;
use Illuminate\Http\Response;
 
class IndexController extends Controller
{
    /**
     * Display a listing of the resource.
     */
    public function index(): Response
    {
        //
    }
 
    /**
     * Display the specified resource.
     */
    public function show(): Response
    {
        //
    }
 
    // ...
 
}

 In this case, if you try to return a view inside of either index or show methods using the view helper, you will see an error.

TypeError:

Return value is expected to be Illuminate\Http\Response, Illuminate\View\View returned

The fix is to update the return type of the method from Response to View from the Illuminate\View\View namespace.

use Illuminate\View\View;
public function index(): View
    {
        //
    }
    

Alternatively, you could also use response()->view(...), Response::view  or update the default return type to Response | View

To get started:

• Make sure you have a bard field in your statamic blueprint
• Install Bard Mutator from the link above
• Add the following snippet that lets you perform advanced operations to a service provider. Either src/Providers/AppServiceProvider or a separate Service Provider will do.
  

$this->app->bind(
    \Tiptap\Editor::class,
    \JackSleight\StatamicBardMutator\Editor::class
);

This is the content I have in my bard field (repeated multiple times) so we can see how to replace just once and all occurrences if we want to.

To replace only once in each paragraph:

Mutator::data('paragraph', function ($data, $meta){
            if (empty($data->content)) {
                return;
            }

            foreach ($data->content as $i => $node) {
                if (isset($node->text)) {
                    $regex = '/^(.*?)\bLorem Ipsum\b(.*)$/';
                    if (!preg_match($regex, $node->text, $match)) {
                        continue;
                    }

                    [, $before, $after] = $match;
                    array_splice($data->content, $i, 1, [
                        (object)['type' => 'text', 'text' => $before],
                        (object)['type' => 'text', 'text' => 'LOREM IPSUM'],
                        (object)['type' => 'text', 'text' => $after],
                    ]);
                    break;
                }
                
            }
});

To replace only once in the entire article:

I used $meta which gives us access to the root tag. Bard data mutator for paragraph is triggered once for each paragraph in the bard field. So you need access to $meta['root'] which is great to store shared variables.

 Mutator::data('paragraph', function ($data, $meta){
            if (empty($data->content)) {
                return;
            }

            if (isset($meta['root']->replaced) && $meta['root']->replaced){
                return;
            }

            foreach ($data->content as $i => $node) {
                if (isset($node->text)) {
                    $regex = '/^(.*?)\bLorem Ipsum\b(.*)$/';
                    if (!preg_match($regex, $node->text, $match)) {
                        continue;
                    }

                    [, $before, $after] = $match;
                    array_splice($data->content, $i, 1, [
                        (object)['type' => 'text', 'text' => $before],
                        (object)['type' => 'text', 'text' => 'DUMMY TEXT'],
                        (object)['type' => 'text', 'text' => $after],
                    ]);
                    $meta['root']->replaced = true;
                    break;
                }
                
            }
});

Read how to format Statamic code automatically with Laravel Pint

 Disk [assets] does not have a configured driver.

  at vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemManager.php:137
    133▕     {
    134▕         $config ??= $this->getConfig($name);
    135▕
    136▕         if (empty($config['driver'])) {
  ➜ 137▕             throw new InvalidArgumentException("Disk [{$name}] does not have a configured driver.");
    138▕         }
    139▕
    140▕         $name = $config['driver'];
    141▕

All I had to do was go to config/filesystems.php and add this new block under disks

'assets' => [
            'driver' => 'local',
            'root' => public_path('assets'),
            'url' => '/assets',
            'visibility' => 'public',
        ],

If you use a driver other than local, take a look at the documentation on how to configure it.

When I deploy changes to content, I added a new Laravel command as part of the deployment flow. Important thing to note is that the Purge by single-file (by URL) allows only 30 entries at a time.

With statamic, I just grab the URLs from the Entry repository for a single collection. You could filter more, perhaps grab only records that have been updated in the last day, or since the last deployment.

This is what I have in the handle method. For this, you need two things:

• Zone ID (it's on your site page in Cloudflare portal)
• API Key (Generate one here with permissions for clearing / purging cache in a zone)
  

// use config() to grab it from your environment
$apiKey = ''; 
$zoneId = '';

$all = Entry::query()
            ->where('collection', 'collection_name')
            ->where('published', true)
            ->get();

        foreach ($all->chunk(30) as $entries){
            $files = [];
            /** @var Entry $entry */
            foreach ($entries as $entry){
                $files[] = url($entry->uri);
            }

            $urls = [
                'files' => $files
            ];

            $http = Http::withBody(json_encode($urls),'application/json')
                ->withToken($apiKey)
                ->post('https://api.cloudflare.com/client/v4/zones/' . $zoneId . '/purge_cache');

            $this->info('Submitted to Cloudflare with status: ' . $http->status());

            if (!$http->ok()){
                dump($http->body());
            }

        }

Elastic\Elasticsearch\Exception\ClientResponseException
401 Unauthorized: 
{
	"error": {
		"root_cause": [
			{
				"type": "security_exception",
				"reason": "missing authentication credentials for REST request [/index/_search]",
				"header": { "WWW-Authenticate": ["Basic realm=\"security\" charset=\"UTF-8\"", "ApiKey"] }
			}
		],
		"type": "security_exception",
		"reason": "missing authentication credentials for REST request [/index/_search]",
		"header": { "WWW-Authenticate": ["Basic realm=\"security\" charset=\"UTF-8\"", "ApiKey"] }
	},
	"status": 401
}

I found two ways to solve this, I could setup either one of these:

• basic authentication
• API Key

Basic Authentication

Use this guide to generate an username / password combination, default username is elastic

Using Elastic Search client:

$client = ClientBuilder::create()
->setBasicAuthentication('<username>', '<password>')
->build();

If you use configuration files, you can set up the following key basicAuthentication in your node pool

'hosts' => [
	localhost:9200'
],
'basicAuthentication' => [
              '<username>',
              '<password>'          
]

Using babenkoivan/elastic-client

If you use babenkoivan/elastic-client (I use it for Laravel), publish the config file and go to elastic.client.php and add it under your connections

<?php declare(strict_types=1);

return [
    'default' => env('ELASTIC_CONNECTION', 'default'),
    'connections' => [
        'default' => [
            'hosts' => [
                env('SCOUT_ELASTIC_HOST', 'localhost:9200'),
            ],
           'basicAuthentication' => [
              '<username>',
              '<password>'          
			]
        ],
    ],
];

API Key

To generate an API key, you will still require the username & password from basic authentication. Then you can generate an API key first using either cURL or Kibana. I used this query:

curl --location --request POST 'http://<username>:<password>@localhost:9200/_security/api_key' \
--header 'Content-Type: application/json' \
--data-raw '{
    "name": "php-client"
}'

This returned a response with the api_key and id key

{
    "id": "<id>",
    "name": "php-client",
    "api_key": "<api-key>",
    "encoded": "<encoded>"
}

Using Elastic Search

$client = ClientBuilder::create()
->setApiKey('<id>', '<api_key>')
->build();

Using babenkoivan/elastic-client

If you use babenkoivan/elastic-client, publish the config file and go to elastic.client.php and add it under your connections to use the encoded key - it includes both id and api key.

<?php declare(strict_types=1);

return [
    'default' => env('ELASTIC_CONNECTION', 'default'),
    'connections' => [
        'default' => [
            'hosts' => [
                env('SCOUT_ELASTIC_HOST', 'localhost:9200'),
            ],
           'apiKey' => [
              '<encoded>
              ]
        ],
    ],
];

What is a Data Provider?

When I write a test for a method, or a class, I write multiple assertions with the values for the same code. Data Providers are useful here when all that changes is the values passed to the method.

DataProviders are a framework for easily controlling how data can be provided from a source

Let's take an example of how you would write a test without data providers. Assume you have a method add($a, $b) in a class Operations that returns a value, summing up the numbers.

    public function test_add()
    {
    	$actual = (new Operations)->add(1, 2);
        $this->assertEquals(3, $actual);
    }

When you want to add multiple assertions, you would be tempted to add another assertion like this:

    public function test_add()
    {
    	$actual = (new Operations)->add(1, 2);
        $this->assertEquals(3, $actual);
        
        $actual = (new Operations)->add(3, 4);
        $this->assertEquals(7, $actual);
    }
    
    // Or a test per method
    public function test_add_first()
    {
    	$actual = (new Operations)->add(1, 2);
        $this->assertEquals(3, $actual);
    }
    
    public function test_add_second()
    {
    	$actual = (new Operations)->add(3, 4);
        $this->assertEquals(7, $actual);
    }

    

These add overhead if the signature of the method changes, or when you want to cover more cases.

How to use a Data Provider in PHPUnit

A Data Provider can simplify this, allowing you to pass multiple sets of values for the same test. From the official documentation:

A data provider method

• must be public
• and either return an array of arrays or an object that implements the Iterator interface and yields an array for each iteration step.

Let's convert the existing test case using a Data Provider. We will use a dataProvider annotation following the name of the data provider.

/**
* @dataProvider addProvider
*/
public function test_add($a, $b, $expected)
{
	$actual = (new Operations)->add($a, $b);
    	$this->assertEquals($expected, $actual);
}

public function addProvider()
{
 	return array(
        	array(1, 2, 3),
        	array(4, 5, 9),
    );
}

In this case, PHPUnit would pass the take the array, loop through the items (array again) and pass the arguments based on the position of the method parameters.

For the first item, it will take array(1, 2, 3), call test_add(1, 2, 3)  and validate the assertions. Then the next item and so on.

Inline Data Providers in PHPUnit

In the test cases above with a Data Provider, we can simplify it even further by inlining the data provider. The annotation to use is testWith

/**
* @testWith array(
        	array(1, 2, 3),
        	array(4, 5, 9),
    );
*/
public function test_add($a, $b, $expected)
{
	$actual = (new Operations)->add($a, $b);
    	$this->assertEquals($expected, $actual);
}

return response()->json(['url' => 'https://www.domain.com/api/test']);

I expected a response like this and was what I saw in a JSON formatter.

https://www.domain.com/api/test

But the raw response looked like this, with unescaped back slashes on the JSON body.

https:\/\/www.domain.com\/api\/test

I used Laravel's default JSON response helper and upon looking into it, there are options that you can set on the response to escape the slashes - JSON_UNESCAPED_SLASHES|JSON_PRETTY_PRINT. response()->json() takes the data as the first parameter, HTTP status code as the next, HTTP headers as the next and then options.

return response()->json(
['url' => 'https://www.domain.com/api/test'],
200,
[],
JSON_UNESCAPED_SLASHES|JSON_PRETTY_PRINT
);

The title tag is rendered via Blade templates, and the value is passed from the controller.

<html>
<head>
<title> {{ $title }} </title>
</head>
...

When the $title variable is passed, it is cut down to just 70 characters as this is the recommended title length for Google.

$title = substr("Title here", 0, 70);

I started looking at the few job postings that returned an empty string instead of a valid string.

$title = substr("SEO Manager at ZAP-Hosting GmbH & Co. KG | North Rhine-Westphalia | Münster | Germany", 0, 70);

My expectation was that it would return SEO Manager at ZAP-Hosting GmbH & Co. KG | North Rhine-Westphalia | Mü as the result. Unfortunately for me, it didn't. When I dumped the variable, the result was this:

b"SEO Manager at ZAP-Hosting GmbH & Co. KG | North Rhine-Westphalia | MÃ"

Notice the weird b before it? Immediately, I knew this was an issue because the special character ü and therefore needed to be handled differently.

I found two possible solutions and both work well:

• Adjust the blade template to print as a special character (no output escaping)

<html>
<head>
<title> {!! $title !!} </title>
</head>
...

• Change substr() calls to mb_substr()

A day after that, I started seeing real world errors from browsers. Some of them were from outdated browsers. Most interesting error that was captured was Unhandled Failed to fetch from Chrome and TypeError: NetworkError when attempting to fetch resource from Firefox.

Initially, I assumed that this might have been a backend error - perhaps no response from my API - so I checked nginx logs, sentry for backend. Everything looked good, which was puzzling. I looked up on Google to find the cause of this issue.

On Stack Overflow, I found someone experienced the same issue. The explanation was quite simple:

When the page loads, the refresh button changes to cross button, now if some api request is in progress during this page loading time and the user click this cross button, then iOS chrome/safari throws this error.

What this meant was this error being logged was a hindrance since it was useless, prevented me from seeing the actual errors. Luckily, there was a solution to ignore these on setup.

Sentry.init({
  dsn: "sentry_dsn",
  ignoreErrors: [
    'TypeError: Failed to fetch',
    'TypeError: NetworkError when attempting to fetch resource.',
    'TypeError: Cancelled'
  ],
});

I wish that the browsers included more information on this error, so it could be captured by Sentry.

- resources	
	- de	
    - en		
    	- app.php		
        - subfolder			
        	- file.php

To access the translation keys in app.php, it's straightforward as described in the Laravel documentation. To access a key from app.php, you can use:

trans('app.key')

Once I organized the language translations inside a sub-folder, I tried to access in this way.

trans('subfolder.file.key')

And it wouldn't work. Laravel documentation does not seem to mention how one can access a key from inside a sub folder. I looked up on Github Issues on the Laravel Repository and found a way to access the key.

trans('subfolder/.file.key')

This worked out well but the point to notice is that Taylor confirmed that this is not a way that may be supported in the future releases.

In the console window of Chrome, I saw an error as well which indicated the structure was off.

Caught TypeError: Cannot read properties of null (reading 'childNodes')at XMLDocument.ready (content.js:218)ready @ content.js:218

I had to adjust my <urlset> from this

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml">

to this, thanks to this Stackoverflow answer

<urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd http://www.w3.org/TR/xhtml11/xhtml11_schema.html http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd"
        xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/TR/xhtml11/xhtml11_schema.html">

Strangely enough that while the XML was rendering properly, Google Search Console was displaying an issue for the sitemap

Your Sitemap or Sitemap index file does not properly declare the namespace!

The schema below fixed the Google issue (that's all we care about in 2021, right?) while the rendering issue still persists.

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:xhtml="http://www.w3.org/1999/xhtml"
        xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">

The error above popped up when I tried to install a package locally via Composer. On composer.json, I had the following package definition:

    "require": {
        "package_owner/package_name": "branch#3de8008",
}

This pointed to a particular commit that I wanted to include when I got the error. It turns out that all packages that are installed locally or via private packages, have to be prepended with dev- so this fixed the issue.

    "require": {
        "package_owner/package_name": "dev-branch#3de8008",
        }