Discussions

Ask a Question

station.locomotive.works - site returning error

After I removed one of the languages from the site settings. I got an error which referred me to contact the administrator. I can't open the site anymore to delete it.

BUG: Locomotive crashes due to SVG resize

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

Allow custom HTML attributes (data-...)

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?

Error: Mongo::Error::NoServerAvailable

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>):

User guide

Hi, Do you have a user guide for the actual usage of the CMS? I mean the daily usage, content publishing, etc.

How to add custom extensions (gems) with LocomotiveCMS hosting

Is it possible to add custom gem extensions to the engine while using Locomotive CMS hosting solution. And if so, how can it be done ?

Automatic Backup

I see we have automatic back-ups set up for our site on Locomotive, but the last one completed was in 2018 - How can we set this up to automatically back-up the site daily again? It looks like it is all set to do so, but just isn't.

No such file error on Deploy field types text and file

Reproduction Steps: 1. `wagon generate content_type books title: string demo: text picture: file` 2. Deploy Changes 3. Create Entity in CMS 4. Synchronize content including data 5. Deploy content_entries Data: books.yml ```yaml - Draco title: Draco demo: '<img title="Screen_Shot_2019-04-08_at..." alt="undefined" src="/samples/assets/Screen_Shot_2019-04-08_at_12.56.14_PM.png">' picture: "/samples/content_entries/Reveal_ICS_MA_240.png" ```

Cannot push wagon to production instance

Hello, I was wondering if someone could help me out. I am trying to push a wagon from a staging instance to a production instance but getting an error when dpeloying the wagon. I am getting the following error root@XXXXXXXXXXX:/home/user/dhr-wagon# bundle exec wagon deploy live -v Pushing Site persisting Wagon [failed] Locomotive::Coal::Error # Error description: Locomotive::Coal::Error # Backtrace: /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/concerns/request.rb:36:in `do_request' /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/concerns/request.rb:15:in `put' /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/locomotivecms_coal-1.4.0/lib/locomotive/coal/resources/current_site.rb:13:in `update' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_site_command.rb:27:in `persist' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:34:in `block in _push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `each' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `_push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:25:in `block in _push_with_timezone' /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/activesupport-4.2.11/lib/active_support/core_ext/time/zones.rb:48:in `use_zone' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:24:in `_push_with_timezone' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:18:in `block in push' /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/activesupport-4.2.11/lib/active_support/notifications.rb:166:in `instrument' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:50:in `instrument' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:16:in `push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:12:in `push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:55:in `block in _push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:84:in `block in each_resource' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:77:in `each' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:77:in `each_resource' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:54:in `_push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:41:in `push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/commands/push_command.rb:31:in `push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon.rb:73:in `push' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/lib/locomotive/wagon/cli.rb:318:in `deploy' /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/thor-0.19.4/lib/thor/command.rb:27:in `run' /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command' /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch' /usr/local/rvm/gems/ruby-2.3.0@wagon/gems/thor-0.19.4/lib/thor/base.rb:444:in `start' /usr/local/rvm/gems/ruby-2.3.0@wagon/bundler/gems/wagon-ea4c9da847ed/bin/wagon:12:in `<top (required)>' /usr/local/rvm/gems/ruby-2.3.0@wagon/bin/wagon:23:in `load' /usr/local/rvm/gems/ruby-2.3.0@wagon/bin/wagon:23:in `<main>' /usr/local/rvm/gems/ruby-2.3.0@wagon/bin/ruby_executable_hooks:24:in `eval' /usr/local/rvm/gems/ruby-2.3.0@wagon/bin/ruby_executable_hooks:24:in `<main>' Seems like the API on the remote live server is not working properly. How can I check if API access is working? Thank you for your help,