Backdrop CMS Weekly, 29 Dec 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop Weekly 12/29

Description

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

A

Hello, everybody, it's December, 29 2 2016, and this is the weekly backdrop def meaning so every week we get together and we talked about the tasks that are facing a backdrop and this particular meeting. We have a really shortened agenda because we're focused on the next release of backdrop, 1.6 that comes out in a couple of weeks january, fifteenth also per our new policy. We are doing code freeze on january first, so we have some items that need to be finished up in order for us to meet that deadline.

A

Let's see here before we get started talking about the progress report updates from the PMC.

A

The only item that we have here is that we did get new phpstorm licenses, although it appears that if you previously received a phpstorm license- and you need to renew it because the old one has expired earlier in december, you can continue to follow the same link that you received initially and that will get you the new license file.

A

Apparently, if that doesn't work, you can always reach out to us info @ backdrop, CMS borg, and we can get you we can send you the link or we can send you a license file if that, as in trouble and thanks again to jetbrains for those perpetual licenses. Quite handy.

A

Alright, let's talk about backdrop. The 1.6 release coming up in just a couple of weeks, the highlighting or banner feature for this release is the reference module that were working on adding to court, which is the shoot 1301 Mike join, give an update on reference module, yeah.

B

I, don't see how that's going to happen for this release I'm slowly working my way through adding tests but I'm having some issues that and no one else's pitched in anything. Along with that, we have a few outstanding issues in the issue: queue for the module that shouldn't be that hard to address. We have a few remaining features which shouldn't be that hard address, but I don't think we can do it all by. However many days two days three days and then I definitely can't do the stuff.

B

The gem was talking about with the replacing the taxonomy reference field and having an upgrade path from entity reference. So yeah I welcome to input on how we should proceed. Yeah.

A

A fair assessment and as I mentioned before, we started to call Jenna's hill, and so that makes some things difficult.

A

I've volunteered, but I'm not been fulfilling my obligation here on on helping with tests, so I still plan on chipping in there as soon as possible, which basically means today and tomorrow and the weekend but yeah you're right that it's gonna be tough, we'll see, yeah I think at this point, like I, can help with testing and I'll see how far we get on that. It might also.

A

It's been proposed that we leave in like term reference by yourself and others that you know cuz doing the upgrade path is challenging, and so that might be on the table and it might not be I think want me to see how John feels about this. After you know, she was unable to work on the upgrade path so that my yeah.

B

Chaley tips and we can always do an automatic upgrade later and I mean we can there's like I, said: there's, basically nothing in the data structure of one of these references other than just like the entity type and I e. That is referencing yeah and is in the same thing the same for turn for for the same things, the same for taxonomy reference. Probably the only thing it has special as the widget for creating that and stuff like that.

B

We might be able to swap things around later and just do an upgrade path later and maybe have a taxonomy module itself provide a special widget to the reference field or.

A

Something so I mean yeah, I'm also not keen on it that we could do like one thing, like the reference module first and then do the upgrade path. Later I mean what it is worth, acknowledging the fact that we do actually have two additional weeks before the release itself comes out and 1.6 is right now very, very limited in its changes. There's hardly been. You know anything at all, actually, so then number of bugs that we have to squash in that two-week period or almost non-existent, because everything is pretty pretty much the same.

A

However, as soon as we introduce reference module and some of these other changes, you know that that's we're going to spend the two weeks actually fixing, so it is possibility.

B

The little sort of the reason that we live is why we came up with the two-week freeze is that we wouldn't be trying to jam stuff in right at the end and I have enough testing and time to do the bug, fixes and stuff. So we're sort of leaving.

C

B

Sort of talking about breaking a rule that we just created for the Attic, yes,.

A

Which is exactly why I'm not keen on it yeah, okay! Well, let's continue cracker.

B

A

And talk about initiative, yeah I.

B

Was honestly at this point I would I would be fine just even if, even if this backdrop releases light, like you know, just keeping reference in the control and maybe doing an official contribute so.

C

B

