If I change the name in my extension's manifest.json, will it create a new extension or successfully change the name?
I'd like to rename (in order to 'rebrand' a bit) an existing extension, but don't want to create a distinct new one - because I want existing users to get other bundled updates. Just want to change the name users see in the store.
I checked in Chrome's developer's site, but didn't find anything related to this mentioned in any of the pages or FAQs, other than a statement saying the name is 'used to identify the extension' which makes me inclined to believe it's not possible.
Yes, if you change the name of the manifest file it will rename the entire extension. Same with the description. But the store ID will remain the same.
Related
I want a user to share a URL to a Google Doc. When another user follows the link, they must make a copy and that copy is available in a shared folder. Are their parameters I can add to the URL to do this?
The users are students and teachers. Users share the same Google Workspace domain. The students have major digital literacy gaps so any steps I can remove to sharing to their teachers is significant.
Given the url of your google docs file, you need to replace edit with copy and use ©Destination=[Drive_FolderID] (optional) to redirect the copied file to a specific folder.
As for the share to a shared folder, I can't find any parameter for it. The copyDestination might still work in your case.
From:
https://docs.google.com/document/d/[Doc_FileID]/edit?resourcekey=[Resource_Key]
To:
https://docs.google.com/document/d/[Doc_FileID]/copy?resourcekey=[Resource_Key]©Destination=[Drive_FolderID]
After confirming to "Make a copy", it opens the copied file and will show on the Drive folder.
Output:
The Microsoft support site (https://support.office.com/en-us/article/check-out-check-in-or-discard-changes-to-files-in-a-library-7e2c12a9-a874-4393-9511-1378a700f6de) says that with suitable permissions it is possible to Check In a file that has been Checked Out by another user and this should retain any changes they have made whereas discarding the Check In will lose them. Even with Site Admin privileges I have been unable to locate this option and wonder if it has been withdrawn?
I have looked within the Library Settings at "Manage files which have no checked in version" but this does not show files which are Checked Out within a Document Set in that Library. I don't know if this is because a Checked In version does exist - the previous version - but suspect that may be the reason.
Can anyone advise if this option is still available or not?
The option only works for files with no checked in version.
Per my test, if I try to check in a page which is checked out by other user currently, I will get the message that "Do you want to override this check out now?"
When I click ok, it will not lose any changes made to the file. So you could use this wat to check in another user's file.
I'm using MIGX to aggregate info for product entries. By default, the MODX file browser opens to directory "Files", where I'd like it to open to "Files->assets->img->products". Do I need a snippet to do this, and what variable would I set? (Or better yet, where is this type of info to be found in the rtfm?)
Thanks much!
The proper way is to create a new media source, or use the default one, and change the default browse directory for that media source. You can then restrict a specific user group to the media source or let everyone use it by default.
Ok,
So about a year ago (I think) google went through a transition where they made Google Apps accounts "real" so we could use them in places like the Chrome Web Store. Unfortunately, prior to that happening I had written some extensions that were under the now conflicting account. So, now what I've got is a two accounts where the old extensions are under this conflicting account and anything past that date is under the new account.
So, it is time to upgrade some of these (old extensions), what I'd like to do is move the extensions under the apps account in a way that doesn't cause problems for the users. Does anyone know a way? It seems like the only option is just to place the extensions under the new account and delete them under the old account, but then I think all of the users would have to know to install the new one.
Thoughts? Has someone gone through this process?
EDIT: As #artur-nowak pointed out in the comments it is now possible to transfer extensions between accounts using this form.
If only your extensions were hosted outside Chrome Web Store (CWS) it would be possible to solve this by modifying update_url in manifest.json (so that extensions will start to download updates from another source). But they are not, and CWS doesn't allow you to modify the update_url param. Because of that, I believe you have two options left:
wait for google to add 'change ownership' function in CWS
or add your extensions to CWS again as a desired user and update the old ones to display a popup/notification "please update" with a link to the new version. Users should be more eager to update if you include some new features to attract them. Also, it will be less annoying from them if config will be preserved. To achieve this, export settings to bookmarks panel (it will be easy to access them) and import them in the new version of extension when it's installed.
I'm looking for a way to localize SharePoint 2010 Folder Names, for a specific application.
I've seen that site names/description are automatically translated, and it seems like SharePoint 2010 supports "multilingual" fields for metadata - but I haven't been able to apply this successfully for folder names.
The folders are automatically generated, and the number of folder is limited (so I'm not looking at providing the users a way to translate their folder names, but a way to localize a predefined folder structure).
In a nutshell :
- is there a way to localize folder names ?
- if yes, is what's the best way to deploy this as part of a solution ?
Have you considered how Managed Metadata might be able to help you with this? If you're able to control terms that are also localized in Taxonomy, perhaps when creating a folder you would pull from the Managed Metadata Store, and then display the appropriate language based on the user's language setting. Just a thought... Since you know the name of the folder ahead of time, you could use that as a label for a folder name term, and then pull another label that matches the user's language and display that.
You can start using a resource files in your project and this link can help you about it.
But if you want to let the user, who creates a folder to set its localized name; then you should consider using SP event receivers.
I hope I've understood you correctly.