Recently I saw a nice extension of Typo3. It is called metatags but I can't find it in the repository. Can someone tell me the extension key?
With that extension it is possible to set keywords, description, robots, revisit, expires, cache-control, pragma and so on. Is it an old extension or a custom one?
Sometimes the repository search doesn't work (neither from backend nor on typo3.org), so maybe this is the reason you couldn't find it. The extension key is metatags an it's here: http://typo3.org/extensions/repository/view/metatags/current/
Related
I have 2 extensions which need to have a specific order on a sitecollection. I already tried setting the in ClientSideInstance.xml and also in Tenant Wide Extensions list.
Do you know other ways to order the rendering of the extensions?
Thank you!
Unfortunately not. There is a parameter in the manifiest.json file, that should allow you which extension should load before, however, it doesn't work.
Some solutions you may try:
One of the extension to leverage the DynamicDataProvider spfx resource, and make the other spfx extension to use the subscrided data.
One of the extension injects some code when it is loaded in the page, like addign an extra class to the body class, as extYYY-loaded. The other extension is monitoring the body attributes using a mutationObserver, and triggers in as soon as the atribute appears.
Today, I have found that something had changed registry values for Chrome policy in my laptop.
It is in 'ExtensionInstallWhitelist' which as the name suggests whitelists chrome extensions.
So, Now I have three extension ids, but don't know how they got there. I googled them and found that one of them belongs to an old malware. But remaining are getting no results.
Is there any way to search for extensions using their ids, or does extension ids change with time and machine?
You can simply goto this URL: https://chrome.google.com/webstore/detail/TEXT/ID_HERE. The TEXT part doesn't matter, it will redirect automatically.
However, note that if the extension is installed locally, or is private, it will not appear on the webstore. Locally installed extensions will have an orange icon in the bottom-right of their logo on the chrome://extensions page.
See also: How is the Chrome Extension ID of an unpacked extension generated?
another alternative, if it is an extension you already have installed:
got to chrome://extensions
enable "developer mode"
ctrl+f and write the id (or just the first 3-4 characters of the id)
We have created a Chrome Extension that is a companion to web sites that we host for our customers. These web sites are hosted under our domain name and interact with the extension using external messaging and relying on the sites being configured in the manifest similar to the following (abcdefg.com is a ficticious domain name):
"externally_connectable": {
"matches": [ "http://*.abcdefg.com/*", "https://*.abcdefg.com/*"]
}
This works great in these cases. However, we have a subset of customers that prefer to host the website themselves under their own domain. The problem is that we do not want to update the extension manifest for the published extension to include all of these sites.
Is there any option of distributing a version of the extension (on Windows) where the "externally_connectable" site list can be set upon installation?
Thanks to kzahel for highlighting the obstacles I was facing and thanks to wOxxOm for providing a solution that will work.
Rather than trying to find a way to override the "externally_connectable" matches configuration upon installation, we found the easiest alternative was to avoid external messaging and use messaging via a content script instead.
The following is a copy of the solution posted above by wOxxOm:
chrome extension - alternative to externally_connectable?
Unfortunately there's no way to do this. You'll need to create a custom extension for every customer with their own domain name. Luckily, there is an API for updating the extension, so you would be able to at least update multiple extensions without too much difficulty. However, the 20 extension limit per account would be a little annoying. I think you can get more extension allowed per account by creating a publishing group and assigning the extensions there.
You could if you are willing to have customers install this in developer mode. That would bypass the 20-extension limit.
Chrome extensions can interfere with how a site is rendered and/or its behavior. This introduces unnecessary states and potential sources of errors.
So: Is there a way to disable all Chrome extensions for visitors of a certain website?
I dont think such API exists (we are taking about webiste scripts, right?) However you could determine if specific extension installed and update your code accordingly. Check this topic how to do this.
Even better and actual topic if you are fighting with adblock plus ;)
The best way to handle so far is to disable Extension sync in that specific browser.
Steps to follow:
https://superuser.com/questions/528014/how-to-disable-chrome-extensions-without-disabling-them-across-multiple-synced-d
.
I wish to run a content script when viewing the source of any web page. (and have a page action icon appear)
The docs here don't mention view-source as a valid scheme.
Is there a way around this limitation?
You cannot insert a content-script into view-source: pages. I didn't found a detailed explanation, but here is the related commit.