Can start using it with their project, downloaders and stuff like that, so if we just like, if you guys want to help me sprint and try to get an official release of reference out, that would be super help. Yep.

A

And I like that idea, actually quite a bit, we could even feature it like in the newsletter that goes out talking about 1.6, let it like to that. It's made to work together or something like that yep and that and that could get some momentum behind making trip version which could be made part of Cory as we go forward. Yep.

A

That's a good I like that idea and if there's anything that we need to adjust in core to make, you know reference module possible. Then we can say you know it's funny, advertising it as a feature, but if 1.6 is required for reference module to work, writing that adds a time. Well, can.

D

I say a couple things up just so: yeah go ahead.

B

Was going to say that, yes, there are a bunch of issues of things with around entity info that we that the reference modules currently adding basically in stuff around the core entities, need to have additional information put in about their leg label field and stuff, like that, so I mean there.

C

Is stuff that we.

B

Can add to core and I have court issues open for I'm not sure if any of them actually got resolved at all, so we have court issues open for it to work with the entity field, and so basically, we can say, like the new reference field is like a super simple, fast module because, like core provides energy information, we're leveraging like entity api a lot more than like the other reference fields, did yep.

A

D

Gregory, or are you going to say yes, so a couple of things? First of all that the idea that you said that you were talking about reminds me a lot of the way Triple H has these experimental modules that get into core I think we might have touched on that issue a couple of times what we said. It's not a good idea but might seem like this is a perfect chance.

D

Bag I'm just saying, and the other thing is, although it saddens me and watch it not enough to help, we we've been through that with the WYSIWYG module I, don't mind if we even like I hate, I hate have been to stress ourselves and members of our community just to get features in. So if this gets pushed Stephen, 217 I'm, not saying don't, try to get it in there, but even if it gets pushed to the next three days I.

D

All we just find this I hate, like I, don't wanna mike, has been struggling with it. For the last week's I see him stressed I hate to see that I wouldn't mind.

A

Okay, yeah great, like I, totally agree as well, and we are volunteer-driven organization and we have been doing incredible work with the resources that we have, but with some person like Jenna's work yourself into illness, you know like hahaha that's a not to anything we want to to push on to anybody.

A

So let's continue thinking about that and talking about it's in HQ I will I promise lend a hand there with testing and try to push that forward, although I don't think I'm quite ready to table it officially, although I think that we should discuss more about.

B

A

B

Take a I mean, there's, there's also a to-do list issue, which is has a bunch of things in it. So we have like ten issues and one of them is it to do list with like 30 issues in it.

B

So there's like a bunch of little things, I get access, checks and stuff, but then there's also like the reverse views relationship which still have to figure out so I mean there's, there's some some meaty chunks and their features that still need to be built into this before it's I, totally ready to replace entity reference or ok.

A

Ok, well, let's it's very least just continue developing the criminal. It is accessible under Jacob, calm, / backdrop dash contribs and that's where developments happening and I really like the idea, at least of making an official release if it doesn't get in then at least having a module that people can actually use. That is yeah searchable and installable, and everything like that.

A

Okay next feature on the list here is entity view modes, adding the ability to add a custom view mode to any entity type and that's issued 315. This issue looks really good. There's been a lot.

A

The actual API underlying part is actually really pretty simple, but we've been going back and forth and back and forth with all of these user interfaces that making a user interface for this has been somewhat challenging, and so initially we implemented it the same as the contributor level, 7 or the way Drupal 8 did it and give it a top-level item under structure for view modes, but it was pointed out the view modes are kind of an advanced topic and at finding like a centrally managed place for all of your view, modes.

A

Isn't kind of like it doesn't really make much sense to have like view modes for users being right next to no, it's like people, don't say: I want to now configure my view modes and do it all at once, it's much more likely that they go to the type of content like the node type like a blog post or slider or whatever it is, and they realize I need another view mode here, and so, rather than putting the b-mode somewhere else, we've integrated the ability to add a view mode on the place where you would actually want to add a few mode, which is looking really good.

A

It's mostly down to a question of whether or not we want to show the disabled view modes on the display fields. Page or not.

