Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    arzvaak
    @arzvaak
    @greyskin I would want to go for the pricing plans as well, but I don't know how economical would it be to get it due to the pageview limits. I wanted to ask if I could set up a website (something like shopify?) And let people buy some plans so they could host their own novel/book website where they could publish their books, so something like wattpad, but I was wondering if I could let them login through the dashboard through my site, make them sign up and have their own domain. And then choose their template (something like wattpad or webnovel) and publish their own stuff? Is it possible to do this with locomotive or do I need to hardcode everything?
    arzvaak
    @arzvaak
    Also are there any more extensive guides on the CMS? Or some tutorials for more complex use cases?
    Luke Grayson
    @greyskin
    @arzvaak ah ok I think I understand what you're wanting: you'd create a site on Locomotive CMS and your users would log into a front-end page on that site and then be able to purchase a website, select a template, etc and that process would create a site for them on Locomotive CMS under your account. I'm not sure this is possible but I suspect @did could confirm. I suggest you PM him directly and ask the question. There is an API available which may be useful for this scenario or there may be some functionality that I'm unaware of.
    Nikolay Bonev
    @DonKoko
    Has anyone done text compression and assets caching policy for a self hosted engine on heroku? I am wondering how you made it work.
    Alex Wellnitz
    @alexohneander

    Hi guys, can someone help me?
    I have Locomotive productive running and would like to use Redis as a cache. I have actually set everything I need but nothing shows up in the cache. What could be the reason for this?

    This is my config:

    config.cache_store = :redis_cache_store, { url: ENV['REDIS_URL'] }
    REDIS_URL = redis://redis:6379/0
    samnymr
    @samnymr
    Hi Everyone, Loving locomotive so far, Can't seem to find a way to change some things within engine to customise it, we're looking at 2 things, One the ability to change the logo/colorscheme of the login page, two, the abilityt o create custom admin pages (for displaying analytics)
    Luke Grayson
    @greyskin
    Hi @samnymr - I assume you're running your own version of Locomotive CMS (as opposed to using station.locomotive.works?
    samnymr
    @samnymr
    @greyskin I am indeed, I've actually solved the first issue, its just the latter
    Joshua Kappers
    @jkappers-ga
    Is there a roadmap for v4+? Evaluating Locomotive and interested to see what's planned for the future.
    Luke Grayson
    @greyskin

    There is this Trello board, but I get the impression it isn't currently being used. @manuchap or @did can probably confirm...

    Regarding your evaluation, my 2 cents is that Locomotive CMS is under-rated. It's capable of quite a lot but the learning curve is steep. Setting up Wagon was the biggest hurdle for me. The other downside is small community which means getting help can take a while at times.

    @jkappers-ga are you planning to set up your own instance or use Locomotive's hosted solution? I'm only using the hosted solution (at this stage) and am happy to help where I can if need be. The more folk we can get on board the better it is for everyone.

    (I really wish I was a ruby dev so I could actually contribute to the development of it - all I can really do at this stage is help with the docs, test, trouble-shoot and report the odd bug).

    Manu
    @manuchap
    @greyskin Yep, the trello board hasn't moved in two years ๐Ÿ˜•. That's one reason why I try to keep this gitter alive. With help from you, @DonKoko and a few others.
    And you're right about the steepness ๐Ÿ˜†. I discovered Locomotive ten years ago and am still almost exclusively using it on my projects unless asked otherwise.
    Manu
    @manuchap
    @jkappers-ga You might wanna check TGV. I created this site (while under depression, hence the haml ๐Ÿคฉ) for myself at first to gather bits of locomotive stuff in a marketplace fashion. Everything on it has a corresponding github repo (even the site itself). I learned all I know thanks to others so I felt like giving back.
    Luke Grayson
    @greyskin

    And you're right about the steepness ๐Ÿ˜†. I discovered Locomotive ten years ago and am still almost exclusively using it on my projects unless asked otherwise.

    I'm heading the same way, i.e. using Locomotive exclusively - I think it will fit most use-cases I have in the SMB space that I work in.

    I really like the idea of running my own instance so I can rebrand the Back Office but I'm essentially a one-man band with a contract designer, admin and accounts person. I'm not sure I have the expertise to run my own platform...

    Joshua Kappers
    @jkappers-ga

    No worries! Evaluating using on an enterprise site that desperately needs a CMS. After evaluating several solutions, we've narrowed it down to Locomotive, Drupal, and Sitecore.

    One strongly desired feature is that internal users are able to spin up something without necessarily being blocked by engineering. A scenario would be that a marketing campaign is launching (or in the works) and a new landing page is required, but the components/sections aren't available to compose it according to the campaign's need. In that case, users would seek engineering assistance, but want to proceed on their own if engineering doesn't have the bandwidth to support them. Halting or postponing the campaign is not ideal.

    Because Locomotive requires components and doesn't have a sort of "WYSIWYG" option for building the pages, it's out of the running. Drupal is likely out too for the same reason. While it's technically possible to achieve this feature in either system, the intention is to move forward with very little (read zero) customization of the chosen platform. A factor that may have kept either in the running would have been the existence of a suite of components that enabled internal users right out of the gate.

    For sites where this isn't an issue, the Locomotive approach has some very clear benefits around consistency and quality. I appreciate that it necessitates well-engineered sections that support various devices and that consideration only need be made at one level: the root. It's definitely something I'll consider for other projects.

    Luke Grayson
    @greyskin

    Interesting! I wouldn't say Sitecore vs Locomotive CMS is an apples-for-apples comparison (although does such a thing really exist in the CMS space? ๐Ÿ™‚) It sounds like your client's needs are bigger than what Locomotive (or most CMS's) can offer at this point.

    On a side note, I have yet to find a WYSIWYG editor that actually results in your getting what you see. ๐Ÿ˜ I've become convinced that a choice of flexible components is the only way for non-technical users to create anything half decent. Locomotive's sections are certainly no drag-and-drop builder and there are lots of things I wish they did, but they do ok and the fact that you can create your own is pretty cool. I believe Locomotive's real strength lies in its content_types.

    Joshua Kappers
    @jkappers-ga

    I totally agree. It hasn't been an easy task by any means.

    While it seems Sitecore will be the winner for this project, I actually haven't evaluated it yet. I'm assured that it's going to be the best fit though. I'm waiting for a demo site.

    I will certainly be surprised if the WYSIWYG features are exact.

    Content types are useful. When consistency and quality are a goal, I really think Locomotives approach to sections is great. I envision UX/Engineering working together to curate and create sections that work well and internal users being almost ensured to build perfect pages by making use of those sections.
    Manu
    @manuchap
    @jkappers-ga If you're still investigating, have you tried OctoberCms? (I really shouldn't advertise competitors here right? ๐Ÿ˜…). It feels a lot like loco (V2 with online code editor) and has a plugins and themes marketplace.
    Joshua Kappers
    @jkappers-ga

    I hadn't heard of OctoberCMS. Thanks for the suggestion!

    This company doesn't have the expertise to support in-house for Php installations. Watching the introductory video, it seems a bit too open that I think it wouldn't be the best candidate. The back-end users won't be technical and would rarely want to interact with source code.

    (rarely, if ever)
    AngeloGodbey
    @AngeloGodbey
    Hello, I have LocomotiveCMS v2.5.4 and am having a hard time figuring out how to add SSL to it. Can anyone point me in the right direction? I have the SSL certificate from gandi.net (our domain provider). I just can't quite figure out the steps I need to do to get my site to have https.
    Manu
    @manuchap
    Not too sure since it's a bit old but I'd try uncommenting line 31 # config.force_ssl = true in this file once the certificate is setup on your server.
    Luke Grayson
    @greyskin

    Anyone been able to use created_at on content_entries? Specifically with the Actions API allEntries()?

    I've implemented the following exactly as per the docs:

    {% action "test get all entries" %}
        var test = allEntries('[content_type_slug]', { 'created_at.lte': getProp('now') });
        setProp('test', test);
    {% endaction %}
    {{ test }}

    and I get zero output.

    But if I remove 'created_at.lte': getProp('now') I get all the entries no problem.

    @manuchap, you'll see I've made a suggestion to remove this from the docs as I don't believe it's currently functioning.
    Manu
    @manuchap
    That's a weird issue that one... I tried last night and it worked fine (in wagon) then tried this morning and I got nothing... unless I force refresh the page (or sometimes also restart wagon) and boom. Results. I believe wagon creates a cookie and the created_at values are the cookie creation date. I haven't tried with engine yet.
    Manu
    @manuchap
    As a side note (not related) it made me discover that text entries created by an action have their lines ending in \r\n whereas using the backend editor these are </br> which makes parsing the results a bit cumbersome.
    Manu
    @manuchap
    Also, isn't created_at.lte': getProp('now') equivalent to all entries?
    Peter Salomon
    @patternpoints
    Yes, all entries should be created before ( less than / equal ) now unless you left your prior tomezone ๐Ÿ˜… . So, the filter should return all entries. Itโ€™s weired indeed
    Did mongodb change the date format? Does โ€žnowโ€œ match the required date format so that the comparison actually works?
    Manu
    @manuchap
    In mongo the dates look like this (so I don't have a clue ๐Ÿ˜„)
    "updated_at": new Date(1620916550219),
    "created_at": new Date(1620064385791),
    Might be pure epoch for all I know
    Luke Grayson
    @greyskin

    Also, isn't created_at.lte': getProp('now') equivalent to all entries?

    Yes, but I was using it as a test to see whether I could get created_at.anything to work, period. I was originally trying to use created_at.yesterday (where yesterday was today less a day).

    In the end, due to what I can only assume is a bug, I had to abandon this method of filtering entries altogether and do the following:

    {% action "test get all entries" %}
        var test = allEntries('[content_type_slug]', {});
        setProp('test', test);
    {% endaction %}
    
    {% assign yesterday = today | adjust_date: -1, 'day' %}
    {% with_scope created_at.gt: yesterday %}
        // run logic on `test` here
        // and then pass the results back to another action
        // so I can run more JS 
    {% endwith_scope %}

    Which is crazy! ๐Ÿ˜•

    Luke Grayson
    @greyskin

    Did mongodb change the date format? Does โ€žnowโ€œ match the required date format so that the comparison actually works?

    I did wonder if the date format was the issue. I've noticed a number of other things don't work around date. For example:

    {{ '2021-09-14' | parse_date }}

    ...will result in nothing. Docs say it should work.

    Manu
    @manuchap
    This date thing is a real brainfunk... Here's a query that works in mongo:
    db.locomotive_content_entries.find({ "created_at": {$gte: new Date(1631491200000)} })
    After many trials, only the long epoch date worked.
    Now I need to figure out how to script that ๐Ÿ˜ถ knowing that new Date("2021-9-13").valueOf() returns a long epoch.
    Luke Grayson
    @greyskin
    Ok so get this: {{ '2021-09-14' | parse_date }} is now working for me. (Or at least it was when I tested it again last night). What do you make of this? I haven't changed anything. Same test page, just reloaded it.
    Manu
    @manuchap
    I think it's {{ '2021-09-14' | parse_date_time }}
    Luke Grayson
    @greyskin
    I believe there is also a parse_date_time but I'm talking about parse_dateand weirdly it's now working for me.
    So bizarre.
    Manu
    @manuchap
    Yes because for me it doesn't ๐Ÿ˜…
    Wagon version: 3.0.5
    Luke Grayson
    @greyskin
    I'm also wagon 3.0.5!! ๐Ÿ˜ฎ
    Peter Salomon
    @patternpoints

    Just tested the date output. For me, the above spits out

    {{ '2021-09-14' | parse_date }}
    # output: 2021-09-14
    {{ '2021/09/14' |  date: "%b %d, %y" }}
    # output: Sep 14, 21

    or, the other way around ( i guess that is the expected output according to the docs:

    {{ '2021-09-14' | date: "%m/%d/%Y" }}
    # output: 09/14/2021
    And for long epoch:
    {{ '2021-09-14' | date: "%s" }}
    # output: 1631592000
    not sure if that helps in time comparison though
    Peter Salomon
    @patternpoints
    but it seems, that parse_date doesnยดt do much...
    works also with "now":
    {{ now | date: "%s" }}
    # output: 1631744078
    Peter Salomon
    @patternpoints
    And back:
    {{ "1631592000" | date: "%Y-%m-%d %H:%M" }}
    # output: 2021-09-14 00:00
    Peter Salomon
    @patternpoints
    And with parse_date, also liquid doesnt accept a format string:
    {{ '2015-09-26' | parse_date: format: "%m/%d/%Y" }}
    # output: error: "no implicit conversion of Hash into String"
    Luke Grayson
    @greyskin
    @patternpoints are you on station.locomotive.works or your own install?
    Peter Salomon
    @patternpoints
    @greyskin I am on my own install, but all the above is wagon