When you are running a multiple PHP applications around the same Database you might get this error which results in not rendering the block. Here is a quick fix for it.
You have set a path for a configuration directory in your settings.php file but is it taking the correct path or not. Here is a simple step to validate that instead of exporting or import configurations.
You have deployed some changes to Live on a tagged release but now you want to add few more features on top of the tagged release and create a new tag. You need to perform the following steps to achieve this.
There can be scenario's where you might want some custom pages or paths to not be cached. There is a better way of doing it now
This can happen when you are running on a older version of composer i.,e 1.0 and wants to update to the latest version but the simple composer self-update command doesn't work instead it tells you Command self-update not defined.
There are scenarios when you are running multiple projects in your development server but each of them may need a different PHP version. Some of them might be upgraded to latest version while some of them still awaits the upgrade.
There are instances when all of a sudden you see your site going down and when you try to look deeper you may find the AWS is running out of storage space. Is your application growing too big or is there an issue with the EC2 instance setup ?
Unknown Collation error usually arrises when you try to move a DB from a higher mysql version e.x, 8.0 to a lower mysql version e.x, 5.7
Upgrading to MySQL 8.0 from MySQL 5.7 offers several benefits such as improved performance, better security, and better support for JSON and spatial data. The upgrade process is straightforward, and you can follow the steps outlined in this blog