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!
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 4 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 4 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 4 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 4 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 4 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 4 years ago
What is the full list of options for "wagon sync -r" command? "Only pull the resource(s) passed (pages, content_entries, translations) in argument" is not all, there is also site i.e. but is there also an option to sync ContentAssets i.e.? Thanks
Posted by Tim Henze 4 years ago
Helle Support, every time we try to clone or backup our site from server to local we get "Pulling ContentAssets # Error description: undefined method `<' for nil:NilClass" and the pull is stopped. All pulling before are fine, "Pulling Site Pulling Pages Pulling ContentTypes Pulling ContentEntries Pulling Snippets Pulling ThemeAssets Pulling Translations" but the ContentAssets crash. What can we do to clean up the server so we get a working clone? Thanks
Posted by Tim Henze 4 years ago
I've got a content block defined as markdown, and it's working fine on the production server, but when viewing locally it's not converting the markdown: ``` --- title: Home page slug: index position: 0 listed: true published: true is_layout: false editable_elements: content/content: "# Content of the home page goes here\r\n\r\nThis is a **para**\r\n\r\nThen what happens?\r\n\r\n- something \r\n- something else" --- {% extends 'layouts/default' %} {% block content %} {% editable_text content, format:'markdown' %} # Content of the home page goes here This is a para {% endeditable_text %} {% endblock content %} ``` Neither the default content or the editable elements bit shows up as HTML, but does on the live site.
Posted by Guy Bowden 4 years ago