Skip to main content

Laravel v7.12.0 released

Laravel v7.12.0 is released in 2020/05/19, here are the changes we`ve merged into this release.

v7.12.0 (2020-05-19)
Added
Added Illuminate\Http\Middleware\TrustHosts (9229264)
Added ability to skip middleware from resource routes (#32891)
Fixed
Fixed Queued Mail MessageSent Listener With Attachments (#32795)
Added error clearing before sending in Illuminate\Mail\Mailer::sendSwiftMessage() (#32799)
Avoid foundation function call in the auth component (#32805)
Fixed inferred table reference for Illuminate\Database\Schema\ForeignIdColumnDefinition::constrained() (#32847)
Fixed wrong component generation (73060db)
Fixed bug with request rebind and url defaults in Illuminate\Routing\UrlGenerator (6ad92bf)
Fixed Illuminate\Cache\ArrayStore::increment() bug that changes expiration to forever (#32875)
Changed
Dont cache non objects in Illuminate/Database/Eloquent/Concerns/HasAttributes::getClassCastableAttributeValue() (894fe22)
Added explicit symfony/polyfill-php73 dependency (5796b1e)
Set Cache\FileStore file permissions only once (#32845, 11c533b)
Added alias as key of package's view components (#32863)

Popular posts from this blog

Composer Security Update (CVE-2021-29472) for leravel #2021

Composer had a security vulnerability reported (CVE-2021-29472) and a new version has been released to address this. Everyone should run  composer self-update  to get v2.0.13 which includes the fix. According to their  announcment : As a precaution after updating Composer we recommend you audit your composer.lock files to ensure they only contain URLs and none which start with -- , e.g. --config and could be considered command line options. Should you find any such URL values despite our belief that this vulnerability was not exploited in the wild, please contact us immediately by email to security@packagist.org. In general we always recommend you review changes you make to your lock files to ensure no untrusted dependencies or external URLs are introduced to your application. Please note that Packagist.org is only a metadata server and package contents are downloaded from a location chosen by the package maintainers. Private Packagist will store copies of mirrored packag...

Laravel Forge Setup on Umami self-hosted analytics | Laravelnote

  Many of us are loooking to move away from Google Analytics where possible. Reasons for doing so include: Data privacy concerns Avoiding cookie warnings Seeking a simpler UI to share with clients/team While looking into alternatives you'll find a range of paid, privacy-focussed SaaS analytics products, as well as some self hosted open source options (some of which are shared by companies who also offer a hosted paid service). I wanted a self hosted option and before settling on Umami.js I also checked: Ackee Plausible (self-hosted, SaaS available) Pirsch (self-hosted, SaaS available) For all I know, these might be great - but I didn't get to a feature comparison or to try any of them out. I went with Umami.js simply because of how I wanted to install it on this occasion: on an Ubuntu VM, with Postgress/MySQL, and without using docker. One nice feature of Umami.js is easily sharing a public dashboard for a website, you can take a look at their own public dashboard (pictured bel...

Create Controllers with a Custom Stub in Laravel 8.36

The Laravel team released 8.36 with a custom stub option when creating controllers, a useCurrentOnUpdate method for blueprint datetime columns in MySQL, a dispatch_sync() helper function, and the latest changes in the 8.x branch: Support useCurrentOnUpdate for MySQL Datetime Columns Tim Martin contributed support for useCurrentOnUpdate for MySQL DATETIME column types: This allows using DATETIME columns for metadata like created_at and updated_at more effectively. Since TIMESTAMP columns in MySQL suffer from the Year 2038 Problem , using DATETIME columns is preferred in some applications. Here's an example from the tests: $blueprint = new Blueprint('users'); $blueprint->dateTime('foo')->useCurrentOnUpdate(); $statements = $blueprint->toSql($this->getConnection(), $this->getGrammar()); $this->assertCount(1, $statements); $this->assertSame('alter table `users` add `foo` datetime on update CURRENT_TIMESTAMP not null', $statements[0]); Queue ...