 Hello, everybody. It is maybe just me right now. Nope, it looks like the others are joining. So this is going to be our Q&A session for the next 15 minutes. So if you have any questions about what we've talked about today, which I believe was just talking a little bit about the philosophy behind Domain and Spoonzone, how the systems work together, the three systems individually and sort of experiences as admins, please feel free to toss them in this court chat, because that's what this whole time is for you. Whatever we haven't covered that you wish we had. I liked, I mean, while we're waiting for, I know there's a little bit of delay. So I liked Audrey's question around just resources beyond. And I really loved hearing and Annika referred to watching YouTube videos. I use the cPanel, basically their official documentation, WordPress beginner. That's one of the things about just myself, my own education with Domain, which putting together resources, writing blog posts, making links to these are my cheat sheets. Here are the codes I'll use, or here's the sites I found. It is unbelievably valuable. It's been fun to work with the support team so closely in the last couple of months. Because when we get questions that come into our support queue, we're Googling. We are looking at those resources. And I work regularly with the support team to say, okay, if you've got a personal cheat sheet or a handy list that you're referencing, make that available so other people can see it, even if it's for the internal team. Or is there anything here that we can put into a public resource for folks, something that we're referencing? But yeah, it's always interesting, that relationship. For sure. So one question I wanted to mention that I have written down, that's not earlier in the day was, there might be a good time to do it right now, is talking about transferring cPanels, cPanels between users. And I think that's a not too difficult one to do, but it's a good thing to know is possible. Yeah. Do you want to demonstrate that, Taylor? Sure. It's actually pretty, luckily, it's pretty straightforward in WHM, CS. Yeah, yeah. So basically, one of the three tools we showed you today, now it's in practice. Yeah, I'm, right now, I'm just getting logged into things here. Take your time because while you were doing that, one of the things I wanted to say was, you know, when we're talking about, you know, resources, one of the things, it took me a while, it should have took me longer than it probably should have, is copying an error code. When you see the error, the first instinct is always like, freak out, right? But once you like, have seen it a million times, like I should have, I finally was like, wait, maybe I should copy it and search it. And then you'll find yourself on Stack Exchange or something like that with someone like, oh, it's a bad plugin, deactivate the plugin. Are you talking about like the HTTP 500 errors? Like, or any of those, right? Like, if you're looking for guides, one of the things is copy and search the error message you're getting. Nine times out of 10, if it's WordPress, it's a plugin, a theme that went wrong, or an update that caused it. Like, some of those seem scarier when you see the error, and we'll talk about this later today. But in fact, you know, a lot of that stuff, if you do the search and you walk backwards from it, you can actually figure out a fair amount of it, you know, which, which is kind of empowering as a domain's admin, because that's part of your superpower to keep it all going is to say, oh, there's an error, I can help you with that. And then you feel great and they feel great. You know, everyone's happy. One of the, my particular few gripes with WordPress is that they have a particular error message that's basically something has gone horribly wrong by, that's it. And it, that's one of the ones in particular. It's have to actually go in and enable error messaging. Otherwise, it's just breaks. Yeah, it's error messaging. It puts them on the web page. So you can't leave it either. Right. It's just dumping them to the page instead of a log file, which is barbaric, I think. That's one of the ones we're deactivating, the plugin or theme is often, you check the error log in file manager, it's right there, and you just say, all right, well, turn that off and then the error goes away. Yeah. Yeah. And that's something that in common troubleshooting tips section, I will kind of show that a little bit of what that looks like. We've also got documentation for that linked in that session as well. So that'll be really good. But all right, I have my windows in order here for showing, moving the basically WHMCS, if you want to, if you want to take a C panel and give it to somebody else, you can just use the move product or service function in WHMCS to do that. And here I'm using S&C's domain of one zone as an example. There's this account owned by an individual Taylor Jaden. Suspect. Yeah. And I actually got an email from, I'm assuming Annika set it up, of that this account is going away. So, but maybe they need to move it before then, right? So you would go into WHMCS, you'd log in, and you could move the product or service out to a different user. So that it's important to note that this, in this case, you need to have the other person needs to have logged in to domain of one zone. So that they're, that they exist as a client in WHMCS. But once that's happened, they don't, they don't even have to have any products or C panels yet. You can just go to the one you want to move, use move product or service and it'll open up a window. And then you can either search for them. We can't see that window. I can see it. Just there it is. Yeah. You'll either search for them using the search box here, or if you know their client ID, because maybe you have it open on another tab, you can just put that in there and transfer. And it's, so it's, it's pretty straightforward if you just need to move it to a new person. I will also mention that there's a document called C panel management that talks about some like similar things, but not exactly the same things, but these are all kind of adjacent, I feel like situations where you've got one C panel managed by multiple people, or you want to do multiple C panels managed by one person, right? The opposite of that. So that's, that's a good document in there too. I'm not going to demo that, but I would know about. Yeah, that's a great point because C panel doesn't natively allow you to have multiple admins. And so we have a couple of workarounds that we can use, you know, with in, in working with WHMCS, we're able to do that. So it looks like Taylor just listed the doc there, but that's a great. It is. And I'll take another point on that. I'm sorry, am I interrupting you, pilot? I was going to say very quickly, while you're still in WHMCS, if you could, Corinne asked earlier, I believe about changing packages for users after the fact, which is something that you can do in WHMCS. And we recommend, I don't know if SNC actually has multiple packages, but we can show you where you would go to do that. Yeah. Yeah. Hold on, I'll throw my screen back up. All right. And so I think that would just be, correct me if I'm wrong, going to write at the top its order and then product service. Oh, change package, change package, change package. And keep in mind, WHMCS, we talked about this earlier, you know, depending on the version you have, things may not be exactly where you're seeing these here. This is a bit older version. So there may be some search and, you know, access there. But WHMCS also has documentation with a lot of that stuff documented. But yeah, you would change it right there. I will mention that SNC does not have multiple packages. And one valid thing that I would add to the last session is I should have done multiple packages. We didn't have a lot of people needing more storage. I could probably count on one hand the amount of people I ever had to increase it for. But still, it's good to do that right from the start. And I will say with new domain setups, that is something that we encourage earlier on now in that onboarding process with new domain schools. And I think it's taken us a couple of years to realize how helpful those can be. And if you can set those policies and be thinking about how you want to architect each of those C panels before you have a lot of users, you know, you just have those policies from ground one, you know, ground zero, as opposed to saying like, okay, we have two, three years of domains under our belt, we have all of these outliers. How are we going to kind of bring them in? Yeah, yeah. I'm sorry, go ahead. I was just going to say that I think it can be difficult sometimes to when you're starting out, it might feel a little bit overwhelming to say, oh, well, how do we account for multiple use cases? And I think that that's a really good point to reach out to other institutions. And that's something that I wish I'd done, because when I started at Carleton, part of what we were trying to figure out is how do we account for different use cases even among faculty. So we have the studio art faculty, we have the history we have the history department, just talking to other schools and to reclaim who can maybe help you get in contact with those other schools about what use cases they find to be common and what the purpose of domains at their school and how those two things connect. I do think that Annika really did a nice job of saying, sometimes it's a bit manual work, but you can go through the sites and see what people are doing and spend a little of that time and it gives you insight that maybe it's not going to just be immediately apparent from what is essentially a black box or cPanel, sometimes whether it's going to install trauma with all the installed apps or going through sites, you get a better insight. And it is time and not time we always have, but I do think her pointing to its value for her to get a sense of what's going on around SNC and Knight's Domains was worth it. I used to do a lot of the same thing with UNW domains, like I would labor over it, I would look at everything and then I would write about how great it was. It was a simple process of read and promote, read and promote to get a sense of what's happening and get people excited about it. One thing that I've been working on since I was an admin at SNC and I picked up a little bit more recently again that I'll talk more about tomorrow in the site archiving section is using just screenshots to get a good overview of what's happening. So I'll share it tomorrow, but I have a script that you can basically just give URLs and it will just go get screenshots and doing that for Domain in One Zone and hoping one of the things I want to do is package that up in a way that any admin can use it pretty easily. Basically, you just put URLs on a text file and it gives you a folder of screenshots and I did that at SNC a couple times and it was amazing just downloading that folder and looking at it on my Mac in the thumbnail view and just being like, whoa, I've never even seen that. You'd be surprised just on a visual overview what kind of cool stuff you can find out. So that's a tool that I'll talk about tomorrow that anyone can use if they have some expertise at the command line, but I'm hoping to make a little bit more accessible soon. And I think tomorrow we're going to wrap up here, but I think tomorrow one of the other things we'll talk about is aspirational uses and very kind of practical uses of domains for establishing some of that stuff with Tom Woodward and Taylor, which I think does return to a lot of these topics of actually bringing that back in. I'm sorry. We have a question in the chat from Ed around PHP and removing old PHP versions. I think this will go a little bit into break, but that's fine by me. Ed says 7.2 is still installed on his system, which is out of support and security. So I'm assuming this would be Yeah, I was actually talking about PHP versions with infrastructure team this past week and it is on our roadmap to address that by end of year. So we are tracking on that. Our team is actually going to meet as a full, you know, all hands meeting. We've got one scheduled for June just to talk about end of year goals and timelines for those sorts of things. So I don't have official timelines for you now, but we should be pushing that out by the June or July email. Yeah, what you should know too is that the way PHP works in a situation like this is unless you specifically tell it to use an old version of PHP, there are multiple versions installed and it's going to inherent by default, the default version on the server, which we should have set to a newer version than that. 7.4 is what we're doing. We'll make two changes. We'll be getting rid of 7.2 at some point and then the inherited version will be increased. And we're also going to be making sure that the latest version is available because I think there's a newer version out that we want to make sure is. 8.0 is out right now. I'm not sure if we'll be moving to that as the default. Any time you move the defaults, it will break some old sites. It just will and you can always go back in and say, nope, this one needs an older version. But it's just a reality of moving PHP versions. I think 8.0 is on some servers of ours already. Ed mentioned 8.1 is out and that I don't think we have out anywhere on our servers yet. We don't, we do. So at this point it probably would be good to close this session, take a five minute break and we will see you back for the next session here soon. Common troubleshooting tips just as Taylor was talking about earlier. Awesome. See you all. See you all soon.