WEBVTT 00:06:53.000 --> 00:07:00.000 Safe button and go back adding a new in air quotes translation. It's a good thing, but in other contexts, having a second button complicates things. 00:07:00.000 --> 00:07:14.000 So. Keeping a simple, we came up with some second. My initial thought was 00:07:14.000 --> 00:07:24.000 Having on all the pages a second button, but that is an overkill and the issue would be 00:07:24.000 --> 00:07:32.000 Hold back longer and longer but That way in the context of the translation, overview page is a good thing. 00:07:32.000 --> 00:07:40.000 The only 2 things. I've noticed during the write up in the discussion during. 00:07:40.000 --> 00:07:52.000 The, was, If you have a on the admin content page, if you filter the page for for example, the content type basic. 00:07:52.000 --> 00:08:05.000 Basic page. If you come back. After adding a new translation for example, then your the filter settings are lost and you are not. 00:08:05.000 --> 00:08:16.000 Coming back to that set filter settings you left off. And that is a detail. We have. Noted during the meeting. 00:08:16.000 --> 00:08:22.000 And the other detail is. 00:08:22.000 --> 00:08:23.000 Okay. 00:08:23.000 --> 00:08:38.000 If you are on the translation overview page and you edit a new translation and you come back into the context for example you have 3 or 4 trans, languages installed and you've added for example. 00:08:38.000 --> 00:08:51.000 On an English page, French. And you have already German installed, edit. And you have set your translation to English, for example, for the admin pages. 00:08:51.000 --> 00:09:06.000 Then Literally, it's pretty overwhelming to know in which context you actually are and where you will direct it to if you push the edit button. 00:09:06.000 --> 00:09:07.000 That is pretty. 00:09:07.000 --> 00:09:09.000 If you push the edit button. 00:09:09.000 --> 00:09:14.000 Yeah, in the in the primary tabs. 00:09:14.000 --> 00:09:30.000 Which which Note that edit button refers to. That is not very clear. In particular, with 2 open issues, I am, I can post the link when I finished the write up. 00:09:30.000 --> 00:09:38.000 And end up in the picture. Illustrating, the issue. It's not very clear. 00:09:38.000 --> 00:09:45.000 You understand it, you can assume it, but it's it makes at least makes us think. So. 00:09:45.000 --> 00:09:47.000 Tricky. 00:09:47.000 --> 00:09:49.000 Hey, hi, Sima. 00:09:49.000 --> 00:09:52.000 I see. 00:09:52.000 --> 00:10:01.000 So does anyone have any issues that they're ready to discuss today? 00:10:01.000 --> 00:10:08.000 I've been working too hard at my day job. I, didn't have any time to think about what to talk about. 00:10:08.000 --> 00:10:18.000 The the might be the issue I've already mentioned last week. About the wordsmithing in project browser. 00:10:18.000 --> 00:10:22.000 For the 00:10:22.000 --> 00:10:23.000 Hello. 00:10:23.000 --> 00:10:26.000 We've brought up already a few weeks ago. 00:10:26.000 --> 00:10:27.000 Okay, are you ready to? Leave discussion on that? Do you want to share your screen? 00:10:27.000 --> 00:10:33.000 Good morning. Yeah, I can one moment. 00:10:33.000 --> 00:10:39.000 Okay, Quinn, Simo, anything from you? 00:10:39.000 --> 00:10:41.000 Not today, yeah. 00:10:41.000 --> 00:10:51.000 Okay. 00:10:51.000 --> 00:10:52.000 Hello. 00:10:52.000 --> 00:11:11.000 I was thinking about that. Block visibility on. 404403 pages what we discussed but I don't know if we have enough to to actually have a recommendation about that but I know I was checking that discussion and I kind of I didn't notice us reporting anything from the previous 00:11:11.000 --> 00:11:18.000 discussion. To that. 00:11:18.000 --> 00:11:24.000 So I didn't notice that comment. 00:11:24.000 --> 00:11:31.000 So maybe we could look what's the status of that one. 00:11:31.000 --> 00:11:38.000 Okay. So let's see, just. 00:11:38.000 --> 00:11:45.000 I'll paste into the chat. This is the link. I think this is the issue. Sima just mentioned. 00:11:45.000 --> 00:11:50.000 And. 00:11:50.000 --> 00:11:55.000 Okay. 00:11:55.000 --> 00:11:58.000 Ralph, can you post the link to the issue you're looking at? 00:11:58.000 --> 00:12:07.000 Oh, sorry, yeah. 00:12:07.000 --> 00:12:14.000 Thank you. 00:12:14.000 --> 00:12:19.000 Let me start. 00:12:19.000 --> 00:12:26.000 Welcome, this is the duple usability meeting for June second, 2023. I'm Benji Fisher moderating and also here. 00:12:26.000 --> 00:12:33.000 Our Ralph Kohler sharing his screen. He'll start off the discussion. And Quinfam. 00:12:33.000 --> 00:12:36.000 And Simo Hilston. 00:12:36.000 --> 00:12:45.000 Okay. We're looking at issue number 3, 3, 2, 3, 3, 5, 4. 00:12:45.000 --> 00:12:53.000 It's in the project browser queue, review all pop-up messages shown by Swell UI and Stella for user friendliness. 00:12:53.000 --> 00:13:03.000 It's an issue. We've already touched in an usability meeting a few months ago. 00:13:03.000 --> 00:13:16.000 Back then we were only able to cover a single Hero message. And Ben she also made a comment, 6 months ago. 00:13:16.000 --> 00:13:33.000 With a few recommendations and after that we worked on trying to improve it. Before and I I have to know the only detail that will recommended. 00:13:33.000 --> 00:13:43.000 To avoid using the term staging. Aria. 00:13:43.000 --> 00:13:49.000 And. Use something else. 00:13:49.000 --> 00:14:03.000 We've tried, but basically it ended up. Staging area could be also used not necessarily in the context of composer, but staging. 00:14:03.000 --> 00:14:14.000 An area for preparation. So, We just could go through the messages. I've created, a text file. 00:14:14.000 --> 00:14:28.000 In italic is the current state. The first message would be. A stage cannot be unlocked while applying. 00:14:28.000 --> 00:14:37.000 For 2 of those arrow messages, I've edited a few, a bit of context. 00:14:37.000 --> 00:14:46.000 What it actually means. Most of the other, error messages. Are sort of self explanatory now. 00:14:46.000 --> 00:14:55.000 Those 2 are the only ones that needed a bit. Further context. So basically, stage,, a stage cannot be unlocked while applying. 00:14:55.000 --> 00:15:06.000 Christmas, yes, project browser could be used by multiple users simultaneously, technically, so it's possible that user B is installing a multiple and user A is trying to install something. 00:15:06.000 --> 00:15:15.000 So it could be. Very hidden from them. Maybe something along the lines and the suggestion now is the staging area area cannot be unlocked. 00:15:15.000 --> 00:15:23.000 While another module is being added, try again in a few minutes. Should we go through? 00:15:23.000 --> 00:15:36.000 All the messages at once first and then step through with comments or should be Go one by one. 00:15:36.000 --> 00:15:37.000 Okay. 00:15:37.000 --> 00:15:51.000 I think one by one will be. He's here. And this. Can you say again, Why are we still talking about staging area? 00:15:51.000 --> 00:15:59.000 I mean, I thought the primary recommendation the last time we looked at this was that staging area means nothing to someone. 00:15:59.000 --> 00:16:13.000 Using this module. Why are we talking about it? I mean, I know that technically it means something and that's the root of the problem, but. 00:16:13.000 --> 00:16:19.000 You know, from the users point of view, this is. 00:16:19.000 --> 00:16:23.000 From a users point of view. 00:16:23.000 --> 00:16:26.000 From my understanding. 00:16:26.000 --> 00:16:36.000 I think staging, just communicate something is prepared. 00:16:36.000 --> 00:16:41.000 And that was the reason why we stuck. 00:16:41.000 --> 00:16:55.000 With staging area because we've tried a few other alternatives but those go. Got lengthy and wordy and Staging was the 3 fifth. 00:16:55.000 --> 00:17:16.000 And the most concise. But yeah, if anyone has a better idea. More than welcome. 00:17:16.000 --> 00:17:36.000 What are the reasons there are not being able to. That on other module while one is already being added, then unlocking staging area. 00:17:36.000 --> 00:17:47.000 So what other cases there are when a user cannot add. A module while another module is being added. 00:17:47.000 --> 00:17:52.000 Because the staging area is locked in that case. When a module that. 00:17:52.000 --> 00:18:04.000 Yeah but what are other cases when you should kind of add module while another one is being added because I think it's kind of a I'm thinking that. 00:18:04.000 --> 00:18:13.000 Would it be enough to say that? You cannot add another module. You'll kind of add a module. 00:18:13.000 --> 00:18:24.000 . One other module is being added or something like that so that it doesn't need to does the user need to know that the reason is that staging area. 00:18:24.000 --> 00:18:41.000 Kind of be unlocked. So it's just to tell that you can't add another module before this something is finished. 00:18:41.000 --> 00:18:42.000 Okay. 00:18:42.000 --> 00:18:45.000 So first of all, I've, pasted a link into the zoom chat. 00:18:45.000 --> 00:19:03.000 So, and anyone can. Log into that site using admin admin. And if you. Are logged in as an admin user and you go to the extend page and then the browse tab. 00:19:03.000 --> 00:19:09.000 You can see the current state of the. Project browser module. 00:19:09.000 --> 00:19:14.000 And I think that, for context. 00:19:14.000 --> 00:19:16.000 Help too, Ralph, if you could. 00:19:16.000 --> 00:19:34.000 Yeah, 1 s already. 00:19:34.000 --> 00:19:44.000 Okay. Oops. 00:19:44.000 --> 00:19:46.000 Oh, and do I have to enable? 00:19:46.000 --> 00:20:04.000 1 s and make it project, Oh no. 00:20:04.000 --> 00:20:11.000 Package manager version 2.5 or newer. 00:20:11.000 --> 00:20:19.000 Is package manager installed? 00:20:19.000 --> 00:20:41.000 Automatic updates is also needed. To be installed. 00:20:41.000 --> 00:20:53.000 Right now. 00:20:53.000 --> 00:21:23.000 Thank you. 00:21:23.000 --> 00:21:30.000 Oh. 00:21:30.000 --> 00:21:36.000 Well, maybe this is. Enough context for now. So this is the project browser. 00:21:36.000 --> 00:21:48.000 And, once once I get my test site set up properly. You will be able to download a module directly from user interface. 00:21:48.000 --> 00:21:58.000 Unless something goes wrong. And something goes wrong is what we're discussing. What are the error messages we should show? 00:21:58.000 --> 00:22:07.000 Yeah, and for the context. Without those errors instead of the view commands button you will have an add an installed button. 00:22:07.000 --> 00:22:19.000 And. After clicking that. And something goes wrong, those 10. Messages are the most common that will show up. 00:22:19.000 --> 00:22:24.000 If something goes wrong. So yeah. 00:22:24.000 --> 00:22:33.000 Yep, and in regards of, Suggestion that might 00:22:33.000 --> 00:22:46.000 I think. 00:22:46.000 --> 00:22:59.000 Yeah, I think that Simo was. Testing, something pretty much like what I had suggested, which is that we talk about another module is being installed. 00:22:59.000 --> 00:23:12.000 Rather than the staging area. Is locked. 00:23:12.000 --> 00:23:42.000 Seymour's suggestion is a new module cannot be added before previous module installation is completed. 00:24:02.000 --> 00:24:07.000 Some actual text to replace that. Shall I try? 00:24:07.000 --> 00:24:11.000 I posted one in the chat. 00:24:11.000 --> 00:24:12.000 Okay. 00:24:12.000 --> 00:24:14.000 Yeah, that's border road, red. 00:24:14.000 --> 00:24:35.000 New module cannot be added before previous module. Installation is completed. 00:24:35.000 --> 00:24:52.000 I would say something like yeah. If the information and then suggest the action. So. First a short sentence, another module is being installed. Period. 00:24:52.000 --> 00:24:58.000 Nice and short. 00:24:58.000 --> 00:25:27.000 Try again in a few minutes. So keep that part from the, from the current message. 00:25:27.000 --> 00:25:32.000 That's cool. Kind of one of the ideas that came looking at that one. What's that? 00:25:32.000 --> 00:25:47.000 You caught install this module but we are installing another module. Instead of that kind of a but it's not really something that would be kind of misunderstood but it kind of reminds me of. 00:25:47.000 --> 00:25:56.000 Replacing one. Something like in a pharmacy sometimes they replaced one medicine with another one that does the same. 00:25:56.000 --> 00:26:10.000 So this kind of up. Because that's something that. Happened to me yesterday so that kind of reminded me of that one but I think there is no really possibility for misunderstanding that one. 00:26:10.000 --> 00:26:15.000 So I think the short choice better. 00:26:15.000 --> 00:26:19.000 The only detail in regards of the another module is being installed. 00:26:19.000 --> 00:26:22.000 Okay. 00:26:22.000 --> 00:26:41.000 If I'm not very technical savvy and I read another module is being installed, I wonder Have I initiated that installation process? 00:26:41.000 --> 00:26:42.000 Okay. 1 s. 00:26:42.000 --> 00:26:47.000 And Quinn has a suggestion in the chat. The previous module installation before adding a new one. 00:26:47.000 --> 00:26:58.000 And I think the issue here with both of those suggestions is that. As the the explanation above says. 00:26:58.000 --> 00:27:07.000 We don't know. Whether the current user is installing another module or possibly some other user. 00:27:07.000 --> 00:27:17.000 Some other admin user is already running an installation. 00:27:17.000 --> 00:27:22.000 So 00:27:22.000 --> 00:27:29.000 You know, if I haven't started the installation telling me that I should complete that installation. 00:27:29.000 --> 00:27:59.000 Seems like a confusing message to me. 00:28:06.000 --> 00:28:17.000 Would it make sense to add to your suggestion, Benjy, another module is being installed by another user. 00:28:17.000 --> 00:28:25.000 Well, it could be also that if somebody keeps multiple, windows, so. There is actually by the same user. 00:28:25.000 --> 00:28:37.000 Kind of. 00:28:37.000 --> 00:28:46.000 So kind of a really used case would be that somebody is updating. A certain module for or installing a certain module for. 00:28:46.000 --> 00:29:01.000 Maybe 3 similar sites and just click having them in different tabs and clicking is to install install but instead of having 3 different sites is having one in 2 process, at 2 tabs. 00:29:01.000 --> 00:29:09.000 Okay, so first of all, I think the original text, has one advantage over mine uses added rather than installed. 00:29:09.000 --> 00:29:13.000 So can you change that? 00:29:13.000 --> 00:29:24.000 And, you know, since we don't know if it's another user or current user. I think we should just Keep it short. 00:29:24.000 --> 00:29:29.000 Say what we know. 00:29:29.000 --> 00:29:35.000 Seem was a point. 00:29:35.000 --> 00:29:42.000 So just another modules being added to try again in a few minutes. 00:29:42.000 --> 00:29:53.000 That's my suggestion. 00:29:53.000 --> 00:29:57.000 Yeah. Plus one from me. 00:29:57.000 --> 00:30:05.000 I mean, if you think it's important, you can add a sentence that it might be another user or might be yourself. 00:30:05.000 --> 00:30:13.000 I don't think that makes it any more actionable. I don't think it's worth. 00:30:13.000 --> 00:30:17.000 Adding an extra sentence but if you think it's it's an important distinction. You can. 00:30:17.000 --> 00:30:28.000 Not necessarily. The long I think about it. Keeping a brief Might do the trick. 00:30:28.000 --> 00:30:30.000 Less is more. 00:30:30.000 --> 00:30:32.000 Indeed. 00:30:32.000 --> 00:30:36.000 Quintimo or are you? 00:30:36.000 --> 00:30:45.000 Are you okay with that? Do you hate that raising? 00:30:45.000 --> 00:30:52.000 I'm okay with that. I'm just thinking about. Add in to your sentence. 00:30:52.000 --> 00:31:03.000 The install cannot continue. But I'm still working on that sentence. I don't know how to add it in it. 00:31:03.000 --> 00:31:07.000 Because clearly we cannot 00:31:07.000 --> 00:31:20.000 I mean the installation process cannot proceed right now, right? So somehow we need to get that message in. 00:31:20.000 --> 00:31:30.000 No, I think the fact that you push the button that says add this module. And an error message pops up, I think in a modal window. 00:31:30.000 --> 00:31:39.000 It's pretty clear that Okay. But it's not going to go ahead. 00:31:39.000 --> 00:31:44.000 Oh, I see. So it's already add. 00:31:44.000 --> 00:31:54.000 Just for the context, everything in regards of staging and composer is during the app process and the install process. 00:31:54.000 --> 00:32:04.000 At the later point, is then the actual install, the add is all everything in relation to composer. 00:32:04.000 --> 00:32:21.000 I see. 00:32:21.000 --> 00:32:26.000 So shall we go on to the next? 00:32:26.000 --> 00:32:27.000 I'm ready. 00:32:27.000 --> 00:32:36.000 Unlock message, install staging area unlocked. 00:32:36.000 --> 00:32:42.000 That's again the problem. 00:32:42.000 --> 00:32:48.000 The whole message is above the staging area and keeping that out. 00:32:48.000 --> 00:32:52.000 It's complicated. 00:32:52.000 --> 00:33:01.000 The suggestion was the chasing area has been unlocked. New modules can be added again. 00:33:01.000 --> 00:33:12.000 Or should the first sentence be striped and just new modules can be added again? 00:33:12.000 --> 00:33:19.000 I think that would be an improvement. Again, less is more. 00:33:19.000 --> 00:33:24.000 Oh 00:33:24.000 --> 00:33:34.000 So again, you know, the. You know the recommended pattern is describe the state. And describe the next steps. 00:33:34.000 --> 00:33:41.000 We'll just try to resolve it. 00:33:41.000 --> 00:33:50.000 And that also pad under the actual State is described in the first sentence and in the second sentence. 00:33:50.000 --> 00:33:58.000 Are the next steps that could be taken. 00:33:58.000 --> 00:34:12.000 But the second sentence should we directly address the admin user and say, You can now. At another module. 00:34:12.000 --> 00:34:23.000 So Quint suggests in the chat. Staging area unlocked. You can now add new modules. 00:34:23.000 --> 00:34:34.000 And I still think the goal here is to remove all references to the staging area because you know, looking at the project browser. 00:34:34.000 --> 00:34:55.000 I don't see a staging area. That's something hidden behind the scenes. So I never want to the user interface to refer to the staging area. 00:34:55.000 --> 00:35:08.000 How about taking out the wood staging? So you can see the area unlocked. You can now add a new modules. 00:35:08.000 --> 00:35:15.000 Oh. Bye. I don't think that helps. It's what area. 00:35:15.000 --> 00:35:16.000 Yeah. 00:35:16.000 --> 00:35:27.000 Where's the key? How do I lock it or unlock it? 00:35:27.000 --> 00:35:28.000 Good point. 00:35:28.000 --> 00:35:40.000 So. So second sentence I think is an improvement. It's not in the passive voice. Like new modules can be added again, that's passive voice. 00:35:40.000 --> 00:35:52.000 So the 00:35:52.000 --> 00:35:55.000 How about 00:35:55.000 --> 00:36:00.000 Oops. 00:36:00.000 --> 00:36:13.000 You can now add. Again. 00:36:13.000 --> 00:36:17.000 I think with again it implies that something 00:36:17.000 --> 00:36:33.000 Was it possible before? And it's now possible again. And that action is adding new modules. 00:36:33.000 --> 00:36:48.000 About something sort of big like The system is ready. Or I prefer full sentences, but maybe this would be a case where we could just say system ready. 00:36:48.000 --> 00:37:04.000 Call it. You can now add up. You can add a new module again. 00:37:04.000 --> 00:37:15.000 Yeah, I like it. Yeah. Clear and simple but provide enough information. 00:37:15.000 --> 00:37:19.000 Would it make sense instead of system just 00:37:19.000 --> 00:37:27.000 Replace with project browser is ready, you can add a new module again. 00:37:27.000 --> 00:37:32.000 Yeah, I think I think that's better than system. 00:37:32.000 --> 00:37:44.000 Although Again, this is project browser used in the user intersect. And face, you know, the page titles, browse projects. 00:37:44.000 --> 00:37:48.000 Technically, it's a package manager. 00:37:48.000 --> 00:37:52.000 Which is ready again. 00:37:52.000 --> 00:38:00.000 Problem is actually just. Yeah, true. 00:38:00.000 --> 00:38:06.000 But if you use Package Manager is ready, then 00:38:06.000 --> 00:38:23.000 Most users don't know what package manager actually is. And that might be confusing. 00:38:23.000 --> 00:38:32.000 Yeah, I'm. 00:38:32.000 --> 00:38:43.000 I think we can leave that decision to. The people working on the issue. People working on the project browser, whether they want to. 00:38:43.000 --> 00:39:04.000 Use the term project browser in the interface or whether it use something big like system. 00:39:04.000 --> 00:39:13.000 Okay. 00:39:13.000 --> 00:39:19.000 Any objections or shall we? Move on to the third. 00:39:19.000 --> 00:39:21.000 I'm ready to go on to the third. 00:39:21.000 --> 00:39:31.000 Okay, that's the last one with direct, naming of staging and it's the most Complicated. 00:39:31.000 --> 00:39:46.000 And I'm uncertain if it works there. To leave staging, source UN unavailable cannot download project ID from any available source. 00:39:46.000 --> 00:39:54.000 Chris wrote, I don't see how this could be improved unless we can pass through. A further error from behind from composer. 00:39:54.000 --> 00:40:04.000 If the code is not currently doing that, it seems like it's pretty fatal. I think someone would have to adjust composer repositories or something in order to make this work. 00:40:04.000 --> 00:40:16.000 I could see this happening if we enable a repo of private modules, then try compose, install my private slash custom module, but the composer, Chase on doesn't. 00:40:16.000 --> 00:40:32.000 Have the private report added in it. If anything possibly adding, please check update your composer Jason and try again, I would have to look deeper at the coach to best understand when this error could happen so can't commit to adding the second sentence. 00:40:32.000 --> 00:40:42.000 And the suggestion is currently unable to download the project. ID module from any available source, this might be a network issue. 00:40:42.000 --> 00:40:51.000 Try again in a few minutes if the problem persists, check the sites composer chase them to be sure the project is available to composer. 00:40:51.000 --> 00:40:59.000 It's such a fatal error and the 00:40:59.000 --> 00:41:08.000 Odds very very low that someone might run into that. We tried to avoid. 00:41:08.000 --> 00:41:20.000 To use something contact your administrator or something like that because You don't know if someone has. A team or even administrator available. 00:41:20.000 --> 00:41:36.000 And also in that case. Being awake and avoiding composer at all. In that case, it might be the wrong choice and therefore we directly addressed the composer Chason. 00:41:36.000 --> 00:41:52.000 In that particular case. 00:41:52.000 --> 00:42:22.000 Yeah, I actually don't have a problem with this. 00:42:31.000 --> 00:42:38.000 And is that first message? Source unavailable and not download project ID from any available source. 00:42:38.000 --> 00:42:44.000 Is that what the project browser is getting from the package manager module? 00:42:44.000 --> 00:42:52.000 Yeah, and that's that's the string. Which, is used in 00:42:52.000 --> 00:42:57.000 This V UI installer fire. 00:42:57.000 --> 00:43:06.000 The pop up message. 00:43:06.000 --> 00:43:13.000 All those messages are the strings. That are used in that installer. 00:43:13.000 --> 00:43:16.000 Okay, so that's the current user interface text. 00:43:16.000 --> 00:43:25.000 Yeah. 00:43:25.000 --> 00:43:33.000 And and when it actually comes up, of course, project ID is replaced by. The name of module. 00:43:33.000 --> 00:43:52.000 Yep. 00:43:52.000 --> 00:44:01.000 Could this come up when? Like in those cases when you run out of some connection. Free connections and you need to. 00:44:01.000 --> 00:44:11.000 Activate like, activate. Another token to talk with the the repository. 00:44:11.000 --> 00:44:23.000 So sometimes with composer, kind of get those. Like get some activate some new tokens to be able to download all the stuff. 00:44:23.000 --> 00:44:35.000 From the repositories. So I'm thinking could this happen at a if there is a one server with multiple sites. 00:44:35.000 --> 00:44:41.000 And because it's, I think it's, I, P related so sometimes it might be that. 00:44:41.000 --> 00:44:51.000 Downloading to a single IP. Oh, it's restricted and then you need to do something with it. 00:44:51.000 --> 00:44:54.000 Tokens or something like that. 00:44:54.000 --> 00:44:58.000 Yeah, there are all sorts of things that could be it. You know, there might be a proxy involved. 00:44:58.000 --> 00:45:12.000 There might be. Network failures. There might be a problem at the source like. 00:45:12.000 --> 00:45:40.000 You know, Drupal ski lab. Might might not be responding. 00:45:40.000 --> 00:46:00.000 . I don't think we need to change it 00:46:00.000 --> 00:46:06.000 Now we move on or Seymour or Quinn? 00:46:06.000 --> 00:46:13.000 Yeah, we can move on. I think the same thing. I don't have anything to add on that. 00:46:13.000 --> 00:46:23.000 So I actually think that, after making these suggestions on the first 2, We might just stop there. 00:46:23.000 --> 00:46:31.000 Say number 3 is okay. I think number 4 is also okay. Just looking at it briefly. 00:46:31.000 --> 00:46:40.000 And. People working on the project browser issue. Continue from there. So the question is we have 20 min left. 00:46:40.000 --> 00:46:50.000 Would we like to continue working on this? Or would we like to look at another issue? Seema, there was one that you we're thinking of bringing up, right? 00:46:50.000 --> 00:46:54.000 Yeah, but I think it might be a long one. 00:46:54.000 --> 00:47:02.000 But we could do a check on that, like, I'm trying to recall what we were talking about. 00:47:02.000 --> 00:47:04.000 Before. 00:47:04.000 --> 00:47:13.000 I think I put a link into the chat of the issue you were talking about if you scroll up in the chat. 00:47:13.000 --> 00:47:31.000 It's 2 2 4. 5 7 6 7. 00:47:31.000 --> 00:47:48.000 Yeah, that's fine. That's one. 00:47:48.000 --> 00:47:56.000 I'll share my screen. 00:47:56.000 --> 00:48:04.000 Let's find right window. Yes. 00:48:04.000 --> 00:48:20.000 Okay. 2, 2, 4, 5, 7, 6, 7. Allow blocks to be configured to show or hide on 200 slash of 3 slash 404. 00:48:20.000 --> 00:48:29.000 Response pages. So those are HTTP response codes. 200 is a successful. 00:48:29.000 --> 00:48:42.000 Connection 4 of 3 means access denied or forbidden. Or of course page not found. 00:48:42.000 --> 00:48:51.000 So let's see, we talked about this at the end of March. And that issue looks like it's still open. 00:48:51.000 --> 00:49:05.000 Probably because we haven't Left to comment. 00:49:05.000 --> 00:49:23.000 So if I remember correctly, one of the. Ideas. Was. Instead of adding And maybe I should also. 00:49:23.000 --> 00:49:33.000 Just for context, go back to my. Site and structure. 00:49:33.000 --> 00:49:43.000 Lock layout. When you're configuring a block, any old block. There are various. 00:49:43.000 --> 00:49:55.000 Conditions you can. Use say only put it on English pages or only put it on Spanish pages. Specific paths that can be included or excluded. 00:49:55.000 --> 00:50:06.000 And the proposal this issue is to add, another. Section here. And say, only show it on. 00:50:06.000 --> 00:50:16.000 Regular response pages. Or only show it on access denied pages or never show it on access to night pages or. 00:50:16.000 --> 00:50:22.000 Only show it or never show it on page not found. 00:50:22.000 --> 00:50:30.000 So for example, the search block. 00:50:30.000 --> 00:50:37.000 I duplicate this tab. 00:50:37.000 --> 00:50:48.000 No, such. Hey, this should give me a 404 response page not found. And the search block does show up. 00:50:48.000 --> 00:50:55.000 So this would give us the option to say, no, the search page should not show up on 4 or 4 pages. 00:50:55.000 --> 00:51:05.000 Or some alternative search page should show up on 4 or 4 pages. And one of our suggestions was rather than adding a new condition. 00:51:05.000 --> 00:51:27.000 Which is what the current issue does. Is to extend. This text field. Which already since uses Front as a special. 00:51:27.000 --> 00:51:35.000 A special path. So right here in the help text. That front first the homepage. 00:51:35.000 --> 00:51:47.000 And also extend this so that 404 refers to a page not found. And 4 or 3. 00:51:47.000 --> 00:51:57.000 So that was one suggestion. Simo, do you remember the other? Things we discussed. 00:51:57.000 --> 00:52:08.000 I don't remember because this is the one that I thought was best. So I think we were talking about. 00:52:08.000 --> 00:52:13.000 Negating. Possibility for 00:52:13.000 --> 00:52:29.000 I think that current proposal in the issue but 00:52:29.000 --> 00:52:33.000 Is used so much on every site and we are like as a country module. Yeah, I'd be happy to have this. 00:52:33.000 --> 00:52:45.000 Separate. Vertical tab there. But when it's core then it's included in all sites in all blocks. 00:52:45.000 --> 00:52:54.000 So look, visibility. So I think then it kind of often would add. Too much. 00:52:54.000 --> 00:52:58.000 Cool much. 00:52:58.000 --> 00:53:07.000 Too much to that. User interface. When if it's not really used so much. 00:53:07.000 --> 00:53:14.000 And also another thing is that. 00:53:14.000 --> 00:53:23.000 With those response codes It's a bit confusing, but it kind of, if you need to check, so like that, if you need to check. 00:53:23.000 --> 00:53:34.000 Response code 200. 00:53:34.000 --> 00:53:45.000 And so I think. If nothing, if nothing is checked. And he chose on all pages. 00:53:45.000 --> 00:53:55.000 200 404 then it would change the current behavior So it would need those defaults. 00:53:55.000 --> 00:54:07.000 Also from that way is a bit. Difficult. So I think adding it to those pages was my favorite option. 00:54:07.000 --> 00:54:08.000 Okay. 00:54:08.000 --> 00:54:11.000 So that's what I'm suggesting. 00:54:11.000 --> 00:54:14.000 Over here, right? 00:54:14.000 --> 00:54:15.000 Yeah. 00:54:15.000 --> 00:54:18.000 Okay, Ralph, you wanted to suggest something? 00:54:18.000 --> 00:54:34.000 Just want to bring up one detail we've discussed in one related issue. That was about the. 00:54:34.000 --> 00:54:41.000 Where we agreed or where the consensus was did the pattern with show for the listed pages and hide for a list of pages. 00:54:41.000 --> 00:54:49.000 That is a good one. But also we've agreed on to move that show and hide. Radio buttons. 00:54:49.000 --> 00:55:01.000 From underneath. To the top. Meaning that the decision show or hide and the criteria after that. 00:55:01.000 --> 00:55:06.000 In the pages. 00:55:06.000 --> 00:55:31.000 We've brought up that one in the context. This on other tabs, there is the checkbox with negate the condition. 00:55:31.000 --> 00:55:32.000 Yeah. 00:55:32.000 --> 00:55:38.000 Trying to You use the browser tools to illustrate what you have in mind, but maybe that's. 00:55:38.000 --> 00:55:57.000 More than I need to do. So yeah, that's sort of related. That you do like this pattern of having the explicit checkbox or radio buttons to either show or hide. 00:55:57.000 --> 00:55:58.000 Yep. 00:55:58.000 --> 00:56:03.000 And we were talking about putting that at the top, at the bottom. Other existing ones don't have that pattern and we. 00:56:03.000 --> 00:56:11.000 Or they have the checkbox within the gate. 00:56:11.000 --> 00:56:12.000 Right. 00:56:12.000 --> 00:56:16.000 Yeah, that's. 00:56:16.000 --> 00:56:22.000 Yeah, so that's not in scope for the issue we're talking about, but it is something. 00:56:22.000 --> 00:56:32.000 Do we know if there's an issue? For being more consistent there. 00:56:32.000 --> 00:56:38.000 I don't think so. I don't think so. There is one. 00:56:38.000 --> 00:56:39.000 But 00:56:39.000 --> 00:56:54.000 And as far as I No, each of those tabs are in separate, is it plugins? And making that consistent someone brought up the worry that it's a bit complicated. 00:56:54.000 --> 00:57:01.000 To accomplish that. 00:57:01.000 --> 00:57:02.000 Yeah. 00:57:02.000 --> 00:57:15.000 Oh. That's not our problem. We are the usability team. We are not the implementation team. 00:57:15.000 --> 00:57:22.000 Yeah, so if we are going to be adding a new condition, we should follow the preferred pattern, which is. 00:57:22.000 --> 00:57:35.000 To use explicit radio buttons. 00:57:35.000 --> 00:57:36.000 Okay. 00:57:36.000 --> 00:57:45.000 And and this could be done in a trip module. Doesn't have to be in core. It's not clear that it's. 00:57:45.000 --> 00:57:56.000 Something that enough people need. That it's worth putting into core. And then if we could implement it as part of the existing. 00:57:56.000 --> 00:58:06.000 Condition plugin. That would be a good user interface. It might not make sense from an implementation point of view. 00:58:06.000 --> 00:58:21.000 But I think that would be really great for, from the user interface point of view. 00:58:21.000 --> 00:58:25.000 But one question is the 00:58:25.000 --> 00:58:32.000 200. Response code a requirement. 00:58:32.000 --> 00:58:37.000 For that issue. To be brought in. 00:58:37.000 --> 00:58:40.000 I'm not sure what you're asking. 00:58:40.000 --> 00:58:44.000 Cause the issue. 00:58:44.000 --> 00:58:54.000 Allow blocks to be configured, to show or hide on 204 or 3 and 404. 00:58:54.000 --> 00:58:59.000 They are adding a 200 also. 00:58:59.000 --> 00:59:10.000 Yeah, but that would be just, on pages. Kind of it all. Or others or all existing. 00:59:10.000 --> 00:59:37.000 Would would cover I think 200. 00:59:37.000 --> 00:59:50.000 Nobody probably wanted but it would be possible also to have a 301 response because I think that shows when if you are redirected you can get. 00:59:50.000 --> 00:59:56.000 3 or one and then you get the page. 00:59:56.000 --> 01:00:02.000 The, yeah, but then. 01:00:02.000 --> 01:00:03.000 So. 01:00:03.000 --> 01:00:11.000 And the page you get redirected to is the one producing the response. 01:00:11.000 --> 01:00:41.000 Yeah, I think I checked so. Checked something actually today related to some redirection issues on one side and I think, 4, like, doing Oh, request so those some of the stages I think it showed that 301 in the response with the page content. 01:00:41.000 --> 01:00:45.000 For instance, 01:00:45.000 --> 01:00:49.000 I put in an eye here. 01:00:49.000 --> 01:01:05.000 I slash issue number. That. Should give me a redirect back to the page I was just on. 01:01:05.000 --> 01:01:13.000 Okay. 01:01:13.000 --> 01:01:17.000 3 or 4. 01:01:17.000 --> 01:01:23.000 I got a 302 redirect. Huh, it's funny, why didn't? 01:01:23.000 --> 01:01:32.000 Let me try that again. I'm a little confused here. Oh, here that off. 01:01:32.000 --> 01:01:38.000 . I will 01:01:38.000 --> 01:01:40.000 I, enter. 01:01:40.000 --> 01:01:52.000 Maybe just different each. Maybe you's different issue, number because those get cast quite strongly. 01:01:52.000 --> 01:01:58.000 Oh wait, it's still loading. There we go. Maybe I just wasn't patient enough. 01:01:58.000 --> 01:02:05.000 So yes, I got. 302 response. 01:02:05.000 --> 01:02:19.000 And I got redirected from the. I slash pattern, the short version, I got redirected to the full project triple issues slash issue number. 01:02:19.000 --> 01:02:32.000 And then that page gave me a 200 response. So Yeah, the 302 response, the redirect sort of isn't getting me any. 01:02:32.000 --> 01:02:41.000 HTML it's not showing me any blocks it's not showing me anything it's just giving me some HTTP headers. 01:02:41.000 --> 01:02:57.000 And then it's page that I end up on. That gives it 200 response. It doesn't know that there was a redirection involved. 01:02:57.000 --> 01:03:16.000 So when we get to a valid page, we don't know that we got there by way of a redirect. 01:03:16.000 --> 01:03:20.000 So I guess. 01:03:20.000 --> 01:03:25.000 Based on our. Our discussion in March, I think. Where we came down was that. 01:03:25.000 --> 01:03:42.000 This could be a can trip module. It's probably not needed enough to be worth adding to And that's debatable. 01:03:42.000 --> 01:03:52.000 It's not a final decision, but. But I would suggest making it a and the alternative of. 01:03:52.000 --> 01:04:07.000 Addings. Special patterns to the pages plugin. Would be probably a better user interface. 01:04:07.000 --> 01:04:22.000 We just have a couple of minutes left. Any. Further comments on this issue. 01:04:22.000 --> 01:04:28.000 Okay. 01:04:28.000 --> 01:04:38.000 So we should definitely get, a and then we can close out that. Usability issue for March. 01:04:38.000 --> 01:04:39.000 What's that? 01:04:39.000 --> 01:04:52.000 Just Just one question. I'm still interacting with the 200 for the trust in the example you have here. 01:04:52.000 --> 01:05:00.000 And the 200 is available What does imply show for the list of pages if you have 4 or 4? 01:05:00.000 --> 01:05:12.000 4 or 3 in front for example selected. And the 200 available. So is it then? Only on front for 4 and 4 3 shown. 01:05:12.000 --> 01:05:15.000 Or 01:05:15.000 --> 01:05:23.000 So if I have exactly this. Then the block would show up on the homepage, show up. 01:05:23.000 --> 01:05:33.000 On the page not found page and which show up on an access to night page. 01:05:33.000 --> 01:05:39.000 Okay. 01:05:39.000 --> 01:05:40.000 So. 01:05:40.000 --> 01:05:56.000 So in in all case, you would need to have add wildcard like just. Us to have it in all. 01:05:56.000 --> 01:05:57.000 Yeah. 01:05:57.000 --> 01:06:03.000 So probably the only time you would use 200 is If you're hiding it, so only show it on 4, 3, 4 responses. 01:06:03.000 --> 01:06:10.000 And but that's the point that is I'm struggling with having the 200 available as an option. 01:06:10.000 --> 01:06:16.000 And having the show and the hide option and that way. That is always a head spinner for me. 01:06:16.000 --> 01:06:21.000 And makes me think. 01:06:21.000 --> 01:06:22.000 Okay, well I. 01:06:22.000 --> 01:06:35.000 Having the dedicated Arab message and pages that's okay. But the 200. In the context of show and tide is confusing. 01:06:35.000 --> 01:06:42.000 Okay, and maybe we don't need it. But I think we have to cut it off there because we have to reach the end of the hour. 01:06:42.000 --> 01:06:43.000 Yeah. 01:06:43.000 --> 01:06:49.000 I will be a triple con next week Monday through Thursday, but, I should be home. 01:06:49.000 --> 01:06:58.000 In time for the Friday meeting. So I hope you can make it again then. Good. Have a good week and a good weekend. 01:06:58.000 --> 01:06:59.000 And try 01:06:59.000 --> 01:07:00.000 Yes, good news. I'll meet you there Benji. 01:07:00.000 --> 01:07:03.000 Oh good. 01:07:03.000 --> 01:07:06.000 Alright, thank you. 01:07:06.000 --> 01:07:11.000 Have a nice weekend. 01:07:11.000 --> 01:07:12.000 Bye. 01:07:12.000 --> 01:07:15.000 Yeah.