A

It's I think it's a question of what our priority is here, whether or not disabled view modes are going to be used frequently enough that we should show them on that page or whether or not adding a view mode or showing a disabled via mode is not important enough to show on the same page and should be stashed away under the add or customized you mowed link, there's mock-ups I know it's a little bit. Ron and I share my screen. Here we go.

A

I'm second: here we go okay, so here's what we're looking at this is a one version where we only show the view modes that are that are activated and then, if you want to add or customized one of the disabled view modes, you have to click this link, which then shows you a drop-down select list of all of the possible few modes and an option to add another one. I, don't think.

A

There's a screenshot of that, and the other option is something like this: where the disabled view modes are always shown on the manage displays page with a button over here on the right hand, side to enable or customize it to actually make it actually be.

A

Used on this particular type of content, those.

B

A

B

Either the first time I've actually finally take a look at it. The customized terminology is a bit weird like it's a gothic and second to realize what it was I mean. It makes sense once I realize it, but like an able sort of seems better or something word yeah, but you know customize make sense, I'm, absolutely cool.

E

Yeah, the problem is it's not really disabled. It just goes to the default yeah.

B

E

Still use it so yeah and.

B

Then yeah, so is it disabled because, like theoretically, if it is disabled shouldn't play because there's places like with reference and you're displaying a you're doing the rendered entity and you have to choose which View mode or or if you're doing a view of nodes, and then you have to choose which View mode to choose with these disabled one show as options so.

A

B

A

Lets that that's the weird thing about it is that you can, you can configure views or reference or whatever it is you used like the full content view mode, even if the full content view mode isn't actually any difference or enabled or whatever you want to call it. It'll just fall back to the default, so it's confusing about it is that they're always enabled so yes, I was highly customized. Argue.

B

Against hiding them with it because they are in play, even if they're not customized, and there should be like a list of them. So yes, I think this. This is better than the other one. That was hiding it, because you need to know that these exist, because then, when you go to select them somewhere else, they show up in the list. Yep.

A

And so that's exactly the two sides of the coin that that we have have this problem I would as strong here I. Actually, I favored the other approach that I prefer to hide them for the reasons that I've stayed here and your point is totally valid as well. I'm, not really sure how to resolve this. We're at a point where, like other people like dr. Wilmont, are also saying that is as well so I know what to do. It's not not that either approach is really bad.

A

It's really just deciding which one is better because both are better than what's then what we have currently and what's an interval aight, I feel so it's really yeah, I'm not quite sure how to resolve it. What's in the PR 0 PR right now is the one where they're hidden where they're in a select list, yeah.

B

Actually looks like looks like looks like there's.

A

Two options here: actually, I can probably even pull up pull up the sandbox.

A

B

Leave the people can be deleted right.

A

Some of them can yeah um first, okay, so this is oh I'm. Sorry manage displays. Is that I always thought that was huh okay. So here's what it looks like right now and the the reason why I'm a fan of this is that really in most situations you don't actually need more additional view. Modes like few modes are not a kind of an advanced topic and it really puts the focus on what your extra are interested in the default view mode and the teaser.

A

And then, if you want to add an additional view mode, you choose which one it is or if you want to add a customized one. So these ones are the hard code, big ones like for content, and so now that one is now added. But if you want to add a new view mode entirely, you know like slideshow or something like that. You give it a label in a machine name, and then this one actually can be deleted, but.

A

Yeah, you can see the options here so reset to default, means use the default settings again and a delete actually would remove that few mode entirely.

D

I'm generously, something that of course not see how you've added the full content least they're right what what was the purpose of hiding it you've added it there. Now it's there, you haven't customized it. Yes, yet so, what's the point of having it there except say, somebody adds it like what you've just done, but you haven't customized it. So what's the difference between this one, as it is now non customized than the other ones that are hidden.

A

For one difference now is that if I were to change the default view mode at this point, it would not affect for content. All content is now a copy of what default used to be, and so, if I change default, like you're, like a managed display here, is like okay, well, huh I think I may have a bug here, because this, because there's nothing actually copy anything, it just says everything all hit, but so I guess. Actually. This is something different in that the view mode when I turned it on it shouldn't do this.

