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!
When I set default images for the `editable_file` tag as suggested [here](https://locomotive-v3.readme.io/docs/tags#section-editable_file), there doesn't seem to be a nice way to read out the editable_file url: for the default image, I need the `theme_image_url` filter, if I set the editable file in the backend My current solution is to check wheter the url contains certain strings and decide wheter to apply the filter or not: ``` {% if person_sidebar_img contains 'pages' or person_sidebar_img contains 'content_entry' %} <img class="img-responsive" src='{{ person_sidebar_img }}'> {% else %} <img class="img-responsive" src="{{ 'default/teacher.png' | theme_image_url }}"> {% endif %} ``` This is of course not necessarily update-safe and seems redundant. Any ideas on how to handle default and uploaded images at the same time? (Of course, on wagon this problem doesn't exist, since the default url works without the theme_img_url filter.)
Posted by Tobias Geisler 3 years ago
Three days of an unanswered question about images not being available from Assets. I've had to move my assets to S3, which I was trying to avoid. Asset servers that disappear when their certificates expire. And guess what? Clicking your "status" link reveals that the certificate for that server has expired to, but nothing is done. You're a hosting company? Tried following your instructions to move my site to Heroku. Although the site runs locally and on your servers (at least for me), following your instructions on deploying to heroku resulted in a crashed app on launch, and no information that could be used in the logs. Your suggestions in the docs is to mod my config pages for the app, but there are none. Repeated inquiries why only I can see my site pages, and others can only see the home page -- unanswered. Eighty percent of questions here unanswered, and unacknowledged, months after they were asked.
Posted by Dan Donaldson 3 years ago
I can't get the image that is assigned to the background of pane in my site to appear. The image is in the image assets on station.locomotive.works temporary hosting. The image url is passed in via a variable assignment this way: {% block 'hero1' %} {% assign hero_url1 = 'incubator.jpeg' %} {% assign hero_headline1 = "Our Programs" %} {% assign hero_alt_head = ""%} {% assign hero_alt_kicker = "" %} {% include 'hero_block' %} {% endblock %} the first assignment is the one in question. In the block, it looks like this: <div class="parallax-quote parallaxBg" style="background: url('{{ hero_url1 | theme_image_url }}') 10% 0 repeat fixed; background-size: 100%;"> … </div> And when rendered, it appears this way: <div class="parallax-quote parallaxBg" style="background: url('https://assets.locomotive.works/sites/5981d7e6a2f4222fdc5e3c88/theme/images/incubator.jpeg?1501697919') 10% 0 repeat fixed; background-size: 100%;"> … </div> So all seems good. But the image does not appear, and I have not got an easy way to determine if the asset is being served, since pasting the url directly into the browser location yields a complaint that it isn't a cached asset request... What is going on here?
Posted by Dan Donaldson 3 years ago
Hi, Based on the contact form guide I've made a form that adds some details, and tries to add associated data (through checkboxes). The form works fine until I check and boxes, then I get an "undefined method `association_ids=' for #<Locomotive::API::Forms::ContentEntryForm>" Is this possible through public submission? Thanks Lawrence
Posted by Lawrence Nicholson 3 years ago
Hello, How do I get the current/active model in the `root.liquid` layout? Right now when I add custom text (SEO title, meta keywords and meta description) it is inheriting from `pages`, and I want it to be customised for the current model. I can call the different models using `{{ models.references.first.meta_keywords }}` so I know the information is available, but need to call only the active/current model
Posted by Linda Bergen 3 years ago
I'm trying to incorporate a library that has javascript, css and fonts that are all expected to be in the same folder. Can I put all of the assets together in a folder and then refer to them in my liquid template using a specific path? The docs don't cover this scenario. Is it even possible? If not, is there some other way to accommodate this scenario?
Posted by Scott Wolff 3 years ago
I'm wondering how do I backup my site and content as I'm guessing the edits are in Mongo? I've tried using the backup command with wagon 2.2.0 but I always get this error: Locomotive::Coal::UnauthorizedError Does this backup (if it works) give me a full backup with all site content? If so how to I restore the backup?
Posted by Chris Brown 3 years ago
Is it possible to deploy all environments from your config file in one command? So to do something like: bundle exec wagon deploy *allenvs* -r theme_assets -f functions.js -v or should I need to list them like: bundle exec wagon deploy dev live_1 live_2 -r theme_assets -f functions.js -v Are any of those even possible? Thank you for your answers!
Posted by Cristina 3 years ago
Hello I'm having an issue where the newest version of our site is having really bad response time. When comparing the old version and new version using mongostat, it seems that the amount of queries being performed is much higher on the new version. This is even when just accessing our home page. To clarify the homepage of both sites are exactly the same. The response time gets so bad when hosting that our server tends to crash. If anyone can assist us with this problem it would be greatly appreciated.
Posted by Mario Gracia 3 years ago
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.
Posted by Niccole 3 years ago
I am coming from a Wordpress background and am looking into Ruby based CMS's. Locomotive seems to be on the top of list as of now. I am wondering if it is possible to have flexible fields in a content type. I call them flexible fields because I am used to the Advanced Custom Fields plugin for wordpress and using their terminology. Here is a link to the flexible content field https://www.advancedcustomfields.com/resources/flexible-content/ The idea here is that I as the developer can build what I like to call modules. For example, an image slider, a testimonial section, a recent blog post section and many many more types of modules. With these modules in place any layout can be built for a page / post / or any other kind of content type. So my question is, is something like this possible with Locomotive. I would like the authors of the site to be able to create a new page, select and order the "modules" they want on that page and fill in the data for those certain modules.
Posted by Cody 3 years ago