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, We currently have our website running on Heroku using the new wagon and professional dyno (www.careerseekers.org.au) . After a day or two, the Theme Assets on the wagon dissappear, and shows our public website without any style or theme, like its just the plane HTML being rendered. Is this a bug on the wagon? or would this be an issue on Heroku?
Posted by Michael Macahilig 3 years ago
Has anyone successfully managed to include font-awesome in a wagon project (outside of using the built-in bootstrap theme that includes font-awesome)? I've tried using the official Font Awesome gem (https://github.com/FortAwesome/font-awesome-sass) with no success. Including just `font-awesome` in my application scss looks for the fonts at the path `/fonts/font-awesome/`, which gives a 404. Including `font-awesome-sprockets` as well gives the error `Custom asset_path helper is not implemented`.
Posted by Jonathan Green 3 years ago
In my locomotive site, if I create a user under "general settings", there's no password field to set the user's password. If I edit an existing user, no password field there either. If I edit my own account, there is a password field and it works.
Posted by Josh Santangelo 3 years ago
I have a field type which is currently a "select", which works fine. I'd like to display it as a series of radio buttons instead. Is that possible? I'm looking at the field types list and don't see anything about radio buttons. https://locomotive-v3.readme.io/docs/define-a-content-type
Posted by Josh Santangelo 3 years ago
Hello, I was experimenting with the demo using the blog template as a solution for a (non-technical) client wanting to post their own blogs. I noticed that when I upload a large image to a blog post it overlaps the edges of the post/page. This is especially apparent when resizing the window for mobile (so setting a width within the image tags doesn't solve the issue). The images don't take into account the size of the page or container they're in at all. Is there something I'm missing or doing wrong? Also, is there a simple way to add image gallery functionality or resizing images within the WYSIWYG editor a-la-Wordpress? Many thanks
Posted by Dino 3 years ago
I've a problem with what a think to be a very common task. I want to filter content entries by the value selected by the user; and if the user doesn't select any value, I want to show all content entries. So, let's say I have a Product model, with a "name" and "category" fields. Name is a string field, and category is a select field. Given the above, the following code DO what I expected: {% assign requested_product_name = '/' | concat: params['requested_product_name'], '/' %} {% with_scope name: requested_product_name %} {% for product in contents.products %} /* PREVIEW PRODUCT */ {% endfor %} {% endwith_scope %} i.e. it show all products if requested_product_name parameter contain the .* regex. But if I use the category field, the regex dosn't work anymore! For example, if category field has two select_options, let's say "books" and "sunglasses", then the following code: {% assign requested_product_category = '/' | concat: params['requested_product_category'], '/' %} {% with_scope category: requested_product_category %} {% for product in contents.products %} /* PREVIEW PRODUCT */ {% endfor %} {% endwith_scope %} show only the entries belonging to the "books" category (the first select option specified). The question is: how to show all entries when the user doesn't pick a filter value in the UI? I can use some "if/then" logic, but with multiple filters, the code can become very lengthy and confusing.
Posted by Riccardo 3 years ago
We have a requirement to set the canonical link in every page of the site that we have developed using locomotive CMS. I initially thought that we can set a custom value in YAML header of every page and access it in page drop. But that is not possible. So is there is any solution for this please?
Posted by Nanditha 3 years ago
We're running http://www.silvesco.com/ on the new Locomotive CMS. We've got some old .php pages showing up in Google search we'd like to do 301 redirects for. When we route /who-we-are.php to /about it doesn't work. When visiting /who-we/are.php we get a 403 error with "nginx" text. Any suggestions for how we might be able to get those redirects in place?
Posted by Tyler Peterson 3 years ago
I have ui_enabled active for all relationships on our sites. For *has_many* relationships, the `Add a new one` button is displayed. For many_to_many relationships, it never displays. This makes the whole thing extremely user unfriendly. E.g. if I want to add a new picture to an album, I have to upload it from the images page which is a click fest. Shall I look for errors on our side or is this a common misbehavior?
Posted by Tobias Geisler 3 years ago
I have something like this: ``` slider: fields: slider_text: type: string slider_bild_1 type: file ``` (metafields_schema.yml) On wagon, this works perfectly. On the engine, I get this (self-hosted and on locomotivehosting): ``` I, [2016-07-16T17:51:02.759050 #3087] INFO -- : [LocomotiveCMS] [ApplicationError] #<NoMethodError: undefined method `slider_bild_1?' for #<Locomotive::CurrentSiteMetafieldsHelper::SchemaGroup:0x00000005 6cbe20>> I, [2016-07-16T17:51:02.762500 #3087] INFO -- : Completed 500 Internal Server Error in 87ms F, [2016-07-16T17:51:02.772287 #3087] FATAL -- : NoMethodError (undefined method `slider_bild_1?' for #<Locomotive::CurrentSiteMetafieldsHelper::SchemaGroup:0x000000056cbe20>): ``` (log excerpt from self-hosted engine) => The file field causes an error (the text field alone works). *Since it's an image field, I changed it to `type: image`, and this seems to solve the issue.* However, I can't get `type: file` to work.
Posted by Tobias Geisler 3 years ago
``` {% with_scope _slug: "technology" %} {% assign section = contents.article_sections.first %} {% endwith_scope%} {% for subsection in section.subsections %} .category-block %h2 {{ subsection.subsection_name }} .articles {% for article in subsection.libraryarticles %} %a.article{:href => '/articles/{{ article._slug }}'} {% endfor %} {% endfor %} {% endblock %} ``` With two models, subsections and articles. In locomotive 2.5.7, the order of the articles would be determined by how they were ordered within the subsection. In locomotive 3.0, the order of the articles is being determined by how they are ordered in the main model page that shows all the articles. Completely ignores the order that they are assigned in the edit page for a subsection. Subsections and articles are both set to order_by manual. Not that it should matter for subsections. Is there a way in the model declaration to explicitly say that order in the many_to_many relationship matters? Or is there some magical filter/sort_by that I don't know about? Thanks!
Posted by Jiexi Luan 3 years ago
Hello, I'm trying to add some new functions inside the admin site, showing a new section in the left sidebar. Any help is welcome =D. I saw the metafields configuration that create a new section but this is a internal configuration. I want to do something like that but with my own database information. Thanks ;)
Posted by Lester 3 years ago
Neither on the engine nor on wagon, this ordering seems to work: ``` {% with_scope start.gt: now, order_by: 'start.asc' %} {% assign future_events = contents.events %} {% endwith_scope %} ``` The order as defined in events.yml is start.desc, which is also the order I get regardless of the order defined in the with_scope tag.
Posted by Tobias Geisler 3 years ago
My hosted locomotiveCMS is under domain blog.mydomain.com. I have mydomain.com/blog maps to blog.mydomain.com for SEO purpose. (via reserve proxy) However, url generated by locomotive will look something like this mydomain.com/posts/post-slub, obviously these links won't work since they are hitting my main app. I want them to be mydomain.com/blog/posts/post-slub. What will be the best way to do this? Thanks
Posted by Eric 3 years ago
It worked for us in v2, but in a project now in v3, we can't get fixed:true to work on editable elements such as editable_text or editable_file. ### The setup In our `index.liquid` file, we have something like this: ```liquid {% block 'site_settings' %} {% block 'map' %} {% capture map_text %}{% editable_text 'map', format: raw, fixed: true %}..{% endeditable_text %}{% endcapture %} {% endblock %} {% block 'slider' %} {% capture slider_text %}{% editable_text 'slider_text', format: raw, rows: 3, fixed: true %}...{% endeditable_text %}{% endcapture %} {% capture slider_image_1 %}{% editable_file 'slider_bild_1', fixed: true %}slider/home-4.png{% endeditable_file %}{% endcapture %} {% endblock %} {% endblock %} ``` We're not using site_metafields because we haven't gotten them to work yet. Even though we're using fixed: true, those editable elements appear on the editor for all pages that inherit from the index. Any ideas on how to get the correct behavior working?
Posted by Tobias Geisler 3 years ago
From the v3.1 release notes I take it that the feature still exists, but only works under certain conditions: Wagon doesn't stop the whole site deployment if a JS/CSS can't be minified. What are those conditions/what can I do to make the minification work?
Posted by Tobias Geisler 3 years ago
Hi, i got a problem while trying to filter my blog entries through with_scope. In wagon my filter system it worked quiet well. But when i deploy it to my locomotive site it won't filter these entries anymore. Here is my Code: {% assign currenttag = params['tag'] %} {% with_scope tags: currenttag %} {% paginate contents.blog by 5 %} {% for post in paginate.collection %} <div class="blog-material"> <img class="blog-image" src="{{ post.image.url }}"> <div class="blog-body clearfix"> <h5><a href="{{ post._slug }}">{{ post.title }}</a></h5> <p>{{ post.text | truncatewords: 50 }}</p> <a href="{{ post._slug }}" class="button float-right">Weiterlesen</a> </div> </div> {% endfor %} <div class="row content-top-min content-bottom-min"> <div class="large-12 columns text-center"> {% if paginate.previous_page %} <a href="?tag={{currenttag}}&page={{paginate.previous_page}}" class="button arrow"> <i class="material-icons">arrow_back</i> </a> {% endif %} {% if paginate.next %} <a href="?tag={{currenttag}}&page={{ paginate.next_page }}" class="button arrow"> <i class="material-icons">arrow_forward</i> </a> {% endif %} </div> </div> {% endpaginate %} {% endwith_scope %}
Posted by Tobias Zoll 3 years ago