Discussions

Wagon: 2.4.1 We currently have a problem where we cannot edit add a field to a content type. We are able to edit details about current fields but when it comes to adding a _new_ field, the `deploy` command is not working for us. This site was handled by many other developers and has sat a bit stagnant. These are the steps we take: 1. Add a new field to a content type 2. Use command `bundle exec wagon deploy staging -r content_types -vvv` Should this not add a new field? We have come up with a workaround that is a bit inconvenient where we delete the content type and then re-add this. This also means we have to deploy all the data with it. If anyone is able to help us out with this issue, we'd be very grateful.

Anybody know how I can organize my file system better than having all the sections in the folder app/views/sections (i.e. split into multiple folders like: app/views/sections/folder1 && app/views/sections/folder2) When I put my sections into different folders, those sections don't show up in the User Interface

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 !

hi, I am triying to render a custom content type called posts in the index page, I choose HAML so I 'm getting this error: undefined local variable or method `contents' for # My code to render is: %ul - contents.posts.each do |post| %li = post.title regards

Hello, We use Locomotive to support our site and we received this email. Can you advise me on what this is or means? Important TLS Disablement Notice Your Payment Gateway ID: 823514 Dear Authorize.Net Merchant: As you may be aware, new PCI DSS requirements state that all payment systems must disable early TLS by 2018. Transport Layer Security (TLS), is a technology used to encrypt sensitive information sent via the Internet. TLS is the replacement for Secure Sockets Layer (SSL). In preparation for this requirement, Authorize.Net plans to disable TLS 1.0 and TLS 1.1 on the following dates: Sandbox: COMPLETE Production: September 18, 2017 We have disabled the sandbox in advance of production to allow you and your developer time to test your website or payment solution and ensure you are no longer using TLS 1.0 or 1.1 prior to September 18th. Please contact your web developer or payment solution provider, as well as your web hosting company, to confirm that they can support TLS 1.2 for your API connections. In addition, we plan to retire the 3DES cipher (a data encryption standard) in production soon. However, the date has not yet been finalized. We will notify you once it has. Please refer your developer or solution provider to our API Best Practices for cipher recommendations, details about TLS 1.2 platform support, and other integration suggestions. Note: If you are not using the current version of your web browser, please take a few moments to upgrade it now. Browsers released prior to 2014 may not support TLS 1.2. You can check your browser's TLS support by visiting https://www.howsmyssl.com/. Thank you for your attention to this matter and for being an Authorize.Net merchant. Sincerely, Authorize.Net You have opted to receive Administrative and/or Technical Notices for your payment gateway account. To unsubscribe, log into the Merchant Interface and click Account from the main toolbar. Then click User Profile from the menu on the left. Select Edit Profile Information and uncheck the email types you do not want to receive. Click Submit to save any changes. For information on Authorize.Net communications and how we handle customer information, please see our Spam Policy and Privacy Policy. Copyright 2017. Authorize.Net. P.O. Box 8999, San Francisco, CA 94128-8999. All rights reserved. All other marks are the property of their respective owners.

I've been running into the "can't be blank" issue for relationships when pushing data to the engine a lot lately. This happens for relationships with _required:true_. So am I right in the assumption, that required relationships still haven't been implemented? Or how would I make them work?

Hi! If I try to access the 'created_at' property in a liquid tag it returns nil (I think). I've tested it both in my Wagon and in my CMS project. My gems: gem 'locomotivecms', '~> 3.0.0' gem 'locomotivecms_steam', '~> 1.0.0' gem 'locomotivecms_wagon', '~> 2.0.0' My custom (faq) content_type: https://dl.dropboxusercontent.com/u/16954780/Locomotive/faqs.yml Liquid template: https://dl.dropboxusercontent.com/u/16954780/Locomotive/faqs.liquid But if I try to access other properties like '_label, _permalink, ...' they returns the correct values. Thanks for any help!

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.