-
Notifications
You must be signed in to change notification settings - Fork 207
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
Error 500 Internal Server Error in /admin/api-admin-menu #1119
Comments
With those 2 things we can see the true response of the api and make sure its not an issue about authentication headers. |
Hi, @nadar. I think the problem is, again, a PostgreSQL incompatibility. Look at the Response you request me:
When I add the
|
Yes its a problem with not compatible querys, as we can see we get the same response, so it has nothing to do with authorizations. I am going to fix that! |
@ricpelo Now the fixed statements should be removed, could you please try again? Thank you for your time, i am really looking forward to see luya running on a postgre sql setup ;-) (The Subsplit will run in 1 hour, then the changes are available) |
@nadar, sure! I'll wait for the subsplit and I'll tell you ;). |
Changes aren't still available... Is it normal? |
just update the composer.json files as described and run |
Works better! But still errors:
|
Hmm ok, I know why I am going to check how to fix this, but temporary could you please just remove the caching component in your config and tell me the result? https://github.com/luyadev/luya-kickstarter/blob/master/configs/env-local.php#L117-L119 (Just remove the whole entry) |
After removing the cache component all seems to work OK! |
Because as far as I can see, those sql depencies can not be provided with a query builder. I am going to investigate on this. But happy to hear it seems to work with pgsql 👍 |
Great, thank you! |
Hi, @nadar, I've got another problem in
|
Maybe try again after the subsplit (in 25min) but i think it was not the reason for your problem. Did you made different comments? Could you please post the full trace? Cause i was not able to find a groupby or counting query in the mentioned model. When does the problem appeard, when dropping a new block? |
Hi, @nadar, sorry for the delay. The problem is still here, and yes, it appears when dropping a new block. |
|
|
Thanks for the trace, now i can see the problem. |
@ricpelo Would please so kind to test again? (Maybe after the composer update you have to run the migrate and import command as well) Thank you! |
Hi! I have the following problem. After
|
it will be So use: |
Oh, great! I'll do it and I'll tell you ;). |
Any news, @nadar? It seems to be a type problem in |
hi @ricpelo, i am little bit busy though i want to fix this 👍 could you verify this very quickly in your vendor folder, cause if this is the case i have to fix a few statements. Thanks |
@ricpelo could you test this problem very quickly in your vendor folder? This would help me lot, as there are a FEW such statements. |
Yeah, I'll try that today, sorry for the delay! |
@nadar, I'd just edited |
and what about |
|
Ok Thanks! I am going to change it. :-) |
Great! ;) |
Hopefully we have catched all those exceptions then. |
Hopefully Luya is now PostgreSQL-compatible ;). |
@ricpelo i did some changes, but this boolean/int validation "thing" is more complicated then i tought, then as now the models must validate boolean values as well but the yii gii model generator threats boolean as tinyint(1) (as there is no boolean in mysql), a little bit wired overall. Cause the angular does not post boolean values, it post int values as well - but lets see what happens. Let me know what happens now, maybe even make a fresh setup. |
@ricpelo maybe it was also not necessary to changes this everywhere and it was only a problem of the "hardcoded" caching statement? |
@nadar, I'll try it, but obviously the |
Using HEAD seems to work OK ;). |
including installation process, droping block, editing pages, working with crud? Would be great! |
All of that seems to works as expected, but this night I'll check deeper. |
@nadar, I'm unable to get crash the app after many use. To me, it works perfectly :). |
@ricpelo Sounds great! So i am going to make a changelog entry as "PostgreSQL Compatible" and close this issue, if you have any further Problems please create another Issue. Thanks for your help. |
@nadar Superb! :). |
What steps will reproduce the problem?
/etc/hosts
and Apache virtualhostluya.local
.What is the expected result?
The admin page rendered without errors.
What do you get instead? (A Screenshot can help us a lot!)
A 500 (Internal Server Error) message.
If I go to http://luya.local/admin/api-admin-menu, I get the following XML output:
LUYA Check ouput (run this script and post the result: luyacheck.php)
The text was updated successfully, but these errors were encountered: