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!
Hello! I use a lot of SVGs throughout my page. If authors visit the Assets page Locomotive crashes. It seems that Locomotive tries to resize the images and completely freezes. See this screenshot: https://drive.google.com/file/d/1Gitjbgk9_EbZYUhvOdXmkd7PAFVAjYEt/view?usp=sharing
Posted by Max Engel 18 days ago
Hi! I recently discovered Locomotive CMS and I'm quit happy with it. But I'm missing the option to define custom fields for all pages. (Every page has the fields, but they are individually per page) For Example: Every page should have an open graph image and an open graph description. (The authors should be allowed to edit them) It there a way to define metafields per page? It would be nice to define own tabs, additionally to content, settings and seo. Another solution would be to create own SEO fields. Thanks in Advance
Posted by max 21 days ago
For our lazy loading script, it would be nice to allow any HTML attributes in the WISIWYG editor (the editor seems to cut any attributes that aren't whitelisted). For example, we'd like to be able to save an image tag like ``` <img data-lazy="some/url"> ``` Has anyone made this happen?
Posted by Tobias Geisler about a month ago
Mongo::Error::NoServerAvailable (No primary server is available in cluster: #<Cluster topology=Unknown[localhost:27017] servers=[#<Server address=localhost:27017 UNKNOWN>]> with timeout=30, LT=0.015. The following servers have dead monitor threads: #<Server address=localhost:27017 UNKNOWN>):
Posted by zr0243 about a month ago
i am trying to add a member from my team to our production site so she can upload content. when i tried to add the user it said her email is already in use, but i didn't see the user on the list of administrators. I thought maybe it was because the user was in our QA site already so i removed the user from our QA site and tried again. I got the same message that the her email was in use. When i went to add the user back to our QA site i got the same message again saying the users email was already in use. Is there a way to remove the users email completely or reset the user so we can get them back in and able to upload content to the site?
Posted by Kaleb Yurchak 2 months ago
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 4 months 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/r[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 5 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 7 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 8 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 8 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 11 months ago