The Problem

In multi-tenant applications built with Filament, ensuring the correct tenant context is crucial for data isolation and application functionality. A common issue arises when middleware responsible for setting the tenant context runs before Filament resolves the tenant from the URL.

In the Reimpact/platform project, a recent update addresses an issue where Livewire update requests were being incorrectly blocked by a custom middleware. This post details the problem and the solution implemented.

The Problem

The ValidationUserMiddleware was designed to handle user authentication and validation for incoming requests. However, it was inadvertently blocking unauthenticated

The Problem

In a Laravel application, particularly when using Livewire, maintaining consistent authentication behavior across different types of requests can be tricky. A common issue arises when Livewire requests, which often send Content-Type: application/json, are not correctly handled by authentication middleware, leading to unexpected 401 errors instead of redirects to the login page.

Introduction

Experiencing a 401 Unauthorized error immediately after a successful login can be a frustrating issue in Laravel applications. This often stems from incorrect redirection targets or misconfigured middleware. Let's explore how to diagnose and resolve such problems, specifically within the context of projects using middleware for access control.

Understanding the Problem

Context: Breniapp

The Breniapp project focuses on [description]. Recent efforts have centered on improving the documentation, specifically regarding mobile responsiveness.

Mobile Responsiveness Guidelines

A key area of focus has been the addition of mobile responsiveness guidelines to the CLAUDE.md documentation file. Ensuring applications are accessible and user-friendly across

Ever fought with mobile scrolling on a specific page? It's a common pain. In the Breniapp/brenia project, we recently ran into an issue where a fixed layout intended for larger screens was unintentionally blocking scrolling on mobile devices on the content generation page.

The culprit? An overflow: hidden rule applied at the page level, combined with fixed panel heights.

Introduction

Content calendars are essential tools for managing and scheduling content across various platforms. A well-designed calendar can significantly improve workflow, collaboration, and overall content strategy. Let's explore the recent enhancements to the content calendar in the Breniapp/brenia project.

Key Improvements

The redesigned content calendar focuses on providing a more

The landing project received a facelift, focusing on aesthetic improvements to the retro theme. The goal was to reduce the overwhelming use of a single color and introduce more visual diversity across different elements.

The Challenge

The initial retro theme relied heavily on yellow, which, while visually striking, became monotonous when applied to all elements like badges, project

Introduction

Color plays a vital role in shaping user perception and engagement on landing pages. A well-chosen color palette can significantly improve the visual appeal and overall user experience. Let's explore how targeted color adjustments can enhance the look and feel of a landing project.

The Power of Color in UI

Colors evoke emotions and associations. Utilizing a consistent and

When using Laravel Horizon, a queue monitoring tool, you might encounter issues with Content Security Policy (CSP) blocking inline scripts. Here's how to address it.

The Problem

Horizon serves its JavaScript and CSS inline using Horizon::js() and Horizon::css(). Without a proper nonce for CSP, browsers can block these inline scripts, even though Horizon's own authentication gate