CMS Development Tutorials - "Getting started with modules" Bug

[HLin]

I am trying my hand at working with the web development side of HubSpot and going through the tutorials one by one. I’ve started the “Getting started with modules” tutorial and got through Part 1 without problem. In Part 2, however, when I attempt to add the

Testimonial.module

created from Part 1 into the

home.html

template in the suggested line, I get an error along the lines of:

Invalid argument in ‘dnd_module’: dnd_area-module-4 spanning columns 1 to 6 overlaps with dnd_area-module-3 spanning columns 1 to 12

After attempting to redo the tutorial and doing my own debugging, I determined that the code I’m adding doesn’t result in the desired change that is shown in the tutorial:

In addition, the tutorial references a

homepage.html

that doesn’t exist and thus I assumed would be the

home.html

file.
And so, I came to the conclusion that either there is a bug I don’t understand while attempting this tutorial, or the tutorial is possibly out of date. I am wondering if anyone else is running into the same issue or if they have resolved this before and how?

[Jaycee_Lewis]

Hi, @HLin Thanks for bringing this to our attention. I am going to block some time off today and run through the guide up to where you are having issues. I’ll follow up here with what I find out for us.

Talk soon! — Jaycee

[cprv]

I also ran into this same issue.

[lourancostahs]

Hi @HLin and @cprv .

I was having the same problem, maybe these two link can help you.
https://community.hubspot.com/t5/CMS-Development/Cant-get-grid-system-to-work/m-p/435588

Drag and Drop Areas HubL Tags - HubSpot docs

In my case I decide that each module has width=4, the first start with offset = 0, the secont with offset = 4 and the last with offset = 8.

[Jaycee_Lewis]

Thanks for sharing that, @lourancostahs

[LFilip]

I got into the same issue following the tutorial, I’m stuck, any news with this?

[LFilip]

For anyone here with the same issue, the problem comes from the grid system. @lourancostahs answer should be accepted as a fix. In my case for the same issue, his suggestion did the trick.