Backdrop CMS Weekly, 20 Apr 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop Weekly 4/20

Description

Today’s development agenda: http://bit.ly/2oaFOw8

A

We're that all.

B

Right, hello, everybody, it's April, twentieth, 2017. We are ten days away from the code freeze of backdrop 1.7 and we are going to run through the world of backdrop CMS, including the looks like primarily focused on the product, this particular weekly meeting, so updates from the PMC.

B

We have no announcements from the PMC at this time, although there's kind of some exciting news in the pipeline, once we get some things worked out internally, that is very exciting and I'm just going to leave you guys hanging on the edge with excitement as to what what the exciting news, maybe, but that may take us a couple weeks to work out some new facilities for backdrop, which should be great, contributed code that looks like we have some are these: are these updated new contributed projects? References?

B

Did it finally get a stable release in this past week?.

C

No, but we're getting closer there I've just pushed some changes that solve some of the Ajax errors that people were getting. So if the people who are getting the Ajax errors wouldn't mind going and testing again to make sure those are resolved, that would be appreciated. Oh.

B

So so, apparently, references module, yeah, okay, references module, the node reference and user reference to mine modules. Oh there was a security update that came out, so the security update that happens last week in the world of Drupal temporarily had the references module mark is unsupported and then we coordinated with the new maintained, errs of the references module and made a new release of that macho. So that's great yay. Thank you.

B

Drip team for helping, coordinate and fix that problem, but then backdrop and within drupal a simple access grants, module and trigger actions to new contributed modules that have come up in the past week, which is fantastic, as always lots of it. Lots of thank yous to everybody. That's been working not just on the core project, but you know are hundreds of contributed modules that are seeing really regular releases and maintenance really appreciate everything that our little community is doing to push forward the backdrop product or the backdrop ecosystem.

B

So this mean we're going to focus mostly on a progress report of bankruptcy, ms the project or product, because code freeze is May first less than two weeks away. So first we'll talk about the 1.6 branch, which includes all of the bug fixes that we make as they are needed, the 1.6 dot for release. I don't think this still has been anything substantial that is cropped up. We have been merging minor fixes here and there and I think, we'll continue to just like as needed.

B

If something comes up, but we justify release, then we can make one at this point. There's really just small things here and there is nothing really for one point, six point four: unless anybody has anything else, they want to bring up, that's not mentioned and the agenda. I don't think that there's anything of note.

B

1.7 1.7 is the next minor release of backdrop in which will be releasing some new features and functionality, and that will be coming out. May 15 2017 and there's a number of issues in which we have been making some progress in the past week redesigning the status report.

B

I'm not actually the best person to give an update on this gregory could maybe you give an update on status report. Unfortunately,.

A

The app there is no update. We had some discussions as to what direction we should take, but I didn't have any time to just work on it. If there's anyone else with more time, they just feel free to pick it up, but yeah. My availability is limited.

B

Okay, um that's the next item that we've gotten here is the views you I redesign, I'm, not sure. If this one has seen action in the past week, you get I.

A

Started that off and then West picked it up and made a new pull request. I engaged some feedback. Their tiny things should be more questions rather than feedback. Should we have zebra striping or not that sort of stuff, but I think wes is busy with other things now so yeah I think that both of these issues, the the two great design issues they need more opinions, and then we need to settle on what we should do. Ok,.

B

So both of those me I had some design feedback that is required. Ok, the next issue that we've got here is the custom. Sorry page element blocks that allows you to move things like the page tabs and page title around as though they were blocks doc. Woman did a reroll of this pull request a little over a week ago and moved back to nice review and we got a lot of great feedback from a variety of people.

B

Thank you, everybody for posting feedback, but it seems that we've uncovered a new problem in which we need some assistance sounds like Jeff. You've may have taken a stab at solving this problem and there's a little bit of back and forth, but I'm having a little bit of trouble just summarizing with it. The issue is at the moment.

B

Jeff. Can you provide any additional comments on on the page element blocks issues, 1704 I can't, remember, I, think it's.

D

The block title options when you click on the configure block, if you say custom title it, doesn't it doesn't respect that.

B

So it looks like it's. Some issue between, like we've, have made a special dialogue for the page title settings and then that can conflict with the page title settings that you get within the block. Yeah.

D