A

It should copy what the default is and then from then on. If I change the default, the full content stays the same. Oh.

D

Yeah I get it so if you bring more, if you bring the moment that you bring more in by the ad or customize existing ones, I mean they copy the default or the support yep, excluding the bag that just happened, they're supposed to copy that default and then from then on, you can is customizing yep.

B

Just speaking from speaking for myself before hidden things where you have to go and into that extra page and select them and stuff like that, will drive me crazy. Just that I don't like to be so many extra clicks.

B

Okay, that's an ottoman and non discoverable, like you, don't know, what's like if you just want. If you just want the list of all the possible view modes for selection, you don't really have like one list. It's like you have to sort of add up all the ones that are enabled and then go look at the ones that are there to see.

B

Yes, I mean if I definitely prefer the second option where everything is just listed, especially since that was especially since that's the way that things are handled with, like like just disabled views and stuff like that yeah anyway. That's my two songs that.

D

Was that was the argument that Doc Leland? How does wed that's what he said non discoverability of the existing ones as well, I'm.

B

D

And I think I would do as well for the record I I.

F

Think there's another factor in the view modes can be a tricky enough concept to wrap your head around that unless you know what they are you're looking for as much contact session to figure out what they are right. So if, if most of them are hidden that that's removing information from you comers to figure out, you know what what it is. They're messing with ya.

A

So one thing that I've concerned around first of all noted everyone's opinions, so we might could might end up going that way. But an additional concern I have is that one change that we introduced here is that previously, when you into this page manage displays, you would immediately see this page that the default view mode with a collapsed field set down at the bottom, and so that made it.

A

So that's so that you were on the page that a new user and actually almost even in my own usage like a you know, this is the page that actually has the stuff that I care about, and it's been put one level deeper under this default option, and so with all of the view modes on the page, at the same time, which I'm not sure if there's actually a version of that something like this, that the default view mode, I mean it is at the top, but there's a lot of buttons on this page and a lot of links on this page to actually get to the page that I want, which is the default.

A

So I don't know, I've got a concern around you know. Taking the page, that's you know is the most commonly visited page and putting it a level deeper, but that's a problem with either approach, but I think that there's more going on this version that a new user might be might not get to the page that they want, which is the default display, and so why did we get rid of the cab?

A

The tabs uh I think it's.

D

What can I say something there I had a design there that with vertical tabs I know that it's wrong from my a from the design standards point I know it was wrong, but it was so fitting, like all nations, with discussing male hiding the the fields for the default one having to do a lot of clicks and everything. The vertical tabs just sorted.

D

Everything else, I think there is a mock-up a thing earlier than that that I had, but it was the issue of using a ue feature that is not meant to be used as such in such a way like the vertical task. Yeah.

E

When my thinking.

D

Was we're gonna.

E

Be redoing the field you I and that's really the core problem I feel like is we're just inheriting a lot of awkwardness and that's you.

A

Yeah and that's something that I've been trying to push towards in this issue as well as that dumb, the problem we're trying to solve here is adding custom few modes like that's it and the less user interface changes. We do to accomplish that goal better.

A

So yeah I also kind of agree about the the secondary tabs that that removing them is. You know we get more changes, but it's a one line thing to to get rid of them.

B

A

From a navigation standpoint, I find them to be useful, but the argument is being made that that secondary taps are a very like uncommon pattern and even within our own socks are like we very, very rarely use secondary tabs. There are places in common.

E

With meaning totally not recommended in a total violation of tabs right.

A

Yeah, so so just the pattern for secondary tabs is both uncommon and a little unfriendly, but I mean I don't really know about removing the secondary tabs myself. I, don't I, don't feel super strongly about it, but I'm also a little bit skeptical about removing them. So and it's like.

B

We could always remove them later hi, so maybe we could take it one step at a time here. The only thing is with the operations then we'd end up with a situation like with the views you I, where we have the secondary tabs for the different view modes and then like an Operations button over to the right or something like that when you're actually looking at the view mode, right and I, think.

