carlosridg
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] Forever spinning wheel after clicking order button in checkoutThis error message suggests that there was a communication issue between the listener and the message channel. The problem arises from the internal promisification of the sendMessage function, allowing it to be awaited. However, if no callback is explicitly specified, one is added internally to ensure the call returns a Promise. Consequently, if sendResponse is not called within onMessage, the API assumes that you have made an error by not providing a response through a callback, and it reports it as such.
Since the new behaviour is very confusing for almost everyone, a solution might be to stop showing this error when the callback is not specified, however it might cause confusion for those developers who still use callbacks and forgot to call sendResponse inside onMessage by mistake, which should be reported ideally as it always was.
In some cases it may be related to the Adobe PDF extension, you can follow these steps to troubleshoot and resolve the issue. First, ensure that the Adobe PDF extension is properly installed and up to date. Check for any available updates and install them if necessary. Next, verify if there are any conflicts with other browser extensions or plugins. Temporarily disable other extensions and test if the issue persists. If the problem is resolved, re-enable the extensions one by one to identify the conflicting extension.
If still error showing, try disabled all installed extensions in Chrome then you will get a clear console without errors.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Google Maps not LoadingThis error is appeared because the WebView can’t recognize the URL Scheme,for example, the WebView will usually recognize only http and https, anything other than these. So WebView cannot parse it to right place, we should use intent to redirect the url. for example – intent://,market://,app://,mail:// etc will not be recognized by webview unless we add a handler to handle these url scheme or by disabling these schemes and only load http and https schemes.
This error has no any specific solution till now. Android user and PC user all are facing this error which needs to be sought out. There’s a long-standing bug in Chromium regarding how links without protocols are handled. It occasionally is patched, but seems to keep resurfacing. In some cases, prefixing your links with http:// (or https://) should resolve the issue for you.
Also, in some cases, try to add target=”_blank” in your URL Scheme/Code. for example:
<a href="mailto:my@email.com" target="_blank" rel="noopener">Link Text</a>- This reply was modified 5 years, 2 months ago by carlosridg.