M6NEN

Hi Yordan, I think I did find a solution, and as far as I am aware it was most probably due to bootstrp and/or jQuery needing an update. I did update both and the problem seemed to have gone. That is the thing, of course, when your website is up and running and you don't need to add anything for a while. Although, sometimes, with widgets that websites offer you, you have to be a bit careful too sometimes they don't update their code for ages andnit gets obsolete, mainly due to Javascript and/or jQuery getting more modern et al. Anyway, I'm glad I've got it working now. Thank you for stepping in anyway.

Yes, Hello, Yordan. I was intending to do the same, but I have been so extremely busy lately that it completely slipped my mind. ? A bit late (but where I come from they say New Year lasts the whole month, so....). So, I hereby wish Yordan and everyone else involved here a very happy and prosperous 2020. (I certainly hope to have a better one than I had last year). See you folks soon.

Hi everyone, I have a tricky one here. I have a widget I placed on a site, which, as usual, comprises a few lines of HTML and a line of Javascript. It is a widget through which people can send requests to a radio station, and then it shows whether your request went through, or failed (in case the requested song does not exist in the repertoire list of the radio), in which case it emails the request to the radio station. This is the HTML: <form class="cc_request_form" data-username="ckhnsbvf"> <div data-type="result"></div> Song artist: <input type="text" name="request[artist]" size="40" maxlength="127" /><br /> Song title: <input type="text" name="request[title]" size="40" maxlength="127" /><br /> Bestemd voor: <input type="text" name="request[dedication]" size="40" maxlength="127" /><br /> Your name: <input type="text" name="request[sender]" size="40" maxlength="127" /><br /> Uw e-mail adres: <input type="text" name="request[email]" size="40" maxlength="127" /><br /> <input type="button" value="Verstuur aanvraag" data-type="submit" /><br /> </form> And this is the Javascript: <script language="javascript" type="text/javascript" src="http://solid33.streamupsolutions.com:2199/system/request.js"></script> As usual, the Javascript is supposed to be inserted just before the </body> tag. So far, so good, now for the issues: to begin with, I had to change the "http:" in the Javascript to "https:", or nothing would work. Then, the widget started working intermittently, and now, it does not seem to do anything, except when you send a failed request, it shows your request went through sucessfully. There is one more suspicion I have: the site in question uses Bootstrap (CDN version), would it be possible the Javascript conflicts with JQuery or something? Before the </body> tag there is this reference to JQuery *which comes immediately after the Javascript for the widget): <script src="https://code.jquery.com/jquery-3.4.1.slim.min.js" integrity="sha384-J6qa4849blE2+poT4WnyKhv5vZF5SrPo0iEjwBvKU7imGFAV0wwj1yYfoRSJoZ+n" crossorigin="anonymous"></script> <script src="https://cdn.jsdelivr.net/npm/popper.js@1.16.0/dist/umd/popper.min.js" integrity="sha384-Q6E9RHvbIyZFJoft+2mJbHaEWldlvI9IOYy5n3zV9zzTtmI3UksdQRVvoxMfooAo" crossorigin="anonymous"></script> <script src="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js" integrity="sha384-wfSDF2E50Y2D1uUdj0O3uMBJnjuUD4Ih7YwaYd1iqfktj0Uod8GCExl3Og8ifwB6" crossorigin="anonymous"></script> I have also tried to put the widget Javascript after the above, no difference. Does any of this make any sense or has anyone come across this before? The widget can be seen working on https://www.vlaamseradio.tk/verzoek.html it is the form near the bottom. Any help will be very much appreciated.

OK, I have done it. No problem with the system having slowed down, it seems to have picked up a bit of speed even. However, I do not see any difference with the previous build, no new features or anything, but also, there have not been any crashes or nothing has been grinding to a halt. So, hopefully (touch wood) they have ironed out the bugs that were left in 1903 and given us a stable drop of juice now.

I see you have already downloae it, then. I have, advised by Britec's video. waited so far. However, I was (am) under the impression that all unnecessary features (or features you do not need) can be removed from Windows. I guess the best bit is to upgrade myself and check it out. And, do not forget to read the document from Microsoft telling people about the fixes and issues, it contains some useful information. I'll be in touch later. By the way, nice talking to you again, Yordan. Kind regards.

Hi folks, it is this time of year again. Microsoft is coming with another upgrade for Windows 10 again. This one is called Windows 10 version 1909. We all know new versions of Windows are usually buggy, as Microsoft cannot be bothered to test them thoroughly and always release them to soon, but this time I have found some further explanations and some good advice on whether or not to upgrade yet, and how to usually act in case of a new upgrade of Windows 10. See for yourself and have a look at this Youtube clip: I think it is very informative and shows you a few things about previews, checking for existing bugs, what to do and not to do and more. Take a look and see for yourselves. Have fun. ?

That is a new one for me too. The first I ever heard about this.

Hmmmmmm, again? I must admit I had missed that one. They will never learn in that company, will they? I am just wondering how much misery (and how long for) their next update will bring.

Oh dear, are Microsoft making themselves look interesting again? I must say, that is a new one to me, I hadn't come across that one yet. (Or at least not as far as I had noticed). Anyway, stil waiting for the bugs beginning to show.

OK, Fairly simple. I just used the well-known Windows Update feature. When I did, all went well with "Getting things ready" and partly "Downloading" but then I got one of the (in)famous 08x0..... errors, a few different ones. However, now it has worked, but I must admit, I don't see any huge differences really, although it seems to run smoothly, no major (or any other, for that matter) problems encountered (yet). I did read that they withheld it for a while because of a serious bug, though (see a previous post). Anyway, so far, so good, although I wonder if it was worth the effort.

Well, as far as I can see now (that is just my two cents, though), the 1903 seems to have been fixed now. However , I have tried to download and install it a few times today, and gues what? The update keeps failing. ? Anyway, I will be patient and take things as they come, we'll see what happens, won't we? Let's say Microsoft can be a bit "unpredictable".

OK, I see this is working now. I have been despeately trying to post this for quite some time, but the forum just wouldn't have it. I have been told the forum has been updated now, and it seems to have worked. Thanks, Opaque.

In another topic here, we have been extensively talking about the Windows 10 1809. They are soon expecting version 1903, which is supposed to be "the best and most stable version ever". However, on Tuesday (today), a patch came out (not the new version, just a patch), which, again, can cause you a lot of headache and misery. I posted this just to warn you and to give you a way to solve the problem should you download (or have downloaded) the patch. If you run into problems, just check out this video and have a life without worries again. Hope I have helped people with this. To the others: Please wait with downloading this patch for now. There is further information about this in the video too. https://www.youtube.com/watch?v=I-qBqegyzvY

Yes, too right, Yordan. However, watch the topic I will be posting next, just a warning to everyone.

Well, I don't use all that doodoo ? neither. But I am just curious what will happen when we get the new major update. I guess it will be a laugh a minute again.