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'm an admin trying to debug something going on the locomotive CMS for a client. The issue I'm facing is that after clicking a link on the preview/mysite, it redirects to the login screen for https://station.locomotive.works/_app/sign_in All of the pages' published status is set to "published" in the CMS so I'm really not sure why this behaviour is occuring. I would like to take the site live (point the domain to locomotive), but I'm not sure if the behaviour would carry over, and if it does that would be a significant problem. I would be happy to provide the exact website in an e-mail, but let me know if this behaviour is intended across your hosted sites, or might be case-specific to my site for some reason. Thank you
Posted by Ryon 7 days ago
I have noticed that whenever I change default values in a section or config files like translations.yml then "wagon deploy" to my site, the values on the site do not change. This makes sense from a content management standpoint, but there are times where it would be convenient to forcibly reset these values. For example, I recently changed a large number of translations in my yml file, and it would be a chore to go through and update them all by hand in the back office. Is there any way to force the site to revert to the default values? I would like to be able to reset, for instance, just one page or just the translations without nuking the whole site.
Posted by Dawson Coleman about a month ago
I'm trying to delete a section. I've made some breaking changes (e.g. changing block types, etc) and want delete the section and re-deploy. I tried running `bundle exec wagon delete staging -r sections -v` but received a garbled error message including the following: *"Resource must be one of page,content_type,snippet,translation if you pass an identifier OR be one of content_types,snippets,theme_assets,translations if you want to delete all the items of that resource. (ArgumentError)"* Is it possible to delete a section?
Posted by Luke Grayson about a month ago
I've set up a number of metafields with `type: image`. They work as expected. However, if I add an image to a particular field and then decide I no longer want an image applied to that field, there is no way to delete the image. I can delete the image from the Assets section of the Admin panel ("Back Office") but what if I don't want to do that? What if I want to retain the image to use elsewhere but simply don't want it applied to my metafield? There doesn't appear to be a solution at this point.
Posted by Luke Grayson about a month ago
The guide [Create a contact form][1] briefly mentions that you can use the JSON API by adding `json: true` to the options. It gives an example response, but not much more than that. In my option the guide is missing some key information. It doesn't tell me if I am responsible for making the request via JavaScript or if the Rails or LocomotiveCMS is doing this for me. If the latter is the case it should also describe how to handle the response. Eg. What event should callbacks be attached to? I'd like to submit some data via an AJAX request but am currently unsure how to do this. I'd like to know the two things mentioned above. 1. Must I initiate the AJAX request myself or is this done by the framework/CMS? 2. If I don't have to initiate the request, how do I attach a callback to handle the response? [1]: https://doc.locomotivecms.com/docs/create-a-contact-form#notes
Posted by Johan Wentholt 3 months ago
I don't get what methods are accessable in the liquid. When I try for example to access the listed attribute of an page it seems to be empty. Is there in any way a full list of all methods that I can call from the liquid code?
Posted by Patrick Hausa 4 months ago
Hi, I have a bunch of Locomotive instances running on Heroku. Unfortunately the MongoLab extension is being phased out by November (they recommend migrating by September) and Compose no longer supports MongoDB 3.4. I am having difficulties finding a cost-effective cloud solution for that version of MongoDB, given that it has been marked end of life since January of this year. Do you have any suggestions? Do you plan on updating Engine to support a more recent version of Mongo? Thanks in advance
Posted by Simon Pinkas 4 months ago
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 5 months 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 5 months 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 6 months 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 6 months 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 7 months ago
Pushing Site persisting MyPortfolio [failed] Resource invalid: metafields_schema Invalid metafields_schema: "767: unexpected token at ''". Check it out on http://jsonlint.com Resource invalid: metafields_schema Invalid metafields_schema: "767: unexpected token at ''". Check it out on http://jsonlint.com /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_coal-1.0.0/lib/locomotive/coal/resources/concerns/request.rb:36:in `do_request' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_coal-1.0.0/lib/locomotive/coal/resources/concerns/request.rb:15:in `put' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_coal-1.0.0/lib/locomotive/coal/resources/current_site.rb:13:in `update' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_site_command.rb:25:in `persist' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:34:in `block in _push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `each' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `_push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:25:in `block in _push_with_timezone' /home/jerome/.rvm/gems/ruby-2.6.3/gems/activesupport-4.2.11.1/lib/active_support/core_ext/time/zones.rb:48:in `use_zone' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:24:in `_push_with_timezone' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:18:in `block in push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/activesupport-4.2.11.1/lib/active_support/notifications.rb:166:in `instrument' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:47:in `instrument' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:16:in `push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:12:in `push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_command.rb:55:in `block in _push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_command.rb:84:in `block in each_resource' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_command.rb:77:in `each' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_command.rb:77:in `each_resource' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_command.rb:54:in `_push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_command.rb:41:in `push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/commands/push_command.rb:31:in `push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon.rb:73:in `push' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/lib/locomotive/wagon/cli.rb:308:in `deploy' /home/jerome/.rvm/gems/ruby-2.6.3/gems/thor-0.19.4/lib/thor/command.rb:27:in `run' /home/jerome/.rvm/gems/ruby-2.6.3/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command' /home/jerome/.rvm/gems/ruby-2.6.3/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch' /home/jerome/.rvm/gems/ruby-2.6.3/gems/thor-0.19.4/lib/thor/base.rb:444:in `start' /home/jerome/.rvm/gems/ruby-2.6.3/gems/locomotivecms_wagon-2.0.1/bin/wagon:12:in `<top (required)>' /home/jerome/.rvm/gems/ruby-2.6.3/bin/wagon:23:in `load' /home/jerome/.rvm/gems/ruby-2.6.3/bin/wagon:23:in `<main>' /home/jerome/.rvm/gems/ruby-2.6.3/bin/ruby_executable_hooks:24:in `eval' /home/jerome/.rvm/gems/ruby-2.6.3/bin/ruby_executable_hooks:24:in `<main>'
Posted by Jeroen van Eisden 9 months ago