Rob – Rob Allen's DevNotes

Displaying errors in Expressive with Twig

If you're not using the Whoops error handler with Expressive and are using the Twig renderer, then you are given no information about the problem that occurred, even in debug mode. To fix this, I changed error.html.twig to this:

{% extends '@layout/default.html.twig' %}

{% block title %}{{ status }} {{ reason }}{% endblock %}

{% block content %}
    <h1>Oops!</h1>
    <h2>This is awkward.</h2>
    <p>We encountered a {{ status }} {{ reason }} error.</p>
    {% if status == 404 %}
        <p>
            You are looking for something that doesn't exist or may have moved. Check out one of the links on this page
            or head back to <a href="{{ path('home') }}">Home</a>.
        </p>
    {% endif %}

    {% if error %}
        <h2>Error details</h2>
        <p>Message: <strong>{{ error.getMessage() }}</strong></p>
        <p>in <tt>{{ error.getFile() }}:{{ error.getLine() }}</tt></p>
        <pre>{{ error.getTraceAsString() }}</pre>

        {% set prev = error.getPrevious() %}
        {% for i in 1..10000 if prev %}
            <h3>Previous error</h3>
            <p>Message: <strong>{{ prev.getMessage() }}</strong></p>
            <p>in <tt>{{ prev.getFile() }}:{{ prev.getLine() }}</tt></p>
            <pre>{{ prev.getTraceAsString() }}</pre>
            {% set prev = prev.getPrevious() %}
        {% endfor %}
    {% endif %}
{% endblock %}

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

{% extends '@layout/default.html.twig' %}

{% block title %}{{ status }} {{ reason }}{% endblock %}

{% block content %}

<h2>This is awkward.</h2>

<p>We encountered a {{ status }} {{ reason }} error.</p>

{% if status == 404 %}

<p>

You are looking for something that doesn't exist or may have moved. Check out one of the links on this page

or head back to <a href="{{ path('home') }}">Home</a>.

</p>

{% endif %}

{% if error %}

<h2>Error details</h2>

<p>Message: <strong>{{ error.getMessage() }}</strong></p>

<p>in <tt>{{ error.getFile() }}:{{ error.getLine() }}</tt></p>

<pre>{{ error.getTraceAsString() }}</pre>

{% set prev = error.getPrevious() %}

{% for i in 1..10000 if prev %}

<h3>Previous error</h3>

<p>Message: <strong>{{ prev.getMessage() }}</strong></p>

<p>in <tt>{{ prev.getFile() }}:{{ prev.getLine() }}</tt></p>

<pre>{{ prev.getTraceAsString() }}</pre>

{% set prev = prev.getPrevious() %}

{% endfor %}

{% endif %}

{% endblock %}

The new part is the within the {% if error %} block. In debug mode, error is set to the exception that was thown and is blank otherwise, so you won't leak sensitive information (as… continue reading.

Posted on 18 October 2017 in PHP, Zend Expressive, Zend Framework Leave a comment

"Software architecture is failing" by Alex Hudson

Alex Hudson's article, "Software architecture is failing" is a really interesting article and resonates with me as I come across this a lot. I recommend reading it. I'm very much in the camp of designing for the business requirements first and my biggest successes are the apps which solve my clients' problems. To call one of my apps "legacy" is a compliment; it means that I've written something that works and is solving real-problems for… continue reading.

Posted on 16 October 2017 in Around the web

Pretty print curl -i

My favourite tool for working with APIs is curl and in particular, I like using the -I switch to view the status line and headers too: This generates an output that looks like this:

$ curl -i https://api.joind.in
HTTP/1.1 200 OK
Date: Wed, 04 Oct 2017 09:51:46 GMT
Server: Apache
X-Powered-By: PHP/5.6.4
Access-Control-Allow-Origin: *
Content-Length: 363
Content-Type: application/json; charset=utf8

{"events":"https:\/\/api.joind.in\/v2.1\/events","hot-events":"https:\/\/api.joind.in\/v2.1\/events?filter=hot","upcoming-events":"https:\/\/api.joind.in\/v2.1\/events?filter=upcoming","past-events":"https:\/\/api.joind.in\/v2.1\/events?filter=past","open-cfps":"https:\/\/api.joind.in\/v2.1\/events?filter=cfp","docs":"http:\/\/joindin.github.io\/joindin-api\/"}

1

2

3

4

5

6

7

8

9

10

$ curl -i https://api.joind.in

HTTP/1.1 200 OK

Date: Wed, 04 Oct 2017 09:51:46 GMT

Server: Apache

X-Powered-By: PHP/5.6.4

Access-Control-Allow-Origin: *

Content-Length: 363

Content-Type: application/json; charset=utf8