I'm not sure I actually came to a proper understanding of the issue, because what I tried to do was just say: if you want to customize the page title do that in the node edit form, but doc Wilma said something else that I didn't understand, so I, don't think I ever properly understood the issue and I think this might.

B

Even be something that we could separate into a different problem like it seemed a mean it might have beat and generally related, and it might introduce us as a set of circumstances in which you can get conflicting settings in one of them wins basically, but as far as the capability goes, I think that that could be considered just to be a separate issue, something that could be not blocking on the implementation of this feature anyway.

B

I'm really good to see the duck moment has at least address all the code feedback that that I've requested there I think it's just a matter of four and what we're going to do with this new issue that has arisen, whether it's something that Lambo separately or or something that we need to address here, but I'm really glad to see that moving forward, yeah yeah would say it's probably still needs work status, though ok layout relationships is issued. 2134 relationships would allow us to jump from one type of entity to another type of entity.

B

We did have a reviewer that came in and reviewed that issue, which is fantastic, but it looks like he has encountered. Some whites reigns of death when, when trying to actually set up the relationships, I think that one's this very clearly probably needs work category. But thank you so much for giving a review on that. One I think our review bottleneck has been pretty severe and it's very helpfully good feedback like that.

B

Let's see, and then they had this last item, a wishlist item, I, would say 24 33, which allows you to would allow you to have all the powers of panel pains panel pane displays from triple seven available on all blocks that are created by the views module that would make it so that, if you could, you could do things like override how the pager displayed or how many items were listed in a block on a per instance, basicity drank it dragging the block that commits of you, I, mean, say.

B

I want this instance to only have ten items, so you can drag in and alone say. I want this from f5. It would be very cool feature when fitted nicely with relationships and element, page element barks, both of which I'm still optimistic that we can complete. Even though we only have ten days left before code freeze before feature freeze.

A

It's worth making that these issues of looking for one of the converted things to reviews, I, think recent comments. It is.

B

Right because recent comments, the recent comment block lets you choose how many comments you want to display and the recent common point so.

A

Yeah basic, this will add options stick to have them some sort of exposed fielder's on the blocks created by views within this book. Yeah.

B

Yeah we can work around that in other ways, but this would definitely be preferable to have just be directly from views rather than a common module. Specific then.

B

The item that I put on here last week seems to have dropped off, but there's a patch that a pro request that I filed regarding copy paste support inside of ck editor, which I think is kind of like a big deal.

B

It allows you to upload files by drag-and-drop from the desktop or copy paste directly from the clipboard and will upload files under the server I mean find that issue that one is in a state of needs, review I know, look what I got a lot of feedback on it, but.

B

Jeff last time he looked at, it was encountering some areas that I hadn't seen.

B

Thank you for updating that issue. 26 30 and that's Anna needs review, states or sorry. I guesstimate meets work state now, I.

D

Think Grail identified that if the Styles folder for the images don't it doesn't exist yet create an error. Interesting.

B

D

It's not like it's their work, flying.

B

Okay, awesome well, in that case, there's some more work to be done. Okay, all right, um yay I love feedback, even if it means stuff needs work. Okay, those are the main items that we have slighted for the 1.7 release. There are some less importance issues and once that are less likely to be completed, do you guys have any additional items that we should add to the agenda for the 1.7 release, hopefully stuff that is in progress rather than something we're going to start a new 10 days before?

B

No okay? That's all I have for the 1.7 status update. If you guys don't have anything else for the product updates, then we go into general discussion and Q&A. You guys have anything. You guys would like to ask.

A

Well, I've had a recommendation for an issue yeah.

B

I saw the issue 2637 and I do agree that that is a one point. Six point four issue, because it's a bug regarding transliteration that it doesn't use the default site language, let's, um let's throw that item into the agenda for the one point six point four releases so that we can keep track of that.

B

Also, there's 14 17.

B

B

Which is the browsed web? Oh yeah, yeah, this one's really cool and I marked this one hour TVC this past week, because I think that functionally it's it's good to go, but I also worked at postponed because it's blocked on a styling issue, and so the autocomplete styling inside of a dialogue has some issues that the autocomplete ends up like underneath the dialogue contents.

B

