
Good content takes time and effort to come up with.
Please consider supporting us by just disabling your AD BLOCKER and reloading this page again.
Hmmm, that's weird well actually everything was working in my system. When I deployed the application to production facing this weird issue. Ya, I know the feeling.
You can quickly overcome this kind of PHP issues in the following ways:
Solution 1 - Check proper permission
Solution 2 - Check the owner of the folder
When you want to write to the files with PHP scripts the file or folder path won't be having proper write permissions. You can fix it with the following
chmod -R 777 file_or_folder_name
NOTE: Kindly check if 555 or 755 or 775 will work first
Sometimes in all the project paths, you will encounter this kind of issue. Then check if the owner of the project is www-data
or not.
If not then run the following command
sudo chown -R www-data:www-data /var/www/html
Here I have changed the owner group of html
to www-data
. Make sure to cross-verify your folder before changing the owner.
Sass or SCSS @mixin vs @extends vs Placeholder (%)
What Is Composer? How Does It Work? Useful Composer Commands And Usage
Ensure text remains visible during Webfont load
Add Analytics To AMP (Accelerated Mobile Pages) HTML Pages
Laravel 7.x Multiple Database Connections, Migrations, Relationships & Querying
Generate Sitemap in PHP Laravel
NGINX Security Best Practices & Optimization
Securely SSH Your Server & Push Files With FileZilla
Install Apache Web Server On Ubuntu 20.04 / Linux & Manage It
Make Laravel Controllers Slim By Skimming Form Validation Request
Laravel Clear Cache Of Route, View, Config Command