{"events":"https:\/\/api.joind.in\/v2.1\/events","hot-events":"https:\/\/api.joind.in\/v2.1\/events?filter=hot","upcoming-events":"https:\/\/api.joind.in\/v2.1\/events?filter=upcoming","past-events":"https:\/\/api.joind.in\/v2.1\/events?filter=past","open-cfps":"https:\/\/api.joind.in\/v2.1\/events?filter=cfp","docs":"http:\/\/joindin.github.io\/joindin-api\/"}

What I would like to do is pretty print the body if it's JSON or XML so that it's easier to read. There are some tools out there, like jq which will format JSON, but they can't seem to cope… continue reading.

Posted on 11 October 2017 in Computing, PHP One comment so far

Converting a Composer dependency to git for editing

I'm adding a new feature to ZF's Problem-Details component and it's easiest to do this within the context of the application I'm developing. The component lives in vendor/zendframework/zend-problem-details and was installed using composer require so doesn't have its own git repository as the distribution zip file was used to install it. To change it to a git repository, we can use the –prefer-source option and specify a branch like this:

$ composer require --prefer-source zendframework/zend-problem-details:dev-master

1	$ composer require --prefer-source zendframework/zend-problem-details:dev-master

I now have a… continue reading.

Posted on 4 October 2017 in PHP View all 3 comments

Custom URLs for a Cloud Foundry application

Now that I have my application deployed to Cloud Foundry, I need it to work with my own domain, such as bookshelf.akrabat.com rather than slim-bookshelf.eu-gb.mybluemix.net. We can do this via the command line which is useful. To do this we need to create a domain and then we can create a route. Create a domain To create a domain, we use the command cf create-domain {organisation name} {domain name}. For me, my organisation is "19FT",… continue reading.

Posted on 27 September 2017 in Bluemix, Cloud Foundry Leave a comment

CORS and OpenWhisk web actions

By default, OpenWhisk will handle the relevant responses for CORS. Specifically, it will respond to an OPTION request with these headers:

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: OPTIONS, GET, DELETE, POST, PUT, HEAD, PATCH
Access-Control-Allow-Headers: Authorization, Content-Type

1

2

3

Access-Control-Allow-Origin: *

Access-Control-Allow-Methods: OPTIONS, GET, DELETE, POST, PUT, HEAD, PATCH

Access-Control-Allow-Headers: Authorization, Content-Type

If you need to change what is sent or you don't want to send these headers at all, then you need to do set the annotation web-custom-options to true and handle the OPTIONS header yourself. Note that if you don't set this annotation, you must not set any of these headers yourself as… continue reading.

Posted on 20 September 2017 in OpenWhisk, PHP, Swift Leave a comment

CLI credentials for a Cloud Foundry database

If you need access to your Cloud Foundry database from the command line the easiest way to get a set of credentials is to create a service key. This is done using the command cf create-service-key {service-name} {key-name}. You can call the key anything, so to connect to my database that I created previously: $ cf create-service-key slim-bookshelf-db ROB_CLI Creating service key ROB_CLI for service instance slim-bookshelf-db as rob@19ft.com… OK Now that we've set up… continue reading.

Posted on 11 September 2017 in Bluemix, Cloud Foundry Leave a comment

Using PostgreSQL with PHP in Cloud Foundry

Having successfully deployed a PHP application to Cloud Foundry, I needed a PostgreSQL database for persistent storage. I found Lorna Mitchell's Connecting PHP to MySQL on Bluemix helpful and this article expands on that information. I want to create a cloud-based PostgreSQL database and connect it to Laravel's Eloquent in a Cloud Foundry application. This is how to do it. Create the database instance As I'm using Bluemix for my Cloud Foundry hosting, I'm using… continue reading.

Posted on 6 September 2017 in Bluemix, Cloud Foundry, PHP Leave a comment

Deploying a PHP application to Cloud Foundry

I recently had a requirement to deploy a Slim application somewhere. As I already have a Bluemix account, it seemed sensible to deploy it to their Application Runtimes service which is an installation of the Open Source Cloud Foundry project. This turned out to be quite easy, but there are a number of steps involved, so I'm documenting it here. Setup the CLI tools I'm a command line person, so did it all via the… continue reading.

Posted on 30 August 2017 in Bluemix, Cloud Foundry, PHP Leave a comment

Adding a user to your Bluemix space

I'm at the stage where I need to give another developer access to my IBM Cloud Functions actions. I'm not really an infrastructure person and I found the user management pages on the Bluemix console incomprehensible, so used the command line. This is how I did it so that I don't have to work it all out again. Add the user to your organisation These are the steps to add the user to your organisation:… continue reading.

Posted on 25 August 2017 in Bluemix One comment so far

Archives