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!
Hi. First, thanks for the awesome job you do with LocomotiveCMS! I'm building a new website using locomotive. It has the regular navigation header with some nested links. I could figure out how to nest menu items, but I think the docs could be improved in this topic. Anyway, my question is related with internationalisation. When defining a nested menu and deploying, only the first top items are showed in the secondary languages. For instance: If I'm creating this structure: - Features - Testimonials - Hosting - Personal - Freelancer - Agency - Enterprise - Documentation For the default language (EN) it seems right, both in the editor and the preview. But for the secondary language I'm only seeing this structure in the editor: - Features - Testimonials - Hosting - Documentation Because I don't understand the difference between global_content and default section's properties, I've been trying both with similar results. Can anyone help with that? Thanks!
Posted by David G. 13 days ago
I want to make my own custom subscription-based website in the future, and right now I'm just in the research phase on which method/software to use as I don't want to use woocomerse or teachable. Can I make a subscription-based website in locomotive?
Posted by Bianca 2 months ago
I've already read this question (https://doc.locomotivecms.com/discuss/5f4f4c6f7b7bb5002a75e8f5) which deals with site-wide search, and this question (https://doc.locomotivecms.com/discuss/574370bc6b0c5c0e00099b4d) which is talking about searching content entries in the Back Office. What I want to do is create a search form to filter content entries on the front end. I'm using the hosted version of Locomotive CMS. From what I can tell there is a site-wide search available but it requires an Angolia account (https://github.com/locomotivecms/search). I have found this GitHub thing (https://github.com/Papipo/locomotivecms-search) but I can't tell if this is something that I can use in the hosted version of Locomotive CMS.
Posted by Luke Grayson 2 months ago
It is written [here](https://doc.locomotivecms.com/docs/json-definition#setting-types) that it is possible to set up a select type for a section setting. I'm trying to use it but it is not specified how to define the select options. Given [this code](https://github.com/locomotivecms/engine/blob/c83a72755ab4da55c7749cacf9cdc749f7e7fce9/app/javascript/src/locomotive/editor/inputs/select.js#L16) it seemed that I had to use an `options` array attribute so i set it up like that : ``` - label: Afficher id: display type: select options: - value: 'tout le monde' - value: 'en activité' - value: 'plus en activité' ``` This is almost working : In the UI editor I see a 3 options select list, but the values i set up are not displayed. Can you please telle me how to make it work ? Thanks !
Posted by Grégoire Colson 3 months ago
I tried to implement a menu section as suggested [here](https://doc.locomotivecms.com/discuss/603f8aa0a0b7aa004f7bb65a). I'm using the attribute `blocks_display: tree` for the section, but it does not seem to work. The list of blocks in the editor UI is still linear and does not look like a tree. I can't even access any of the blocks I created inside my liquid template using `section.blocks_as_tree`. `section.blocks` seems to work. Can somebody give me an example of a working section using `blocks_display: tree` ? Or maybe i understood something wrong ? Thanks !
Posted by Grégoire Colson 3 months ago
Hi, I just changed a field name of one of my content types from "location_name" to "name". I also changed every reference to "location_name" in the others files, and especially in data files, to avoid issues. Nevertheless when i try to deploy my site locally this error show up : ` Resource invalid: entries_custom_fields is invalid, #0: Label is already taken` The error seems to alert about the label attribute of the field, as if it was trying to create a new field instead of overwriting the existing one. If it's the case it makes sense that there is a conflict with the already existing field with the same attributes. But it seems really strange to me not to be able to edit fields in some files without breaking everything...
Posted by Grégoire Colson 3 months ago
My pages include multiple sections that i'd like to reference in the menu as sub-links (anchor links, with #) of the pages links. Example : I have a "Home" Page with 3 sections with ids "section-1", "section-2" and "section-3". In the menu I display the main "Home" link and when hovering this link i'd like to display 3 anchor links to go directly to the corresponding sections. Is it possible ? The "page" liquid drop doesn't seem to include the page content of sections, so I wonder how to achieve this. Thanks ! Grégoire
Posted by Grégoire Colson 3 months ago
Hi, I'm struggling at the very beggining of the "Quick Start" Guide, as I simply cannot install the latest version of wagon (3.0.5 at the time i'm writing this). I'm using Ubuntu 20.04 and I installed ruby following this guide : https://gorails.com/setup/ubuntu/20.04 Then I try to install wagon using gem install locomotivecms_wagon but it installs the version 1.5.8. So I try forcing the latest version using gem install locomotivecms_wagon -v 3.0.5 but i got the following error : ERROR: While executing gem ... (NoMethodError) undefined method `request' for nil:NilClass Can somebody help me here ? I really don't understand what's going on. I never experienced such issues with other standalone gem installations. Thanks a lot, Grégoire
Posted by Grégoire Colson 3 months ago
Since v3 or v4 sitemap.xml is populated by pages which are tagged as "listed". In previous version we used to use this attribute to know if the page should be listed in the menu or not. But now we would like to send to sitemap all pages and keep using "listed" for our menu. Is it possible to add a new attribute to split these functionality from the dashboard ?
Posted by RB 4 months ago
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 6 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 11 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 11 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 12 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 12 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 about a year 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 year ago