So we need to fix the styling issue, I think first, because I don't want to introduce a new feature, especially one that will probably like be screencasting and demonstrating if it has a very blatant styling issue and so course should always be in a shippable state. So I think that if we're bringing a new functionality like to the forefront, it needs to look good in its implementation.

B

Even though, even though the functionality works great, we need to fix the styling problem first, so the styling issue is 2517 and Wes has been pained in that, although an assigned, but he hasn't- responded as actually having time available so I. Don't think that something that really explicitly requires a designer's hand, though I think it just needs a somebody. That's could ensuring consistency between the way that things appear and actually, in this case, it's literally solving a bug with CSS rather than even designs, consistency.

B

Okay, excellent a lot. Thank you for pointing out that transliteration bug I would say that that's a high priority, thank for us to to correct we'll see about when we make a 1.6 point for release we're only little under 4 weeks, I mean a little under a month away from release. It might be that 1.64 comes out the same time as 1.7 does, but in any case, I think that we should prioritize that fix for for being in the next release, whatever it is or whenever it is.

B

Anything else that you guys would like to bring up for discuss.

C

I'd like discuss the reference module right up, yes, I just been dating, so there's the Ajax errors that I mentioned on that that I've fixed the problem for some of those is like, went on the when setting up the reference field, there's an option to limit the results that can be selected by bundle so when people are going through their selecting the bundle and selecting user for the user one.

C

But the problem is: is that the users and files don't have bundles, basically, there's just one type of em, so I changed it to check to see. If a bundle is the plot, a bundle key is supplied and if not don't let the user have that selection, which is easy enough comments, were a bit more difficult because for comments, the bundle, the thing that's using for the bundle is the type of node.

C

The comment is on so to solve this for now: I also disabled, choosing a bundle on that field if the bundle key is not found in the database table. So so, like most most entities like in in their base table, they have a field for bundle, whether it's label, bundle or type or something like that and so I make actually checking to make sure that the key is in the table and if not I'm, just disabling that option. So that means that you basically can't choose what types of comments to select I.

C

Don't think this is a big deal because, like I think we should refactor the comment module at some point anyway, but, like it's, I, think it's okay. If people just select all I want to reference comments, I, don't think people usually reference comments, but if they do and think it's a huge deal to only select like comments that are on pages, as opposed to come and sit on posts, I got.

B

Jennifer Jen hosted not any eight percent use case, but I would say, even if it were in eighty percent use case, that we should focus on completing the functionality that we have to make it a usable module and then emanator it on after that. So I think that's the line solutions with the time being.

C

Basically, my question was anyone else like have any know of any like contributed ease that like have one name for their bundles like in there in there, like you, know, entity arrays, but a different name in the database table or whether that's uniform, like this is a weird thing, but it's like I think this is a good solution just because, if there is any weirdness around that it actually checks and just disables, though that option based on if it's the database tables and sound I mean I, guess that seems like a fairly good solution for the time being and then, if we encounter any other types of entities that have weirdness around mismatches, this won't, it will limit the functionality but prevent any errors.

C

So that's I'm good. Everyone.

B

Yeah that sounds good to me and I think that those keys between like the database tables, like the keys that are in alg entity info and the keys that are in the database I. Guess they I guess they could be different, but I can't see any practical reason why people would attempt to do so. I mean like you, want them to be the same. It didn't. It really helps with consistency, and it's it's the way that every entity I've ever seen has been a simple.

C

Yeah anyway, so, like you know that that seemed to be the only thing where people were getting errors.

C

So if people could try out the reference module again and make sure that it's all working for them, then I will go ahead and do a release. Excellent.

B

Thank you, Mike look I'm just reading out what Jenna janaza saying anything you can up Jen. It doesn't sound great, but you can still.

C

Hear you sorry.

D

I was needed, acessórios gonna pick up all the background. You.

C

Found you sound just a bit, you know fuzzy, but it's not it's not that bad. Okay, you can talk. Thank.

B

A

Maybe she was just being ironic as their microphone like. Thank you. Mike.

B

Okay, do you have anything else that I'd like to bring up e anybody on the broadcast.

B

Okay, all right well, I think that's it for our broadcast and for a public meeting. Thank you, everybody for joining. Thank you everybody for watching. As always, we've got 10 days before code. Freeze, I'm, really stoked about some of the things that we've got slated and he's hoping won't be able to push through it. So, thanks again everybody and we'll talk to you later see you later.