kelter

…been following this thread as I have this issue too…

The dev branch seems to work here. When will the current dev branch get rolled into the release version?

thank you.

@prathameshp

Yes – I’ve updated to each successive release. All seems to be working now. thank you.

If it’s just (mostly) for text and you don’t want to have to worry about where the text “breaks” from column to column, just use CSS Multi-columm on the container div. It’s one line of CSS ??

div {
    column-count: 3;
}

Play here.
https://www.w3schools.com/Css/tryit.asp?filename=trycss3_column-count

@gamersk Blasphemy! ?? I jest…
But I’d suggest looking closer at WP-Forge though – once we see more of Foundation 6.4 and grid solutions you might prefer it to BS.

Would be helpful to know how this was resolved.

@aware That’s great – will check it out. Thanks! Now about that changelog ??

@aaron – got it. I’ll use GitHub from here on. thanks. Will come back and resolve this once you come up with a solution ??

Yes – all seems good. I’d initially used the GitHub 1.0.3 version and looked good. I’ve now pulled it from the WP plugin repo and confirmed no problem. Thanks!

@aaron Ware Thanks for the follow up. I’ve had a chance to poke around this a bit more. Looking forward to seeing the transition to F6 (and maybe using the Flex grid too – not sure how you’ll do that with the draggable UI though) Good luck – I’ll be following along.

however everyone needs to understand that Foundation was basically rewritten from the ground up,

Fair enough. Plus of course Foundation still seems to be in a bit of a mercurial state anyway – lots of updates already on the 6.x version.

Best of luck everyone! ??

Would like to see (or suggest having) some sort of “transition” docs for folks trying to move from 5.x to 6.x? Think that’s possible?

Same issue – Subscribing too.

?? Just keepin it real.

I do think that whenever an update is released and a child theme is being used, that any and all files should be checked to see if there are any changes to the original parent files. At least this is what I would do

Exactly my point regarding diffing against your source… or any source.

Since we’re on the subject of the header.php file, should the * @since WP-Forge 5.5.1.7 line be updated to 5.5.2.2?

Not really sure how that header comment stuff is supposed to work, and diffing against the entire theme code is time consuming ?? thanks.

v 1.1 looks good. Thanks!