00:00:26.827 --> 00:00:30.449 I've already been through this and and I hoped you find the
00:00:30.449 --> 00:00:34.071 right version. You'll be fine, but I would like everyone to
00:00:34.071 --> 00:00:34.977 confirm anyway.
00:00:37.127 --> 00:00:40.698 It seems like we have a variety of different ways people are
00:00:40.698 --> 00:00:43.567 installing and or using the installer right now.
00:00:44.727 --> 00:00:47.467 And I wanted to make sure that we're all using.
00:00:48.247 --> 00:00:51.127 The version that comes from the download link that I'm about to
00:00:51.127 --> 00:00:53.737 send in the chat because the download link version that I
00:00:53.737 --> 00:00:54.457 will be sending.
00:00:55.947 --> 00:00:58.975 Contains logic that automatically updates the
00:00:58.975 --> 00:01:03.320 installer, and I could and I can push out updates for you guys so
00:01:03.320 --> 00:01:07.533 that as we add support for new stuff versions or we fix bugs or
00:01:07.533 --> 00:01:08.257 we add new.
00:01:09.337 --> 00:01:12.490 You know better logging or whatever it is you guys will
00:01:12.490 --> 00:01:15.925 automatically get that and you don't have to compile it from
00:01:15.925 --> 00:01:19.135 source or pull latest or anything like that. It's it. In
00:01:19.135 --> 00:01:20.317 theory it just works.
00:01:21.857 --> 00:01:24.707 As my good buddy Todd Howard likes to say.
00:01:28.997 --> 00:01:33.970 So I'm going to put that link in the chat real quick if you are
00:01:33.970 --> 00:01:36.767 not sure what version you're using.
00:01:37.877 --> 00:01:40.207 I will tell you how it's like.
00:01:43.397 --> 00:01:44.807 And we'll tell you how to find out.
00:01:48.197 --> 00:01:51.925 So what you need to do to find out and I will share my screen
00:01:51.925 --> 00:01:52.827 and everything.
00:01:56.577 --> 00:01:58.847 Where is my screen? There it is.
00:02:01.177 --> 00:02:03.647 Well, you need to do open your.
00:02:04.657 --> 00:02:08.378 Your salt. If you open the install. Hey, look at that and
00:02:08.378 --> 00:02:08.827 update.
00:02:12.157 --> 00:02:15.799 Yeah, that's what it looks like when it automatically updates.
00:02:15.799 --> 00:02:19.037 That's cool. I didn't plan for that. But you know what?
00:02:19.967 --> 00:02:23.685 I'm glad that happened. UM, if you open the installer and it
00:02:23.685 --> 00:02:27.525 doesn't open this window, you are on the wrong version. You're
00:02:27.525 --> 00:02:31.547 on an old version and we need to get you updated so the installer
00:02:31.547 --> 00:02:35.082 the correct version of the installer is bundled with this
00:02:35.082 --> 00:02:35.387 tool.
00:02:36.027 --> 00:02:38.757 This tool needs to be what opens when you open.
00:02:39.537 --> 00:02:44.157 The CLT, or the installer uh EXE is this tool. Whoops, he's going
00:02:44.157 --> 00:02:45.207 to click there.
00:02:46.887 --> 00:02:49.274 If that's not happening, you're using the wrong version of the
00:02:49.274 --> 00:02:51.320 installer and you should download the correct version
00:02:51.320 --> 00:02:52.797 from the link. I just sit in the chat.
00:02:54.667 --> 00:02:57.167 Is everybody, is everybody with me so far?
00:02:58.287 --> 00:03:01.320 Just make sure can I get everybody who is presently here
00:03:01.320 --> 00:03:04.087 to raise their hands so I can make sure people are.
00:03:05.147 --> 00:03:07.517 Following along checking their things.
00:03:09.677 --> 00:03:11.047 Place version is.
00:03:11.817 --> 00:03:13.517 1.7 dot two that correct.
00:03:13.317 --> 00:03:15.807 Yes, correct. Uh, the the.
00:03:14.347 --> 00:03:14.717 OK.
00:03:16.337 --> 00:03:18.657 Uh patch notes are updated but.
00:03:20.397 --> 00:03:23.457 Yes, the the correct newest version is 1.7 point 2 so.
00:03:24.577 --> 00:03:28.717 If everybody can just confirm that they.
00:03:29.917 --> 00:03:33.100 I have checked that so it looks I think the only person that
00:03:33.100 --> 00:03:36.231 hasn't raised their hand that would need to would be. Greg,
00:03:36.231 --> 00:03:39.570 are you still? Are you here or are you checking if you have the
00:03:39.570 --> 00:03:40.457 right version or?
00:03:40.287 --> 00:03:42.607 Ohh apologies. No I I haven't.
00:03:42.957 --> 00:03:46.145 OK, cool. Cool. Umm, alright, so the next thing to do real quick
00:03:46.145 --> 00:03:47.567 is if this version does open.
00:03:49.207 --> 00:03:52.853 You can click installer and in the footer down here you'll see
00:03:52.853 --> 00:03:56.556 the version number. So in this case, like Greg said, the latest
00:03:56.556 --> 00:03:57.887 version is 1.7 point 2.
00:03:59.227 --> 00:04:02.374 If you're on a version older than that and it didn't prompt
00:04:02.374 --> 00:04:05.206 you to automatically update, you're probably directly
00:04:05.206 --> 00:04:06.727 compiling from the source or.
00:04:07.727 --> 00:04:10.459 Or you're. Yeah, you have an older version somehow that
00:04:10.459 --> 00:04:13.434 doesn't have the auto update logic. If the version number is
00:04:13.434 --> 00:04:16.507 missing, you're on a, you're on a significantly older version.
00:04:17.367 --> 00:04:20.470 Umm. And that'll mean that you're also not receiving the
00:04:20.470 --> 00:04:21.667 automatic updates, so.
00:04:23.107 --> 00:04:26.362 There's a handful of things that we're gonna be rolling out with
00:04:26.362 --> 00:04:28.716 this tool soon to start capturing common error
00:04:28.716 --> 00:04:31.921 information and whatnot so that we can start to really solidify
00:04:31.921 --> 00:04:35.026 this thing. I know for a lot of people it kind of get to it's
00:04:35.026 --> 00:04:37.880 still faster than doing the whole thing manually, but it
00:04:37.880 --> 00:04:41.085 doesn't finish the job. It gets you about 75% of the way there.
00:04:41.085 --> 00:04:44.290 That's the thing we're hoping to fix with this, but it's really
00:04:44.290 --> 00:04:46.944 hard to fix that when we don't have a good idea that
00:04:46.944 --> 00:04:49.648 everybody's using the right version, that everybody's
00:04:49.648 --> 00:04:52.703 getting automatic updates. We don't know how much people are
00:04:52.703 --> 00:04:55.257 actually using it or what those common errors are.
00:04:55.537 --> 00:04:56.067 So.
00:04:57.007 --> 00:05:00.222 I'm hoping that sooner than later we're going to be able to
00:05:00.222 --> 00:05:01.937 get automatic error information.
00:05:03.657 --> 00:05:07.612 That you can obviously opt in or out of if you feel that you
00:05:07.612 --> 00:05:10.984 don't let that information shared for one reason or
00:05:10.984 --> 00:05:11.827 another. But.
00:05:17.407 --> 00:05:21.166 That should help us get this thing a lot closer to stable
00:05:21.166 --> 00:05:25.184 until that time. If you use the installer and it does not get
00:05:25.184 --> 00:05:27.387 you a fully functional CEF local.
00:05:28.087 --> 00:05:30.681 Please tell me what didn't work and what you had to do to fix
00:05:30.681 --> 00:05:30.807 it.
00:05:31.897 --> 00:05:34.765 And if possible, include the logs on the final step of the
00:05:34.765 --> 00:05:36.807 installer. There's an export logs button.
00:05:38.947 --> 00:05:42.808 If you run the installer and you don't have a function, a fully
00:05:42.808 --> 00:05:46.790 functional SEF local by the time it's done, export the logs, send
00:05:46.790 --> 00:05:50.652 them to me and include what it didn't do correctly that you had
00:05:50.652 --> 00:05:51.617 to fix manually.
00:05:53.367 --> 00:05:55.767 And I'm hoping that.
00:05:56.587 --> 00:05:59.768 Again, I'm soon we'll be able to automate that, but in the
00:05:59.768 --> 00:06:02.786 meantime I have. I have not been. I know that there are
00:06:02.786 --> 00:06:06.021 people that this doesn't fully work for and I'm not getting
00:06:06.021 --> 00:06:09.417 enough feedback on what those issues are, so I can't fix them.
00:06:09.717 --> 00:06:10.867 Umm, that's.
00:06:11.677 --> 00:06:15.273 Unfortunately, the classic it works on my local. I can get a
00:06:15.273 --> 00:06:18.868 fully functional stuff local when I run this on my computer,
00:06:18.868 --> 00:06:20.047 but the process for.
00:06:20.957 --> 00:06:23.746 Setting up a CEF locales so complex and involved, and
00:06:23.746 --> 00:06:26.949 there's so many variables and people's environments that it's
00:06:26.949 --> 00:06:30.306 very difficult to get it to, you know, just because it works for
00:06:30.306 --> 00:06:33.715 me or works for somebody doesn't mean it's guaranteed to work for
00:06:33.715 --> 00:06:36.711 everyone else. And that's the thing that we need to start
00:06:36.711 --> 00:06:38.467 narrowing down and resolving. So.
00:06:39.157 --> 00:06:41.607 Uh, any questions? Anybody have any?
00:06:42.417 --> 00:06:43.507 Thoughts on all that?
00:06:50.517 --> 00:06:54.930 Anyone brave enough to admit that it doesn't fully work on
00:06:54.930 --> 00:06:55.827 there local?
00:06:57.187 --> 00:06:59.777 Yeah, it doesn't work on mine, but Brendan already knows that.
00:07:00.027 --> 00:07:03.987 Yeah. Yeah, we had a he sent me a log for that one. Yeah. And it
00:07:03.987 --> 00:07:07.763 is perfectly fine if it doesn't. I I'm. I'm under no delusion
00:07:07.763 --> 00:07:08.677 that it's like.
00:07:09.597 --> 00:07:12.921 A perfectly flawless thing. I do hope that it's still makes your
00:07:12.921 --> 00:07:16.194 job easier. I hope that it still gets you most of the way there
00:07:16.194 --> 00:07:18.547 and it's still faster than doing it manually.
00:07:19.257 --> 00:07:22.285 Umm but yeah, by all means. If it doesn't work, don't feel like
00:07:22.285 --> 00:07:25.124 you're hurting my feelings by telling me. I I would love to
00:07:25.124 --> 00:07:27.537 know if it's not working because I need to fix it.
00:07:28.927 --> 00:07:32.046 By fully functioning local, there's still gonna be some
00:07:32.046 --> 00:07:35.332 steps afterwards, even if it runs 100% correctly, like the
00:07:35.332 --> 00:07:38.451 translations and skins in the database that you have to
00:07:38.451 --> 00:07:41.737 update. Still, that's not built into the installer, right?
00:07:42.147 --> 00:07:44.987 That is, or should be. If that's not working, that's a bug.
00:07:46.397 --> 00:07:50.627 For me, locally when I run this thing I get a completely fully
00:07:50.627 --> 00:07:54.387 functional local and the only things that might not be.
00:07:55.527 --> 00:07:56.917 Perfectly functional.
00:07:57.777 --> 00:08:02.717 Are I believe for the skins it may replace?
00:08:04.067 --> 00:08:07.977 The skin name in the database with the.
00:08:09.037 --> 00:08:10.427 Well, no, I wouldn't do that. Never mind.
00:08:11.337 --> 00:08:13.617 I have the logic, I have logic built to prevent that.
00:08:12.307 --> 00:08:15.691 Yeah, I think the only post installer step I had to do that
00:08:15.691 --> 00:08:19.074 I can at least remember is updating that skin path. I think
00:08:19.074 --> 00:08:22.457 I had to replace the clarity word clarity with whatever the
00:08:22.457 --> 00:08:25.277 client name was. Whatever the client acronym was.
00:08:23.757 --> 00:08:28.095 OK. And yeah, and I think that might have been because the skin
00:08:28.095 --> 00:08:29.247 didn't exist yet.
00:08:31.007 --> 00:08:34.401 Didn't you have to also copy the skin from the clarity one and
00:08:34.401 --> 00:08:36.987 then do that in the DNN database? Or was there?
00:08:38.127 --> 00:08:41.439 You might be right, but it's been a while since I set it up.
00:08:38.307 --> 00:08:41.657 I might be thinking of somebody else's. Yeah. OK. I can't
00:08:41.439 --> 00:08:43.937 I haven't installed a new version in a while.
00:08:41.657 --> 00:08:42.177 remember.
00:08:44.307 --> 00:08:46.957 Yeah. OK. Well, at any rate.
00:08:48.257 --> 00:08:52.972 Yeah. If it it, it should for me. If I do a like a standard
00:08:52.972 --> 00:08:54.387 setup on my local.
00:08:54.987 --> 00:08:58.647 Umm. Like no brands, no signal R or anything complex. I just do a
00:08:58.647 --> 00:09:02.140 normal stuff site, I get a fully functional site. Translations
00:09:02.140 --> 00:09:05.800 are good to go, DNN's good to go at the end of the site there's a
00:09:05.800 --> 00:09:09.183 button to visit the site and I can click on that and get and
00:09:09.183 --> 00:09:12.399 load up a working site. And again that's my local because
00:09:12.399 --> 00:09:15.948 that's where most of this code has been written. And so if it's
00:09:15.948 --> 00:09:17.057 not working for you.
00:09:17.677 --> 00:09:22.179 Umm, anything that isn't working out of outside of or inside of
00:09:22.179 --> 00:09:23.867 that standard SEF setup?
00:09:24.507 --> 00:09:25.417 That should be.
00:09:25.837 --> 00:09:27.407 Uh communicated.
00:09:28.327 --> 00:09:29.507 Uh, so we can fix it.
00:09:31.877 --> 00:09:33.879 And then Tim and Bradley, I don't know if you guys had your
00:09:33.879 --> 00:09:35.447 hands up from earlier. If you have a question.
00:09:37.517 --> 00:09:39.017 Ohh no offer has put my hand down, sorry.
00:09:39.417 --> 00:09:40.787 Same. Sorry about that.
00:09:39.577 --> 00:09:39.887 You get.
00:09:40.867 --> 00:09:44.390 No worries, alright. Any other questions? If not, we can move
00:09:44.390 --> 00:09:47.117 on to whatever else we're going to cover today.
00:09:53.687 --> 00:09:57.176 Alright, cool. Well next is schema changes and I didn't
00:09:57.176 --> 00:10:01.289 necessarily get a volunteer, but whoever wants to go over that so
00:10:01.289 --> 00:10:02.597 that we can get that.
00:10:03.357 --> 00:10:05.717 Recorded here and then get the documentation updated.
00:10:13.587 --> 00:10:14.057 Well.