-
Notifications
You must be signed in to change notification settings - Fork 212
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 on updating entity schema #53
Comments
Hi, |
I have 777 on web/ already. |
Zyles — do you have a screen shot of the 500 error (full browser window). A modern web application can throw a 500 in a variety of different ways — knowing which way will help others help you with your problem. |
Thanks Zyles, that's helpful. However, in the future if you can take a screenshot with the full browser window, including URL bar, that will be extra helpful to people trying to debug. Looking at your screenshot, it's a stylized error which means the problem isn't with the web server, it's with the application itself. This is also the error page OroCRM shows when running in production mode. If you run it in development mode, you'll often get a more robust error. Can you try running the application with a development mode URL and posting the 500 error screen shots you see there?
|
I can't screenshot the entire URL since it is a public URL. I have now tested it with app_dev.php The application is a fresh https://github.com/orocrm/platform-application Now I get access to the error logs and stuff and this stands out:
|
Hi, @Zyles ! Can you run Urgent fix is to remove https://github.com/orocrm/platform/blob/1.2/src/Oro/Bundle/InstallerBundle/Resources/config/services.yml#L40 this definition.
Can you check this closely? This functionality was removed on master, so looks like you are suing 1.2 version |
Seems to work now. I can create new entities and update schema in dev mode. But there is a new problem. Everything works with app_dev.php but if I login without it I get 500 errors everywhere I go. |
Now it spits this out in prod.log on ANY url I go to. Again I have no issues with app_dev.php
|
Zyles, you might have more luck on the OroCRM forums — these are starting to sound more like development questions that issues with the framework/application itself (I know, there's a fine line between the two). Oro uses Symfony's logger (Monologger, I think). This logger will hold all logged content until an error of a certain level happens (
It sounds like PHP/Symfony/Oro are looking for a custom class |
try if error still be there then you need to run schema update in dev mode |
It is not a development issue since I have written ZERO code. Like I stated before I used the skeleton platform installation. If I use the interface provided by the default Oro platform to create custom entities and it throws errors this is obviously a problem somewhere else. Thanks now it works. What is the source problem of this issue? Is it cache write/delete permissions? I am pretty sure when I installed the application that I fixed them or else I would not even be able to run the application in the first place. I once again ran When you update the schema does it clear the cache etc. by itself? |
This listener supposed to be wide-case but its hard to cover all cases(sometimes permissions must be removed after installation), so we decided to use check on setup only. It was removed in master. Will be in our next release. |
This problem still persists. Pretty annoying. |
Provide detailed steps to reproduce please. |
This seems to be tied to the field type "Text".
Other field types seem to work. SQLSTATE[42000]: Syntax error or access violation: 1170 BLOB/TEXT column 'source_data' used in key specification without a key length |
Just updated to the latest Oro and it seems to have been fixed now. Thanks. |
So I tried to make new entity, added field etc. and run "Update schema" and I get 500 error.
Which log file would this be saved to? I checked the logs for prod.log and dev.log and the apache log but I can't find any errors.
In fact this destroys the entire application. I can not go to any report view.
An urgent fix would be welcome as I need to test the entity system extensively.
The text was updated successfully, but these errors were encountered: