Welcome to the Locomotive V4 developer hub. You'll find comprehensive guides and documentation to help you start working with Locomotive V4 as quickly as possible, as well as support if you get stuck. Let's jump right in!
Reproduction Steps: 1. `wagon generate content_type books title: string demo: text picture: file` 2. Deploy Changes 3. Create Entity in CMS 4. Synchronize content including data 5. Deploy content_entries Data: books.yml ```yaml - Draco title: Draco demo: '<img title="Screen_Shot_2019-04-08_at..." alt="undefined" src="/samples/assets/Screen_Shot_2019-04-08_at_12.56.14_PM.png">' picture: "/samples/content_entries/Reveal_ICS_MA_240.png" ```
Posted by Carlos Olson about a month ago
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 [email protected]:/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/[email protected]/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/concerns/request.rb:36:in `do_request' /usr/local/rvm/gems/[email protected]/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/concerns/request.rb:15:in `put' /usr/local/rvm/gems/[email protected]/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/current_site.rb:13:in `update' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_site_command.rb:27:in `persist' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:34:in `block in _push' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `each' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `_push' /usr/local/rvm/gems/[email protected]/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/[email protected]/gems/activesupport-4.2.11/lib/active_support/core_ext/time/zones.rb:48:in `use_zone' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:24:in `_push_with_timezone' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:18:in `block in push' /usr/local/rvm/gems/[email protected]/gems/activesupport-4.2.11/lib/active_support/notifications.rb:166:in `instrument' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:50:in `instrument' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:16:in `push' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:12:in `push' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:55:in `block in _push' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:84:in `block in each_resource' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:77:in `each' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:77:in `each_resource' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:54:in `_push' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:41:in `push' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:31:in `push' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon.rb:73:in `push' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/cli.rb:318:in `deploy' /usr/local/rvm/gems/[email protected]/gems/thor-0.19.4/lib/thor/command.rb:27:in `run' /usr/local/rvm/gems/[email protected]/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command' /usr/local/rvm/gems/[email protected]/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch' /usr/local/rvm/gems/[email protected]/gems/thor-0.19.4/lib/thor/base.rb:444:in `start' /usr/local/rvm/gems/[email protected]/bundler/gems/wagon-ea4c9da847ed/bin/wagon:12:in `<top (required)>' /usr/local/rvm/gems/[email protected]/bin/wagon:23:in `load' /usr/local/rvm/gems/[email protected]/bin/wagon:23:in `<main>' /usr/local/rvm/gems/[email protected]/bin/ruby_executable_hooks:24:in `eval' /usr/local/rvm/gems/[email protected]/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 2 months ago
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 4 months ago
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 5 months ago
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 5 months ago
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 8 months ago
I have a set of content entries that I want to use (US States) and I want to push only it to production. Everything I do, I either send all the content entries across all models, or nothing. Is sending only 1 table even possible?
Posted by David Cook 8 months ago
Hello, in my acces points i have define my domains in www.qualimetrie.com I want to activate the SSL for this domain and for both qualimetrie.com and www.qualimetrie.com. Can you help me ? Thank you best regards -- Bonjour J'ai configuré le nom de domaine sur www.qualimetrie.com dans la partie access points. J'aimerais activer le certificat SSL pour le domaine que ca soit avec ou sans les www. Pouvez-vous m'aider ? Merci cordialement, Morgan GELDOF Responsable communication Qualimetrie
Posted by Morgan Geldof 9 months ago
hello we write site template for locomotivecms v4.0.0.beta2 it is landing page and use bootstrap 4 https://github.com/EBII/site-templates/tree/v4.0.x/landing-v4 review or comment welcome which branch to pull request ? master one ? regards MonsieurB
Posted by MonsieurB 11 months ago
I tried installing using the instructions found in https://doc.locomotivecms.com/v4.0/docs/heroku . It seems it would be an easy change to switch ruby version to a version that Heroku supports: https://devcenter.heroku.com/articles/ruby-support#supported-runtimes Heroku returns this log: -----> Ruby app detected -----> Compiling Ruby/Rails Command: 'set -o pipefail; curl -L --fail --retry 5 --retry-delay 1 --connect-timeout 3 --max-time 30 https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/heroku-18/ruby-2.2.2.tgz -s -o - | tar zxf - ' failed on attempt 1 of 3. Command: 'set -o pipefail; curl -L --fail --retry 5 --retry-delay 1 --connect-timeout 3 --max-time 30 https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/heroku-18/ruby-2.2.2.tgz -s -o - | tar zxf - ' failed on attempt 2 of 3. ! ! An error occurred while installing ruby-2.2.2 ! ! This version of Ruby is not available on Heroku-18. The minimum supported version ! of Ruby on the Heroku-18 stack can found at: ! ! https://devcenter.heroku.com/articles/ruby-support#supported-runtimes ! ! Push rejected, failed to compile Ruby app. ! Push failed
Posted by Ron Maravilla 12 months ago
I am using an engine_overrides.rb initializer according to old Locomotive CMS docs to allow special theme extensions upload (json, XML etc..). After a little struggle with the engine_overrides.rb initializer in v3.4.1, I found out that method extension_white_list had been deprecated in favor of extension_whitelist in recent versions of CarrierWave. Changing the function name in engine_overrides.rb to extension_whitelist did solve the problem. I would be ok to write updated instructions on how to configure custom extension_whitelist in Locomotive if needed (just point me where).
Posted by Charles about a year ago
Hi, I cannot seem to find how not to display untranslated pages. If the page is not translated it should not be accessible and visible in the menu, but instead I get the page in default language. Is there some setting to change this behavior? In fact I would even need possibility to hide the page if translation exists but it is not finished yet. Thanks
Posted by Toni Milovan about a year ago
Hi This might be really obvious but I don't get it - it all works perfectly, I had no problems installing both locally and remotely. When I create a new site and attempt to add media it throws that error. > nil is not a valid asset source the remarkable thing is that I can even see the file in the file system, additionally if you upload an image directly as a content type - that works perfectly as well. To further confuse matters, uploading assest to my local engine works perfectly fine as well! Hope somebody can help! MB
Posted by mouseball about a year ago
this is first deployement of shopinv and deploy template that work in wagon. any idea ? Extracted source (around line #67): ] else raise InvalidURIError, "bad URI(is not URI?): #{uri}" end end does proxy can use https or need to be set by locomotive to force https ?
Posted by MonsieurB about a year ago