A

That that's the thing is that like for something like managed fields, for example, we don't have a secondary tab of every field, for example, so it makes it so this so now I'm, you know, I've got the breadcrumb going on, but other than that you know, I'm, not yeah I'm, not in a secondary tab anymore.

G

Yeah, can you change which view mode is the default view mode now.

A

The default view there's always a view, mall view mode called default and it's always the default.

G

Can we have a tab? That's managed display, just like it always was in a separate tab. That's managed displays or manage view modes. That shows all the view modes that you can do things with and if you customize one then it becomes available. I manage display.

A

So you suggesting that we have another primary tab up here. Is that bad? Yes? Oh so.

C

Thankfully feel the first one would be the default one and then another one for other one. The first one would be the one that the note is using to render well.

B

They're all being used for the note to render at different circumstances, he's.

E

Saying manage display stays as it is, and there's a new tab that handles fee modes like creation kind of stuff. If.

B

You had it that's that's very confusing I crap: where does it somewhere? Does that and it's very confusing yet.

D

Doc will does initially had a separate, not with me the content type, a separate plates that was scrambling. The whole thing was one of the designs, but we turned it out. I got camera or why? But it was a totally super separate nights. I think either structure.

D

So it was, it was, it was not within the primary tabs of the content. Type itself was none of the previous designs. Yeah.

A

Let's see so seems like we're, kind of I mean actually. Actually there is some agreement here amongst the people, at least that are on this, call that that we don't like putting them under the add new thing, yeah, so I think it would be most valuable if everyone that has an opinion could post their opinion as so or as it is to the issue queue so that we get it more than just on this.

A

Video call, although I can summarize there as well, because we do need like we just need to figure out how we want this to be split, display, does user interface, the oh and actually apparently enabling 10. You know not not copying from the default.

A

There is test coverage that Jenna's been adding, but it seems like it's incomplete because it should, you know, account for a situation like that.

A

Okay, um you guys have more feedback there more discussion that we should have about this I sort.

B

Of want one question: was there discussion about? Why calling it a view mode as opposed to a display mode.

D

B

It ready, sir, you.

D

Have a separate issue of that side: okay, because.

B

Of it, because because it's under like manage displays, then it makes sense to call them display modes. Yeah.

A

We yeah it's. We separated out into a separate issues specifically because it got it got messy yeah, because.

D

You modes, which was sort of like making an association with views, yeah Fleming.

B

D

Admin but yeah we have a separate II, shall find it in the post. Ending was.

B

The argument for calling a new mode well.

A

If they're already view modes, okay,.

B

And yeah I me, nuts and.

D

That's what Drupal 8 calls them as well. So if.

A

You have people coming.

D

From Drupal 8 they will we yeah and.

A

And, more importantly, there's api's that call it via modes. So your anyway.

B

A

That discrepancy there, young.

B

Yep inherited Drupal crap yeah.

A

Okay, wow there's a lot going on there more than more than I might approach, but plaintiff.

B

Process, this is actually a good discussion. It almost would make sense if we had like some sort of meetings to discuss these big issues. More often yeah.

A

Well, we know I mean we do have them on a weekly basis, but I think.

B

We have so many things on those calls that would just sort of gloss over all the details. Yeah, maybe if maybe, if we just choose one issue, to focus on for that meeting like a deep dive for each week or something.

E

That's been the plan where we talk about it after this after this meeting. If we want to do that for next week, I don't know how successful it's been, but I think that was the idea. We talked about a low back.

A

Okay, yeah yeah. We can do exactly that, although we just talked about this particular issue so, but that is the idea of the the follow-ups that we could in theory, you know schedule some action for to like discuss further after the meeting, so it is possibility if we need to that on this topic or another one at the end of the call.

A

Alright. The last item here is adding a file view which is 2375 Gregory. You gave this review. Thank you very much. Would it be possible for you to give a summary of the status of this pull request.

D

