@patternpoints I built an Instagram client as Ruby-Gem.
I linked this Gem to my Locomotive page.
The Ruby-Gem serves as a plugin and provides a Liquid-Drop, with these drop I can display my Instagram Postings.
In this gem I would like to access the metafields. If I see it right, this only works with Coal?
I've just updated my locomotive engine from 2 to 4. Before update I could edit every page right inside of locomotive admin panel. But now every page, except the main one, says "No editable elements found".
Can it be related to migrations scripts? Is there a way to make all the content in all pages editable?
Thanks a lot in advance
settings in the definition.https://doc.locomotivecms.com/docs/json-definition
Hello all again. I've tried to get started with the new way of building Loco-sites with Sections. We're running latest master both server side and locally. I've followed the documentation on doc.locomotivecms.com regarding sections. I wanted to learn the basics with Sections and therefor I've tried to follow the examples that follow the generated section. These are the steps I've done:
- Created new fresh site in Loco production server administration.
- Cloned down the site to my computer.
- I noticed that
/app/assetswith necessary javascript-files were not created (even with generate section-command), so I ran the commandbundle exec wagon generate webpack. - I created new section
wagon generate section test. - I replaced all sample-file-references in
app/views/sections/test.liquidwith an existing image-filetest.png. - I added
{% sections_dropzone %}to index.liquid with examplesections_dropzone_contentas instructed in section-comment. - I deployed all to production server.
When I ran the server (wagon) locally, it works and shows expected data on index.liquid page/section.
When I access editor on production server for index.liquid (or 404.liquid) it just hangs and "Waiting for the preview pane to be ready" to finish. No errors in console or network. I have no access points domains yet and no redirects activated.
What have I've missed? Thank you in advance.
Hello,
Is there a way to bind the backend to a particular domain?
This so that admin.example.com/locomotive will serve up the backend but mysite.example.com/locomotive will not.
I was looking around in rails routing, but haven’t found routing based on the domain.
<script type="text/javascript">
var companies = [
{% for company in contents.company %}
{"name": "{{ company.name }}", "url": "{% path_to company %}"}{% unless forloop.last %},{% endunless %}
{% endfor %}
];
</script>
Bad URI: mongodb+srv://my-name:my-pass@my-atlas-cluster.mongodb.net/heroku_db
Invalid scheme. Scheme must be 'mongodb' or 'mongodb+srv'
MongoDB URI must be in the following format: mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]
Hi @arzvaak - there are different levels of administration. The documentation doesn't address it but it's described here: locomotivecms/engine#1286. You'll notice there appear to be a couple of "issues" where certain roles have access to things they shouldn't but in general it works.
Regarding themes, you'll have to set up your own or I believe @manuchap has a bunch he has set up.
Are you wanting to resell Locomotive CMS? There are a range of pricing plans available: https://www.locomotivecms.com/pricing (or you can set up your own instance and host it yourself as it is open source). We use the hosted option so we don't have to do the server-side stuff. It works really well for us and @did (the author) is super helpful. If server-side isn't your thing I'd highly recommend going this route.