New look for CArehart.org, especially better for the blog on mobile
Until this weekend...and it may not be noticeable to all, but I suspect some things will stand out to regular readers, starting with....
Blog much improved on mobile!
Until this weekend...and it may not be noticeable to all, but I suspect some things will stand out to regular readers, starting with....
I also noticed that it marks my 17th year of blogging here, almost to the day with my first entry posted this same week back then, Apr 15 2006. That's "pretty darn interesting", as Ray Camden might say.
FWIW, I'd also blogged elsewhere--yes, on CF--prior to starting this one. And the first of those posts were in early 1998--so technically it's my 25th anniversary of blogging about CF. :-)
[Edit] This post originally had been addressed to speakers at last week's great Adobe CF Summit. Adobe had been unable to arrange streaming or recording of the dozens of presentations. But it turns out that at the same time I was writing it, Adobe was posting that they will be asking Summit presenters to present on webinars they will arrange. As such, I withdraw here my request to host those presentations, as I certainly don't mean to lead to any confusion over things.
Still, I will leave up this post as a general offering to ANY presenters, on of course ANY CF topics. :-) Read on for more.
My session will be at 9a 930a Eastern on Monday July 18:
And I wanted to offer some additional thoughts--first planning to offer them as a comment--because there's a lot behind the question and his observations. But as it got longer, I realized it was too long for a comment. Also, I didn't want people to think (in reading a comment on Ben's blog) that I was challenging Ben or questioning his understanding of the matter! Not at all. :-) Instead, I was just wanting to add more context, to help other readers, and based on my years of observing the community.
What I offer here is pretty much exactly what I wrote, but I have added headings, to help readers here:
Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.Updated in July 2024, to present the three most effective solutions at the top of the post
Do you have a modern Asus laptop with the NumberPad (orNumPad) feature (a virtual numeric keypad embedded within the touchpad)? You may know there's a button to enable/disable it on demand, but do you find find it coming on when you brush that by mistake? Are you annoyed by that behavior, and all the more that you can't find how to "permanently" disable it?
In this post, I discuss ways to try to permanently disable it. (Indeed, I discuss many ways I have found or that have been shared here as the post evolved over the years.)
Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.Come learn what's new about FusionReactor 8.3 in the first of what are planned to be a series of Youtube Live webinars from the folks behind FusionReactor. In this first episode, FR Technical Support Engineer Michael (Mikey) Flewitt and I will be teaming up to introduce FusionReactor 8.3.0, which should be released very soon.
Join us on Feb 3 at 2p US EST (and set a reminder/subscribe) here: https://www.youtube.com/watch?v=f0TKfnhIE24
Besides discussing and demonstrating what's new in the 8.3.0 release (which includes several features), we will of course be open to your questions. That's the whole point of going to the Youtube Live format!
And again, this is the first of what are planned to be a series, with future episodes addressing not only FR feature changes but reviewing FR features you might have missed, and as important: how to use FR to solve important problems in CF, Lucee, and Java servers. We're also open to addressing broader issues related to such technologies, in an "ask me anything" format.
So come along, and do subscribe, and bring your questions and comments. We're trying to make it a resource that will benefit many. Of course, it's our first, so we will iron out the kinks as we go!
Note: This blog post is from 2017. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.I happened to try to visit today an Adobe forums page, when I got this error:
If this happens to you, I have a possible quick solution (if you just want to get to the page in question):
Use your browser's menu option to have it create a "new private window" (FireFox), or "new incognito Window" (Chrome), or "new session" (IE), or the like.
This will open a new window for your browser, and it will NOT send any cookies to the page in question. And you should find that suddenly the forums "work", which tells you that the problem was about the server's unhappiness with something about the cookies in your browser.
If that's enough, great. If you want to know a bit more, read on.
Note: This blog post is from 2017. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.Have you ever had a web site "go dark" on you? or found that a given page on a site somehow disappeared? Maybe it's only temporary (there may even be a "we're down" message, though the site or server may just fail to respond at all), or maybe the failure of the page or site will be permanent.
The good news is that there are at least two easy ways that you may well still be able to see that content you may be missing:
TLDR;
Try putting either cache: or web.archive.org/ in front of the URL of whatever page you're trying to visit, as in:http://web.archive.org/https://www.carehart.org/index.cfm
to perhaps see years of archived versions of a page/site.
Or to see any Google snapshot of the most recent cached version of a page, use this in a Google search,
cache:https://www.carehart.org/index.cfm
Either may or may not work, for various reasons I explain below. And note that this works for domain names or individual web page URLs. You may find that it also works with or without the protocol (http:// or https://), but try using it the other way if one does not work.
For much more, read on, as I share tips (and gotchas) on using both tools.
Note: This blog post is from 2014. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.If you're a user of proXPN (a free/low-cost VPN service), and you get the error, "Connecting to proXPN has failed", here is a simple solution that you may not find offered elsewhere: just try restarting proXPN. For more information, read on.