I, don't remember the review. huh Sorry I, don't remember if I did a thorough code review, because usually what I do is I look at that you're talking about the file, adding the file view right. Yes, that's right! Yeah, all I did was just not really just run through and I'm, not sure if I would be just. Let me quickly jump to that issue. I mean. Maybe the review is just going through it quickly and just looking at the user interface and the text mainly and let's see yeah, let's fly gum.

D

Why I see I see I see that I see the thing? Yes all right,.

F

A

You've got so there's a lot of things. Yeah you've got some good ideas here that, like we need a confirmation. Well, the confirmation should be should tell you if a file is in use and linked to the places where the files in use, so you can see it before you delete it. That's a great idea: yeah.

D

And there were some glitches as well like if you delete a file from the slimmest see again, if you deleted a file from one of the operation links available as in each role of its file, we would ask you would get you a confirmation dialog, but if you did it from the math operations, it wouldn't ask you, we just go ahead and delete every file.

D

So that's that was one thing thing.

D

Yeah, that's the second point that I say so. If you click the delete button available in the operations column greats file, it gets you to a information. Dialog, sorry a page, but if you do it through the dark complexion, drop-down menu, it just goes ahead and deletes everything so that got.

A

D

A

I think we have a confirmation page for that when we delete nodes we could adopt the same model. They're actually gives you some a little bit more elaborate, come from.

D

Yes and the other thing was that I tried deleting an image file created an article and then I went to be this view. The file view and I deleted damage. So I went to view the article again or actually edited and then I uploaded the same file. So I got to I got an error at the website in Canada and unexpected error.

D

And then the works? Okay, the letters logged in.

A

Okay, so it sounds like we have a number of issues here. The view itself is working and functioning, but has some improvements that are necessary, plus bugs that need to be worked out. Okay,.

D

Well, yeah and then in it some simple stuff, like the actual name of the dacian file being file admin I'm trying to get consistency with the other places that we are converting to admin views to be managed XYZ. So it should be managed files as a title and imitation file just just so that people can locate the views easily if they go to their active config folder.

D

And yes, so just just a few things. A few corrections in the view here and there also the tights title of the queue. If you have it as manage files, or if this makes sense, I have a screenshot there. But if you open the can I do that. Can I share my screen if I open d, the sandbox, the call request, just let me see if I can demonstrate what I'm talking in that real quick.

D

A

Can share my screen too, if you prefer Gregory I, don't know how to do mine. How do you do it? In the left hand, side barb that hang out there to draw right side that says green chairs. The second button all.

D

Right yeah I got that.

D

Okay, everybody can see it excite I.

H

Got the soil, so let me get there probably password.

D

There's a new website just out of the circuit.

D

So it should be knowledge files, so the the thing is: if you go to find content, this is well it's going to become manage content with one of my full requests and also this.

A

D

To be Malik's content as well and now lemons file class yeah, so this is all under content, so it should be content manager is instead of manage files manage files, because I have other pull requests that are replacing this with the view and it's again manage content comments, so in content, planets comments and then also these changes to content manage content. So everything is under a title that says content and then it's manage content manage comments, manage files yeah. How.

A

I'm, sorry that the title of this page is admin content by the way.

D

Is a wonderful request for it that recur ex it? So it's another issue: it's one of the small issues that I'm fixing all the the views. Small issues like that egg, fine to change the just the content and this becomes manage content, and this becomes manage comments and all these are views. Excellent, okay,.

H

Great, how do I stop this creature now? Okay, can.

G

We move an entire config file to the active config in an update hook.

A

um You could, but I don't owe you could, but that's it's not a very safe thing to do, because what happens is if you just copied an existing config file like the one that ships with the module and just copied it all in it. That makes it inconsistent in the future. If we were to change that config file in the future and also have an update hook that changed it, you would end up with like an old site that updated would copy a newer config file than the previous then like gosh.

A

This is confusing to explain it's the same reason why you can't copy you, while you can't use hope, schema to update a database table because hug scheme of my change or the config file might change, and so the future version that gets changed. The update hook will be expecting the old version and then subsequent update hooks will build upon the old version. That might not be the one that got copied in anymore if that makes some sense. So when it comes to, if.

