I'm working with an extension for chrome, and I'm supposed to use the Id of the extension.
I'm able to get the Id from the developer mode (it's an unpackaged extension).
So my doubts are:
When I publish the extension on the chrome extension store everyone will have a different Id?
If yes, how could I access it via code? (react.js)
Related
I am distributing Firefox ESR in an enterprise environment, including a homemade WebExtension in the distribution\extension directory as explained in https://support.mozilla.org/en-US/kb/deploying-firefox-with-extensions
This instance of Firefox is installed to be used for a particular set of applications and is not intended to be used as the user's main browser. It is launched through a cmd script with a specific profile, for instance :
Firefox\browser\firefox.exe -profile myParticularProfile
Starting Firefox this way creates the profile if not already present, and the profile will not be visible in the profile manager.
Everything is fine after initial installation : every new profile of every user will get the extension copied to the extensions directory of its profile, and the extension is activated.
However, I need to be able to update the extension without reinstalling Firefox. The problem is, the updated extension does not get copied to existing profiles.
The documentation says that the extensions will be updated when Firefox is updated, but I need to be able to update the extension without updating/reinstalling Firefox.
Clearing the "extensions" folder in the profile does not solve the problem (the extension does not come back with the update version as I hoped)
I also tried clearing various cache directories without success
I hope I will not need to write a command script to update the extensions myself since I am not certain I will be able to easily locate and modify every user's profiles.
Maybe suggesting to firefox that it has been updated (even if it is not true) would do the trick, but I do not know if this is possible.
Any ideas ?
I am trying to load a simple .txt file content with a Chrome App (using file: protocol); I need to show its content for the user in a <div>. I need to open the file from a path typed in a input text (or defined in a string variable).
The flag --allow-file-access-from-files works fine when I load my .txt file content through Chrome browser. However, when I try to do the same with my Chrome App launcher (I have applied --allow-file-access-from-files flag on it), it keeps telling
Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource.
I dont know if I am missing something or if it is impossible for chrome app.
My user will work with the app in Windows platform.
I finally figured out that --allow-file-access-from-files does not work at all in my case.
I started coding using fileSystem and made something like the recomended in this question, following the main example. Now I am able to work with files in a directory asking the user to choose it only one time.
I'm developing an extension (and website) for a friend who needs to make different profiles for people, comparable to an intranet or online address-book.
The extension works almost great, but I'd like to have an option to upload profile pictures at the frontend in the create and edit action.
The example of Helhum on Github somehow doesn't work on Typo3 7.4. It tells me
An error occurred while trying to call Helhum\UploadExample\Controller\ExampleController->createAction()
image:
Object with identifier "1:/content/" does not exist in storage
Problem might be that you do not have that folder. You can try with default user upload folder like:
UploadedFileReferenceConverter::CONFIGURATION_UPLOAD_FOLDER =>
'1:/user_upload/'
I am using an App on my site that is kind of a list and allow you to select a file.
Is there a way to restrict the file extension that the user can select? Can I do a receiver(event handler) to handle this?
I do not want to restrict the file extension for the whole site. Only for this portion.
Thank you.
For SharePoint Online, this is the list of supported file types that can be stored in SharePoint Online -
http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/types-of-files-that-cannot-be-added-to-a-list-or-library-HA101907868.aspx?CTT=5&origin=HA102694293
This list is not customizable. Note that SharePoint Online does have virus protection built in to check files when they are uploaded.
Also check:
http://community.office365.com/en-us/f/154/t/149796.
For workarounds:
http://community.office365.com/en-us/f/154/t/239908.aspx
I created a simple demo passbook pass in iOS 6. I emailed it to myself and it works fine. Now I need to share it with people. I uploaded the .pkpass file to the server but safari is not able to recognize the file format or mime type and hence it does not download it.
Any ideas how can I share it?
Safari should recognise these.
I think you probably need to add the MIME type to your web server, so it knows how to present the file to visitors.
Edit: the MIME type you need to add to your web server is application/vnd.apple.pkpass
Passbook is only availiable on the iPhone 5 or phone users that have upgraded is iOS6. It is also available on the latest OS X Mountain Lion 10.8.2 release.
If the person doesn't have any of these, when they see it in their email, it will just show the .pkpass file as is. If they have Passbook on their device, it will do some graphical markup to it and they can click to add it to Passbook.
The MIME type has to be supported by your email server, but since you received the pass, it appears your server supports it, or doesn't care. In my case, we had issues with Amazon Web Services Simple Email Services as their WebAPI wasn't accepting files of type:
application/vnd.apple.pkpass
Which has been remedied.
https://forums.aws.amazon.com/thread.jspa?messageID=384277
To download a passbook file in Safari (mobile and desktop), you have add the correct mimetype to your server.
To do so, you can simply create an .htaccess file (or edit the existing one) and append the following line:
AddType application/vnd.apple.pkpass .pkpass
This will do the magic. After this change, if you'll click on a link <a href="..."> that points to a .pkpass file using Safari mobile on your iPhone it will automatically open it with Passbook.
I think that the pkpass files will only be recognised by:
Devices running iOS6 and above (i.e. with the passbook App installed)
Safari on OSX 10.8.2 (or above)
Edit: Google Chrome Version 23.0.1271.91 and above on iOS6 now also supports direct download of .pkpass files