I deployed a radiant cms application to server. In production mode while creating child page I am getting "Validation errors occurred while processing this form. Please take a moment to review the form and correct any input errors before continuing" error even though i given tiles, slug, It is working fine in development mode. Please help.
Thanks
Related
I'm trying to replicate a bug in development which come from the production environment.
When the bug occurs I should see a 500 server error, but rails is displaying the following page to me, which is not what I want:
the grey rails error page
(the error in the image is not the one I'm trying to reproduce, but it shows they error page, which is what I'm talking about here)
How can I turn off this feature from rails so it just display a 500 error that a normal user will see?
And what is this tool/page called? I usually just call it the (red) rails error page. (but in this case it is grey for some reason, I don't know why too. Does anyone know?)
Try to the following
# config/environments/development.rb
config.consider_all_requests_local = false
By default, this value is true because of the need to debug code on development environment that's why, if you change value with false then will show the error page which is designed default.
If you need to generate and design custom then the follow this tutorial.
Hope to help
What about run rails in production environment?
rails server -e production
I have a Rails app on Heroku with a couple of forms on it. They show up fine locally, but on heroku, my form doesn't show up at all. I know my database is being accessed, because I have a greeting message with a user's name at the top of the page that's displayed fine.
Has anyone run into this issue and had any luck solving it?
Try to run your app locally on production environment and check is your form show up properly.
What I want to do works on my OSX dev machines and on a staging server. However, I encounter problems on the production server.
I have a Rails Engine which I have created, maintained, and used over the years: https://github.com/allesklar/tkh_admin_panel
It works fine on many apps and I have been porting it to this new website as of late. For admin views, my controllers render the 'admin' layout which is located on this engine.
Everything has gone great until I tried to deploy to the site's production server. I get the following error:
ActionView::Template::Error (no implicit conversion of nil into String):
This exception occurs in the line with the following code:
render layout: 'admin'
I can't pinpoint any differences in gems, rbenv ruby versions, or any other factor from one setup to the next.
I've tried to reset the binstubs and done a number of other things.
No matter what I do, it works on the staging server and not on the production server.
Please point me to some directions where I can investigate further.
UPDATE ---
The scope of the problem has changed entirely since now I'm experiencing the same issue on my development machines.
I therefore think the problem lies in the host app/gem relationship. The same version of this gem works fine with some other Rails host sites of mine.
Any ideas welcome.
Try to recompile all assets. If you can (it's a prod server) delete all assets and manifest and re-deploy.
Try to delete all cache, if you are using page or fragment caching, perhaps your deploy system is not cleaning it correctly.
Simply reboot the system (simple action that fixed a lot of problems in the past).
And if nothing works, try to display the full backtrace to see where this is happening
I have a backboneJS app working with the gem rabl on Ruby on Rails
Better error only shows ruby errors (or rather server side errors), if it's a javascript error it will occur on the browser not the server, if the assets have errors it should appear in the precompilation, so you probably are covered too.
Anyways, using better errors has no downsides, cause the cases that won't work with better errors won't work with the basic error pages without better errors.
PS: If you want to debug an ajax request you can try opening the browser console and click the request that has an error and choose something that means close to 'open this request in a new tab'
Im facing a hairy bug when submitting a ruby on rails form on production environment, consisting on a blank response and page displayed by internet explorer 7-9.
This bug does not happen with any other common browsers and it's even quite random with ie as it sometimes works fine.
When failing, logs show a "200 OK in 0ms" which made me think about caching, but that didn't seem to be the source. After some debugging it looks like the server returns the 200 reply without even running the code; it doesn't stop on any breakpoint placed inside the action, tough logs show it was processed by it.
The failing form is a custom devise registration one, using devise in a spree 0.60 application and ruby on rails 3.0.7
Server is thin behind nginx.
Any suggestions? Thank you.