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
www-data. Make sure to cross-verify your folder before changing the owner.
Basic Server Security Setup For Ubuntu / Linux
Sass or SCSS @mixin vs @extends vs Placeholder (%)
Securely Connect Server MYSQL DB From Sequel Pro / MYSQL Workbench
NGINX Security Best Practices & Optimization
Testing Laravel Emails With MailHog
Why You Should Run Cronjobs In Laravel?
Debugging Laravel Queue Email Issues
Supervisor For Laravel Queue Scheduling
Push Files To CPanel / Remote Server using FTP Software FileZilla
Accessors & Mutators In Laravel. Problem In Set Attribute While Saving/Updating Data & How To Resolve It