I meet some problems about newly published extensions in this month.
When I download my extensions from Developer Dashboard by this type
I can install extension normally by pushing it into chrome, but now newly published extension cannot install it before version 60 and publish an error:
I don't know how to figure it or if web store did some crx package change?
Can anyone meet this problem?And help me.Tks.
PS: I download crx by other types from Google, this crx file can install normally and MD5 is different from crx file from Developer Dashboard.
Try 1:- change Change ext version in manifist.Json
Try 2:- remove really unwanted config from manifist.Json
Try 3:- remove unwanted
file from directory.
Related
I updated some code in an unlisted extension I am managing, published it to the store as usual, and it has successfully updated the version number.
When I attempt to install it, I get:
Package is invalid: 'CRX_HEADER_INVALID'.
The crx file is created for me, as per the docs here: https://developer.chrome.com/docs/webstore/faq/#creating-a-listing
... I just upload the zip file containing my extension's code, as such I don't know what to do. I checked it is crx3 and it is. I am running Chrome Version 88.0.4324.96. I tried to install the previous version that was on the store, and the same package is invalid pop up appears, so the only thing I can think is that the issue could be down to how this crx file is created from my zip. Not sure how I would go about dealing with this, or if someone else had had this issue maybe they know whats going on?
EDIT: Have tried it on multiple versions of Chrome, same outcome on all. Believe the issue is with the conversion to crx file, but am yet to identify what the issue is.
I had to migrate to Manifest V3 in order to fix this.
The Google documentation "Introducing Manifest V3" did not state anywhere that migration was a required step in order to update an extension that was already on the store.
i'm trying to download zip file from my application hosted on IIS, but unfortunately the download is not being completed, it's stuck on 99%
i tried to change the MYME-Type to octet-stream, without luck. also i tired to manage the MYME-Type from the web.config with same situation.
NOTES: 1- I'm able to download RAR files without any issue.
2- I'm using IIS 7.5 under windows server 2012
According to your captured image, I guess you used chrome to download the file. There are two reason which will cause this issue.
One is your computer has installed the anti-virus checking for the downloaded files. I suggest you could try to disable the related setting and try again.
Besides, the chrome has contained the build-in scanning/checking the files which is used to checking the download files. I suggest you could try to start chrome with this switch:
--safebrowsing-disable-download-protection
Firefox standard and beta version does not allow unsigned extensions, so I use Firefox developer edition and set xpinstall.signatures.required to false in about:config.
I download source from https://github.com/mdn/webextensions-examples and use my script to build xpi (after putting it to root directory of repo and copying my manifest-firefox.json as well).
For each extension, as you can see from the script, I copy it to a temp folder, modify manifest.json (remove chrome-only fields if any and add gecho for firefox) and zip all into one file.
However, when I tried to install them one by one, I failed to install all.
Every time I installed one, it would replace previous.
Steps:
Click Menu bar - Tools - Add-ons to open Add-ons Manager
Click Extensions and then gear on the right
Click Install Add-on From File and choose one under path/to/webextensions-examples/dist
Did I miss anything in my build script to cause this? Or is this as designed to only allow one unsigned extension?
I'm 4 years too late but for anyone that finds this question later this is due to having the same "id" for the multiple extensions if you're using "browser_specific_settings" in your manifest
I run FCKEDITOR 6.x-2.3 on a drupal 6 website, a bunch of hacker team worked to see if there is any security issue on website and they found some vulnerabilities with FCKEDITOR, an anonymous user can upload files to the server using some uploader like this one to the server.
for an anonymouse user I can access direcotries such as:
sites/all/modules/fckeditor/fckeditor/editor/filemanager/browser/default/browser.html
sites/all/modules/fckeditor/fckeditor/editor/filemanager/browser/default/frmupload.html
to upload my uploader file. is there a way to fix it? or I should forget about using FCKEDITOR or any other wysiwyg editors?
You can update your FCKEditor module (check: http://drupal.org/node/1482442)
Or,
you can use CKEditor instead of FCKEDITOR. See: http://drupal.org/project/ckeditor
I have faced similar security issue using CKEditor. And I have following the below steps:
Here is the process to update ckeditor and ckfinder:
Update CKeditor version 6.x—1.13
Download CK Finder latest version 2.3
Unzip the ckfinder in sites/all/module/contrib/ckeditor/ckfinder
Open /all/module/contrib/ckeditor/ckfinder/config.php
Comment out the CheckAuthentication() function
Add the below two lines
$baseUrl may differ depends on products.
Open /contrib/ckeditor/ckfinder/config.js
add the below lines:
Note: I would like to request all to prepare a set of allowed and denied extensions
One more additional issue: Add cookie_domain in sites/default/settings.php file.
Our firm has begun building MonoTouch iPad/iPhone apps for enterprise deployment.
How do I take the app and create a *.ipa file for upload to our MDM server?
An .ipa file is basically a glorified .zip file. There are a couple of routes you can go down:
Export the project to xcode and under "Build" click "Build and Archive" - fill in the appropriate details and the project should create the .ipa for you as expected.
If this isn't an option, (which it isnt for us, so this is the method I've used, to great success) you can simply create all the components that go into the .ipa and right-click, "Compress..." in Finder.
The .ipa is made up of the following components:
A folder named "Payload", which contains the compiled (release/iPhone) .app
a 57x57 .png icon file (which is displayed while the app is being downloaded)
a 512x512 .png file of the icon once again - however this has to renamed itunesartwork with no extension
iTunesMetadata.plist - this contains information about the app, such as copyright name, genre, itemname, softwareIconNeedsShine (you can google what information this needs).
The way I package up our .ipa, is I have a folder called "App Packaging" which has all of these components already in, and I simply update the .app file whenever we do an upload, "Compress..." then rename the file to x.ipa (OS X will ask if you want to use this extension, make sure you select ("use .ipa" !).
With the current Monodevelop (2.8.6.5) and Monotouch (5.2.5) it is as easy as right clicking on your project -> options -> iPhone IPA Options -> check Build ad-hoc/enterprise package (IPA) for the desired configuration.
We created a special configuration called Distribution which builds using the Distribution Certificate and In House Distribution Profile.
Luke, I like your answer and have given you the credit. I am adding some more details for my own, and others, notes.
Use SpotLight to find one of your own MonoTouch apps. Search on ".ipa".
Rename it to SomeThing.Zip
Unzip it.
You can then use the structure of the unzipped folder to edit then rezip.
Just another way to get an IPA that made it easy for me, drag your .app file onto your itunes library and sync your device. ITunes then creates a copy of the app as an .ipa file in the user/music/itunes/itunes media/mobile applications. This can then be distributed much easier than the .app file.