G

You're, upgrading a site, this view doesn't show up. If you install a new site, this view shows up. So we need something to say: hey, there's a new, because it's the because the default config doesn't get into active config unless you go through an installation, yeah yeah. So.

A

Although it's inconvenient, the way that will have to do this is will take the config JSON and then turn into an array and then take copy paste. The entire array into the update hook and then save the config file. That way so I hosted.

D

An easy question about this by the way and the way we have two ways of doing it. There were two full requests that actually did. This whole thing copied the entire JSON file as a enough in a format of an array, and there were another- took two bull request, but what they did is they read the JSON file. They config that could befall config Stuart building a data object outside, and then they did Jason d'accord on that I have an issue.

D

Just let me find it real, quick again have an issue claire, and I was asking why the hell we were doing it differently and it seems like that. The update hooks in the two full requests were like huge code, they're just copying over just.

H

Let me find it real, quick.

A

Yeah, but it's similar to any other config file. That's um whenever we created a config file like all of the stuff that was copied out of variables in Drupal, 7 and then put into config and in fact drop or or with we created a new module or create a new config file. We never copy the file out of the config directory and just load it into the active config directory for the same reason.

A

So whenever it would create a config file, you actually need to code it exactly the way the default config file needs to be in the update hook and then just like config save, and that makes it so that the starting point is always consistent. So subsequent update hooks that build on that the build on modifying that config file will all get the same expected output, while new sites will use the default config file that that's in.

G

The config directory, so config save knows to make a brand new file if one doesn't exist. Yep. Okay, I.

D

Can either where were pull request that actually was checking if the config is immune? Does that function that says config? Sorry there was a tech, beef configured new son. So was this code? Sorry excuse? That is what happens.

D

A

Yep, but either way both you guys are definitely right that we need an update hook. That actually creates this view for existing sites. There are I mean we do a fair amount of you know if you update your site from an old version of backdrop to a new version of backdrop that the new functionality is there, but it's not turned on, but this is a situation that's I feel like.

A

It should definitely be there just as a manner as a matter updating your site from one person to the other, because this is modifying the way things work or adding a new feature to an existing system that would change its behavior. This is a standalone thing that is entirely by itself.

D

Also another thing that I wanted to ask the chick what happens but seeing we are replacing those those legacy triple seven pages with views, but but we allow these views to be disabled. So if it is stable, if you disable the manage content or admin content view, then people lose the entire menu of find content. That is.

B

D

Don't know if we, if this is desired, because people might actually want to replace the view that we have the fair on but I don't like it's a little bit of allowing the Guinness to shoot themselves in the foot. Just saying yeah.

A

Yep, that is, that is the case and I agree, but let's, um let's make a new issue of probably for that for the discussion, yeah, okay, that's it! Those are the three main items for 1.6. It's funny. I was feeling really good about the lab latter two entity view modes and file view, but now, after talking about them, I'm feeling a little less confident even about them, but we have.

A

We have a couple of days to get them into a committable state and then a couple of weeks to actually do follow-ups to fix any bugs that that we've accidentally introduced. So we've got some work to do. We've only got today, let's say three days to actually polish these things up and any other issues that are tagged for the 1.6 release. So I'd say we should put our focus on any few modes in the file view which seemed like they both have small bugs and upgrading issues and testing issues.

A

So that's where our focus should be for the next couple of days and we'll we'll see where we are by next week. We will be in feature, freeze and we'll discuss. You know the things that we need to do to actually prepare for the week, so I prepared for the release next week.

A

That's it anybody else. Do you guys have anything that you would like to add.

A

Okay, anything that we should talk about next week that that we would like to add to the agenda yeah, not really I, think I. Think sticking with our focused agendas up until the releases. That is a good idea. So, okay, that's it! Thank you! Everybody for watching, think you are ready for joining, we'll, see you guys and get her in an issue queue and, let's, uh let's keep cracking all right, bye. Everybody.