With the last reCAPTCHA update, the function to hide mails ("Mailhide") seems to have vanished completely.
although you can still get keys and although, actually, using the old libraries (no longer available from the website...) everything works.
Do someone know something?
Thanks.
It seems like Google stopped reCAPTCHA Mailhide.
There was an alternative scr.im but the website disappeared.
I'm now using spamty which seems to work fine.
Related
I just made a brand new project with Nuxt using the npx create-nuxt-app command.
This error might not be related to Nuxt it self but its really annoying to have it in all my nuxt projects and I struggle to get rid of it. It appears in Firefox developer edition when I run the npm run dev command for localhost.
The connection to http://localhost:3000/__webpack_hmr/client was interrupted while the page was loading.
The connection to http://localhost:3000/_loading/sse was interrupted while the page was loading.
Any idea how to get rid of this ? thanks
Wow, never realized this error is always present in Firefox. Usually, this kind of thing just disappear when your refresh the page once but it looks like it is persisted in Firefox indeed.
I guess this have something to do with the way HMR websockets are done.
Here is a github issue talking about the problem and here is the most up to date mozilla bug report.
Not sure if the latter is anyhow relevant.
Maybe this is just a flag to set in Firefox or something related to Vue specifically. Nonetheless, you can filter-out some errors but putting -<your-query> in the console search. Works great to remove some annoying error that you don't really care about.
This is how it looks
For almost every page I open in Firefox, I see this error in the Console of the developer tool bar:
(!) The Components object is deprecated. It will soon be removed.
The source is the html page. It happens with pages I create, but also on many common websites.
I found this documentation on Components object on MDN web docs, but that does not clarify a lot. Note that even that page shows this message(!)
It looks like a warning, but according to the Console filter, it is an error.
My main questions are:
Is this something for me, as a developer of the page reporting this, to solve?
If so, how do I go about that?
I am not aware of any problems as a result of this. For now, that is.
I have seen this for over a year, maybe longer. I mostly ignore this, but every now and then it starts nagging me again. I don't want my code to break suddenly and would like to get rid of this message obscuring other messages.
This is not for the developer of the page to solve.
While biking back home, a possible cause popped up in my mind: could one of the add-ons I use cause this and yes, that appears to be the case.
I restarted with disabled add-ons and the message was gone.
Then I enabled them one at a time and the culprit is
Selenium IDE.
A bug report on this issue was closed with Won't fix, with the message:
This error will resolve itself when we move to a native app later this year.
In a MozillaZine topic of 2012, it is explained how it could have been solved.
The first one is just a warning that the addon is using "Components"
directly, which won't necessarily always be possible when using the
Add-on SDK. (The preferred way to do it is to access the aliases for
Components.classes and Components.interfaces and such that the SDK
provides by requiring the "chrome" module.) It shouldn't be a problem
right now, but might become one in the future.
it happened for me after installing Selenium plugin in my FireFox.
I'm getting a strange behavior and after hours trying to figure out what might be causing this issue, still can't solve or understand why is this happening.
The project, using Laravel Framework 5.6.39, suddenly is loading every page twice, like a redirect. This happens in all routes, even the ones not using the master page layouts.
Examples: I call myproject.develop/ or myproject.develop/login or myproject.develop/articles and it loads the correct views but twice. It feels like a redirect to the same page or a refresh.
Some of the things I've done and didn't result: clear cache, clear config, clear views, clear routes, disable debugbar, disable clockwork. The behavior is the same.
Thank in advance for any help in trying to solve this issue.
After Ross Wilson suggestion to disable Javascript in the browser (Chrome o Mac OS), first it didn't solve the issue.
Nevertheless all the steps taken as described in my question, and also cleaning any application settings in the Chrome developers console, it wasn't working.
Then, reverting Chrome settings and re-enable Javascript in Chrome, it "magically" worked and this weird behavior disappeared. Just guessing that this might be a Chrome bug (using Version 71.0.3578.98 (Official Build) (64-bit)) while I was thinking anything was wrong with the application—routes, controllers, scripts, etc.—and it wasn't.
So if anyone starts experiencing this issue of pages loading twice, follow the steps and you might probably get lucky and solve the issue.
Thanks Ross!
Icognito mode solved it... so after dumping a bunch of chrome extensions it finally stopped.
I deleted cache from Chrome and the problem is gone
Ok, none of the others thing worked for me. This can be kinda obvious, but is good to check if you dont have any "src=''" in your code, this seems to try to make a request to the same url with the src type header. that happened to me.
When I try to use Google Prettify to syntax highlight my code, I notice that it causes code to become one line ... why is that? When I remvoe prettify, it works
This is a well-known issue that someone's still trying to track down. Hang on, I've got the bug favourited somewhere...
Yeah, there we go, here's the link to the issue in the Google Code issue tracker, assuming you're using IE, or one of the other affected browser/versions.
Internet Explorer 9 was released today, and I decided to check a few Magento sites we build in the last couple of months to see if everything continues to work with the new version.
But unfortunately it doesn't. I came across one particular problem that is caused by the version of the prototype library which is shipped with Magento, version 1.6.0.3.
It looks like the cancelling events in eventhandlers isn't working.
For example, if you try to log in to a Magento shop, and just leave the login and password fields empty, IE9 submits the form even if there were errors, and the errors disappear after the refresh.
So that's quite a big problem I think.
So my question is: how can we deal with this problem? I see a couple of ways to deal with this:
Wait for Magento to release a new version with fixes
Upgrade the prototype library to the latest version which probably already has fixed the issue
Mess around in the existing library and try to fix the bug in there
Waiting for a new Magento release isn't a good idea because it probably will take a few weeks before there is one, and because it will cause a whole lot of other problems if you are running a very old version of Magento.
Upgrading to the latest prototype library is probably the best idea, but will everything in Magento continue to work with the latest version of prototype, does anybody has any experience with this?
So what's everybody's opinion about this problem?
Any ideas other than mine?
As upgrading Prototype has the potential to break a lot of things in Magento (and, honestly, doing anything in Magento has the potential to break a lot of things in Magento), I created a theme override for my
app/code/design/frontend/{package}/{theme}/template/page/html/head.phtml
file and slapped the following as the first element under the head tag:
<meta http-equiv="X-UA-Compatible" content="IE=8" />
This tells IE to pretend as if it is IE 8, where possible. This solved an issue where, for example, you could not check out and complete the payment process if you only have one payment method enabled, as in IE 9 the fields will all be grayed out.
Note that it really must be the first tag underneath the <head>.
Since upgrading Magento in any way has the potential to cause problems, I feel this is the least intrusive way to solve the issue in the near term.
Solved: http://www.alexanderinteractive.com/blog/2011/10/solving-the-ie-7-ie-9-magento-prototype-validation-bug/
I spent a couple days on this, and discovered the only thing that truly works is disabling things at the form level. This should solve all your problems.
As a quick fix, I think I would take the same approach you are advocating, and upgrade Prototype to a version that does not contain this issue. However, Magento will be coming along with a patch (this is too big to ignore), and at that point, it would be wise to undo your changes and apply the patch they provide to keep in line with normal upgrades.
It is rarely worth it to manually dig in the internals of Magento's JS, so that option seems a bit off to me. There are probably several places where this semantic is used and you may miss some of them.
Hope that helps!
Thanks,
Joseph Mastey
I've updated the prototype.js file to 1.7 and so far it's correct. I dont see any errors. If you apdate and find errors please notify!
The proper fix is in the Magento forums.
In template/catalog/product/view/tabs.phtml, change the line that reads:
ul.select('li', 'ol').each(function(el){
to
ul.select('li').each(function(el){