Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 23 13:17
    proxygear closed #164
  • Nov 23 13:17
    proxygear commented #164
  • Oct 13 08:06

    did on v4.1.1

    (compare)

  • Oct 13 08:06

    did on master

    upgrade Steam to 1.6.1 + bump v… (compare)

  • Oct 13 08:00

    did on v3.1.1

    (compare)

  • Oct 13 07:59

    did on master

    bump version to 3.1.1 and use S… (compare)

  • Oct 13 07:57

    did on v1.6.1

    (compare)

  • Oct 13 07:54

    did on master

    revert the PR #176 (issues in p… bump version to 1.6.1 (compare)

  • Oct 05 06:42
    simahawk commented #1398
  • Oct 04 07:21

    did on v4.1.0

    (compare)

  • Oct 04 07:21

    did on master

    bump version to 4.1.0 (compare)

  • Oct 04 07:12

    did on v3.1.0

    (compare)

  • Oct 04 07:12

    did on master

    bump version to 3.1.0 (compare)

  • Oct 04 07:06

    did on v1.6.0

    (compare)

  • Oct 04 07:06

    did on master

    bump version to 1.6.0 (compare)

  • Oct 04 06:53

    did on master

    revert back to 1.6.0.rc2 (since… (compare)

  • Oct 03 15:43

    did on master

    bump version to 1.6.0.rc3 (compare)

  • Oct 03 15:38

    did on master

    also push the seo_title, meta_k… (compare)

  • Oct 03 15:02

    did on master

    display an error message if the… (compare)

  • Sep 29 14:28
    alg opened #1402
Peter Salomon
@patternpoints
@did congrats & chapeau!
Didier Lafforgue
@did
thanks @patternpoints & @manuchap
:-)
just a few words about Maglev & LocomotiveCMS (I've already told @greyskin & @manuchap )
first the differences between Maglev & LocomotiveCMS: Maglev is just the sections editor that is already present in LocomotiveCMS. No Wagon, no content types, no liquid tags or drops.
Actually, LocomotiveCMS didn't target Rails developers but just dev people who wanted to get a site up and running pretty quickly without dealing with integration stuff (server, plugins and so on). Well, at least, it was the promise.
Didier Lafforgue
@did
In the long run, maybe LocomotiveCMS v5 will include Maglev. I don't know yet, it depends on the lot of things.
I should have started with this but we aren't going to shutdown LocomotiveCMS and the hosting platform. We'll fix any blocking issues, probably implement some little features asked by our clients (👋 @greyskin ) but that's it.
About Maglev, it's used in production for a niche French e-commerce company, so far so good. And we also built a SaaS service based on Maglev (https://mytotems.page) in order to test our Maglev pro package.
Didier Lafforgue
@did
In the next days, I'll announce "officially" Maglev , probably on Reddit and in some Rails newsletters.
In the meantime, I'm working on a very very cool POC that might bring a lot of highlights on the project. In short, a headless version of Maglev. You implement your site in Nuxt (or Next or whatever JS frontend frameworks) and you edit the content in Maglev.
kind of a small Storyblok (https://www.storyblok.com/)
Didier Lafforgue
@did
oh, I forgot to mention it. I forgot to talk about the financial sustainability of Maglev. 2 sources of revenues:
  • themes! (I can't imagine how happy the Rails developers will be if we provide some sexy themes for the landing pages / marketing sites of their Rails app.
  • Maglev PRO -> the multi-sites / multi-themes version of Maglev that could empower Franchise / Marketing vertical businesses.
Luke Grayson
@greyskin
Awesome @did! Well done - very exciting!
Peter Salomon
@patternpoints
@did glad to hear that you are still going to continue locomotivecms.
Luke Grayson
@greyskin
Yes, same here! :smiley:
Nikolay Bonev
@DonKoko
nice job @did. Looks exciting. I am personally more curious to hear about the headless version so looking forward to that
Luke Grayson
@greyskin

Does anyone know if it's possible to do something like {% with_scope field_name: !empty %}?

Obviously I've tried that but it doesn't work. Any ideas?

Manu
@manuchap
{% with_scope field_name: '' %}?
Luke Grayson
@greyskin
Duh! :laughing: thanks mate!
Didier Lafforgue
@did
@DonKoko thanks. I've just finished my first proof of concept regarding Maglev/Nuxt3 and it works really great :-)
In a nutshell: you create a Nuxt3 app, you define your sections (YAML + Vue components), select the Maglev API endpoint and boom, you can edit the content of your Nuxt 3 site.
ok, It's still pretty raw but I'm super excited by the final result.
Nikolay Bonev
@DonKoko
sounds awesome. I would love to give it a try once you have something we can test
Didier Lafforgue
@did
(everybody is welcome!)
Peter Salomon
@patternpoints
😎 Thanks!
Luke Grayson
@greyskin
Sweet thanks @did - joined!
Luke Grayson
@greyskin

{% with_scope field_name: '' %}?

@manuchap, I read too quickly (and I think, so did you :laughing: )

I'm looking for !empty, i.e. not empty

Manu
@manuchap
🤦‍♂️
Manu
@manuchap
Been tryin' again and again after seeing this line in steam's code: OPERATORS = %w(all exists gt gte in lt lte ne nin size near within) but nothing worked 😭
Manu
@manuchap
The irony
Capture d’écran 2022-10-15 à 01.10.47.png
finally figured out how to properly indent the sidebar in the docs: subtitles needed to be h3, not h2 😅
Luke Grayson
@greyskin

Hey guys, has anyone had any succcess with public content_entry submission with a file field? I have been working on it for several hours now and am none the wiser. The form submits and the content_entry is created, but the file field is blank...

My content type contains a file field:

- file:
    label: File
    type: file
    required: false
    localized: false

...and my form contains the same field:

<input type="file" id="file-upload" class="file" name="content[file]">

And ideas?

Manu
@manuchap
<input type="file" id="file-upload" class="file" name="content[file]" value="{{ file }}">
Manu
@manuchap
Unless you use model_form, add the enctype to the fom: <form method="POST" enctype="multipart/form-data">
Luke Grayson
@greyskin
Hi @manuchap, I've already tried value="{{ file }}", value="{{ content_type.file }}" and value="". All result in the same thing: no file upload.
(I am using model_form).
Peter Salomon
@patternpoints
Is „file“ a preserved name maybe?
Peter Salomon
@patternpoints
Other than that, I’d try first to post the form to a toptal.com bin
… to make sure the form works properly
And then check the other side using curl curl [URL] -F name=John -F photo=@john.jpg
Peter Salomon
@patternpoints
Have you tried {{ file.url }}?
Luke Grayson
@greyskin
Yeah tried {{ file.url }}...
Luke Grayson
@greyskin

Hey guys, has anyone had any succcess with public content_entry submission with a file field? I have been working on it for several hours now and am none the wiser. The form submits and the content_entry is created, but the file field is blank...

Got it. I had json: true set on model_form and was submitting the form with AJAX. This adds a layer of complexity that I wasn't aware of. Simply using data: form.serialize() won't work. This StackOverflow question helped me solve the issue.

There folowing things I needed to add/replace in my AJAX form submission:

  1. Use FormData to save the form data to a variable and use this variable instead of data: form.serialize()
  2. Add cache: false, contentType: false and processData: false as settings to the AJAX call.

Abridged Code:

$('.form').on('submit', function(e) {

    e.preventDefault();

    var form = $(this);

    var formData = new FormData(this);

    $.ajax({

        type: 'POST',
        url: form.attr('action'),
    //  data: form.serialize(),
        data: formData,
        dataType: 'json',

        success: function(data) {
            console.log('Success:', data);
        },

        cache: false,
        contentType: false,
        processData: false

    });

});
Manu
@manuchap
👍👍👍 It was my first idea that you might be using ajax 😅
Luke Grayson
@greyskin
Haha you should have said! :laughing:
Peter Salomon
@patternpoints
Uhhh … thanks for sharing! That’s a trap I would have run into too.
Luke Grayson
@greyskin

Anyone know / found a way to include HTML in content_type templates?

You can include basic HTML in the metafields_schema.yml file - I've found this very useful for my clients for a bit of formatting and emphasis where needed, e.g.

- some_field:
    label: Some Field
    type: string
    hint: '<b>Important:</b> Emphasise information for especially dumb clients.'

I've even managed to include <style> elements in places.

Unfortunately, I haven't managed to find a way to do the same thing in content_type templates.