Discussions
Cannot push wagon to production instance
Hello,
I was wondering if someone could help me out. I am trying to push a wagon from a staging instance to a production instance but getting an error when dpeloying the wagon. I am getting the following error
root@XXXXXXXXXXX:/home/user/dhr-wagon# bundle exec wagon deploy live -v
Pushing Site
persisting Wagon [failed]
Locomotive::Coal::Error
# Error description:
Locomotive::Coal::Error
# Backtrace:
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/concerns/request.rb:36:in `do_request'
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/concerns/request.rb:15:in `put'
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/current_site.rb:13:in `update'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_site_command.rb:27:in `persist'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:34:in `block in _push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `each'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `_push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:25:in `block in _push_with_timezone'
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/activesupport-4.2.11/lib/active_support/core_ext/time/zones.rb:48:in `use_zone'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:24:in `_push_with_timezone'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:18:in `block in push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/activesupport-4.2.11/lib/active_support/notifications.rb:166:in `instrument'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:50:in `instrument'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:16:in `push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:12:in `push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:55:in `block in _push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:84:in `block in each_resource'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:77:in `each'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:77:in `each_resource'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:54:in `_push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:41:in `push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:31:in `push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon.rb:73:in `push'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/cli.rb:318:in `deploy'
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
/usr/local/rvm/gems/ruby-2.3.0@wagon/gems/thor-0.19.4/lib/thor/base.rb:444:in `start'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/bin/wagon:12:in `<top (required)>'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bin/wagon:23:in `load'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bin/wagon:23:in `<main>'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bin/ruby_executable_hooks:24:in `eval'
/usr/local/rvm/gems/ruby-2.3.0@wagon/bin/ruby_executable_hooks:24:in `<main>'
Seems like the API on the remote live server is not working properly. How can I check if API access is working?
Thank you for your help,
Posted by Jorge Rodriguez about 4 years ago
How to Avoid Public Submissions Accepted on All Paths?
It seems Locomotive accepts public submission POST requests of any `content_type` to any path.
Is there a way to change this behavior so that form submissions only work with the public submission url \(/entry_submissions/\<content type slug\>\)?
This way, we can easily lock out spam bots which don't run javascript.
Posted by Tobias Geisler over 4 years ago
Unable to add domain
I am unable to add a new domain name to my site. It just gives an error stating "My site is not updated." I have looked at the logs and do not see any errors.
Posted by Jorge Rodriguez over 4 years ago
Unable to access back-end of CMS
We have a website www.strykercare.com.au which is not currently letting us access the back-end to update content (vial www.strykercare.com.au/locomotive)
It has also suddenly stopped allowing customers to register and gain access to login-only content, and as I am unable to access the back-end I cannot diagnose this problem.
Posted by Maru Lush over 4 years ago
SSL Handshake failed
Hi,
We've got a website hosted at https://startupgrind.cat configured with Cloudflare and seems like sometimes at random takes ages to load while other times gives an error 525: SSL Handshake failed.
Please, get in touch!
Posted by Àlex Rodríguez Bacardit over 4 years ago
callAPI action: send integer types?
Struggling with an API call atm: Is it possible that the `callAPI` action converts all numbers into floats when converting the data object to JSON, no matter what? Does anyone know how to work around this behavior? If I could prevent the automatic JSON conversion of the data object and do the conversion myself, that would be helpful.
This is causing issues with an API endpoint expecting integers to the point where I'm not able to use the API.
Posted by Tobias Geisler over 4 years ago
Problem uploading photos
I go to upload a photo (both png and jpg versions) and it never allows me to upload them. Minutes before this problem occurred, I was uploading photos no problem. What might be the issue and how do I fix it?
Posted by Mikayla Montoya over 4 years ago
Section and filters
Does sections support filters? How do can I limit size of characters in text attribute of section?
Posted by Filip Strahija over 4 years ago
How do I reach you
Part of my website no longer works. How do I talk to you
Posted by Cheryl Pollard over 4 years ago
Pulling content from published site
I've found that I've been able to push content without a problem, but i've just updated a few images through the control panel. I can see that when I `bundle exec wagon sync production`, the images are transferred locally. For example, "/samples/_production/content_entries/big_gun.jpg", and data/production/content_entries/background_images.yml is updated.
But for some reason it does not actually appear in the local dev site as it does in production. I tried using the environment production with wagon, which makes the image appear, but other content that appears in production is then not present.
How can I bring all production content to appear in my local environment for development?
This is with wagon 3.0.0.rc0.
Posted by Cory Logan over 4 years ago