#hoopla

I'm using the geolocation_googlemaps module to add a location field for an event content type. It is rendered in the backend to choose a location and in the frontend to show a map with the chosen location to the user. Recently, it stopped working. It is still possible to choose locations in the backend, but in the frontend the generated request to Google Maps gives a 403. However, when copy-pasting the URL to the browser, it works. The issue is not related to a restriction of secure/insecure content mixing, because the URL adapts automatically with in the beginning. The issue is that Google changed its usage and billing policies. The module uses the Google Maps Static API, which could be used without an API key up to now, but now every maps API needs such a key. Google writes about this here: https:developers.google.com/maps/documentation/maps-static/usage-and-billing

So in order to get a key and to get it into the Drupal module, follow these steps. First, go here https://code.google.com/apis/console and create a project. Go to the APIs and search for the Maps Static API. Create a key and restrict it to the Static Maps API and the referring domain(s) which should be able to use it. In the dashboard, add a payment method. Second, copy-paste the API key to /admin/config/services/googlemaps. When reloading the page, everything should work again.

An alternative is to switch to open streetmap. There are Drupal modules in place including geolocation and leaflet. I'll check these out later.

Die SymfonyLive startet heute in Berlin mit zwei Tagen Workshops und einem Konferenztag: http://berlin2018.live.symfony.com/

I use scanimage in connection with ImageMagick for automated scanning in my ERP systems. Suddenly it broke and convert started complaining:

scanimage [...] | convert - -compress jpeg -quality 100 -density 100 pdf:- > tmp.pdf
convert: not authorized `pdf:-' @ error/constitute.c/WriteImage/1072.

ImageMagick introduced some policies. They need to be adjusted to be able to write PDF as before. https://stackoverflow.com/questions/42928765/convertnot-authorized-aaaa-error-constitute-c-readimage-453#93 worked for me.

I used the manual from https://github.com/sonata-project/SonataAdminBundle/blob/3.x/docs/cookbook/recipe_sortable_listing.rst, but it did not work for me. In fact, it contained too many bundles for my setup making the installation overly complicated. Furthermore, there is a pitfall when using YML files for entities. Using YML is supported, but not well documented and if annotations (as in the manual) are used together with YML, the annotations will be ignored. In order to get it working I needed to do the following steps.

Install the prerequisites gedmo/doctrine-extensions and pixassociates/sortable-behavior-bundle via composer. Activate the Sortable bundle in AppKernel:

new Pix\SortableBehaviorBundle\PixSortableBehaviorBundle(),

Add position field to Doctrine YML and update the entity PHP and database as usual:

fields:
        position:
            type: integer
            nullable: true
            column: position
            gedmo:
                - sortablePosition

In the Sonata Admin class add the following:

protected $datagridValues = [
        '_page' => 1,
        '_sort_order' => 'ASC',
        '_sort_by' => 'position',
    ];

protected function configureListFields(ListMapper $listMapper)
    {
        ...
        $listMapper
            ->add('_action', null, [
                'actions' => [
                    'move' => [
                        'template' => '@PixSortableBehavior/Default/_sort.html.twig',
                        'enable_top_bottom_buttons' => true,
                    ],
                ]
            ]);
    }

    protected function configureRoutes(RouteCollection $collection)
{
    // ...
    $collection->add('move', $this->getRouterIdParameter().'/move/{position}');
}

Activate the Sortable Admin for this entity in services.yml:

admin.lineitem:
        class: Ond\ErpBundle\Admin\LineItemAdmin
        arguments: 
            - ~
            - Ond\ErpBundle\Entity\LineItem
            - 'PixSortableBehaviorBundle:SortableAdmin'
        tags:
            - { name: sonata.admin, manager_type: orm, label: Line Item, show_in_dashboard: false }
        public: true

Symfony 1.4 requires PHP 5.5 or less, so it doesn't run on any current Ubuntu which ships with newer PHP versions. I don't want any old version running on my system, but still be able to maintain some legacy applications. There is a nice Docker image which does this trick: https://codeyourdream.com/blog/how-run-multiple-php-versions-apache-one-linux-machine-using-docker

Existing applications can be accessed by their local URL (the docker image uses the host's apache virtual host configurations), but on different ports depending on the PHP version needed, for example http://ondorierp.localhost:8055 for PHP 5.5. It uses the host's MySQL, which needs to be configured to use the Docker IP address to bind to.