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!
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 2 days 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 27 days 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 about a month 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 about a month 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 about a month 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 2 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 2 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 4 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 5 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 5 months ago
Hello, i try to deploy my site-template landing-v4 but can not! i use my own instance of locomotive just install from rubygems and Wagon 3.0.3 wagon side : wagon deploy production -v bundle exec wagon deploy production -v # Error description: error # Backtrace: /usr/local/bundle/gems/locomotivecms_coal-1.6.0/lib/locomotive/coal/resources/concerns/request.rb:54:in `do_request' Locomotive side (locomotiveapp/log/developpment.log) Started POST "/locomotive/api/v3/tokens.json" for 127.0.0.1 at 2020-01-29 10:53:39 +0100 MONGODB | localhost:27017 | locomotive_development.find | STARTED | {"find"=>"locomotive_accounts", "filter"=>{"api_key"=>"xxxxxxxxxxxxx"}, "sort"=>{"_id"=>1}, "limit"=>1, "singleBatch"=>true, "lsid"=>{"id"=><BSON::Binary:0x69869658804180 type=uuid data=0x562c58165c7b43a9...>}} MONGODB | localhost:27017 | locomotive_development.find | SUCCEEDED | 0.255s NoMethodError (undefined method `[]' for nil:NilClass): grape (1.1.0) lib/grape/router.rb:163:in `cascade?' grape (1.1.0) lib/grape/router.rb:95:in `transaction' thanks for your help
Posted by MonsieurB 6 months ago