-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 Error When Trying to Edit Component and Viewing Theme, Stylesheet,Localisation and 'Create an Incident Template' Pages #1432
Comments
Ping @jbrooksuk. |
I was looking for this issue earlier but couldn't find it. Looks like GitHub/Chrome cached the issues list. |
It's all good here: |
Still using MySQL @TheoBearman? |
Yeah I am. |
What are you editing? |
Trying to add a link to a component caused the error initially. |
Loading the actual list of components, as you showed in your screenshot, still works for me. |
So it's adding, not editing? |
No adding a link (web link) to a component. |
Is the link valid? |
It is yes. |
Are you running from |
I added a valid link to a component, checked on phpMyadmin and it was on the component but I got the 500 error rather than a success message on Cachet itself. |
My install is always up to date with master. OCD levels of always. |
Is it still happening? It's odd but I can't recreate this issue at all. |
I just recreated the error. I can walk you through it on Skype. |
Update: I am reciving new 500 errors on other pages. Issue title has been updated and the new error logs are:
For the
I have confirmed all the folders and subfolders of my Cachet install have 777 permissions, including |
This is still definitely a file permission error on your part I'm afraid. Access denied really does mean access denied. |
I'd personally recommend chowning the folders recursively to the user running the webserver rather than opening up the file permissions in an insecure way though. |
What command would I use to chown the whole folder to the www-data user? |
|
Ok. That fixed all the issues except for the 500 error when the weblink is added to a component. It does actually save but gives me a 500 error when clicking the 'save' button rather than an 'updated' message on the component list. |
Can you drop the latest log entries in again please. |
@jbrooksuk Here you go:
|
Did you remember to run |
I'm pretty sure that this isn't a Cachet issue, but an installation one. The demo and my local instance are working just fine. |
Any ideas how I can correct it? |
Is there a possibility that #1439 applies to me? |
I'd be confused if so, because yours has been working. |
@jbrooksuk Indeed. Any ideas for fixes? |
I'm afraid not. Your permissions are all correct? Try running |
All my permissions are correct. That command didn't work either. Never mind. Not a big issue. |
What about |
I can't for the life of me replicate your issue I'm afraid Theo. |
I offered to Skype to show you the issue. That command also didn't work. |
I know buddy, but I'm not around all of the time I'm afraid. |
I finally fixed it. When I ran, |
Please never use the artisan migrate command. Please only interface with our |
Are these commands new? Is there a list? |
These commands have been in cachet for a very long time. They do not exist in a normal laravel app. |
Just run |
So what is the command to run the database migrations using the |
We don't have one. That's the point. You're either installing, updating, or re-installing. The details of what happens under the hood don't matter. |
You want |
And this is on top of |
You still need to do the composer part, but after that, our app commands deal with the rest. |
All clear. Thanks Graham. |
I have verified this isn't a Ubuntu permissions problem because my whole Cachet folder has 777 permissions.
The text was updated successfully, but these errors were encountered: