Uploading Chrome Extension - Error: Failed to process your item - google-chrome-extension

When uploading my zip file using the Developer Dashboard, I'm getting the following error:
An error occurred: Failed to process your item.
Can not process the manifest file.,Can not process the message.json file.,Can not process the key.pem file.,Chrome Web Store system error, please try again later.
I've followed 3 different tutorials (2 on extensions, and 1 on uploading to the Developer Dashboard) that I found on creating an extension on Googles' site. None of them say to create a message.json so I didn't create one (not sure why its telling me it can't process it). There is also no key.pem file, as they said do not generate this file and don't include it - as it will be generated when you upload it.
It says try again later, but I've tried several weeks now with no luck.
Currently, I'm exploring if my zip file is generated "funny" from 7-zip. I'd use the built in windows zip once I get that working again - however it seems corrupted.
My manifest file is in the root folder, and and the extension works in developer mode on my chrome. I've quadruple checked that the JSON is valid as well.
The extension works great for me, but fails the upload process.
How do I get past this step of the process?

Make sure manifest.json is in the root of the zip archive (not inside any directory)
Use the standard deflate zipping method in 7-zip, not anything fancy like deflate64

The answer to this was:
In the 7-Zip settings, I was using the compression method Deflate64, I changed it to Deflate and it the zip file was accepted. Thanks to #wOxxOm
I probably wouldn't have had this problem but my windows built in zip is currently corrupted and used 7zip to make a zip file.

Related

IIS cannot download zip file not being completed

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

Joomla 3 problems using Akeeba Release system with zip

I'm trying to use the Joomla ARS. I've set it up and it seems to work for everything except the download of zip files.
I've set it up so that you can see the file in the front end but when you click on it a:
The requested document was not found on this server
error is thrown.
I've tried directly linking the file and it downloads fine. I've also set up an article to check that it'll download and again it works fine. So I don't think there are any permission issues since the zip file can be downloaded just not by using ARS.
Finally I've also tried different file types in ARS and if I swap the zip file for an xml file or a pdf file they both download fine.
Any ideas about how to debug?
I figured it out :)
The site had add a suffix to url switched on which was stopping it getting the correct route. Changed that and it worked as expected.

Amazon Echo Lambda Function ZIP issue

So, I'm trying to invoke a Google Could Messaging service from Amazon echo, using NodeJS (using mac os x).
Since my main.js file contains 3rd party libraries, I installed them with
"npm install" command. I'm using the following libraries for sure:
https://github.com/ToothlessGear/node-gcm for NodeJS Google Could Messaging
async
When I made my ZIP file and uploaded to amazon lambda, I got the following error message:
It looks like your Lambda function "oAa" is unable to be edited inline, so you need to re-upload any changes. This may be because your file is too large or your zip file contains more than one file to edit. However, you can still invoke your function right now.
The ZIP file isn't large, it's only 1.5 Mb. I assume I have this error, because the file contains all the libraries I need, with more than one js file.
I've attached the folder structure of my ZIP file. It contains from one file and one folder. I have one file in the main folder, and a tons of libraries next to it (inside the second folder).
UPDATE
this is the error message what I get:
{
"errorMessage": "Exception: TypeError: Cannot read property 'application' of undefined"
}
and this didn't work as a solution:
https://forums.developer.amazon.com/forums/message.jspa?messageID=18330
Did any of you met with the same issue in the past? May I kindly ask for your help, guys ?
Thanks,
Karoly
I got it to work by not zipping the directory (and contents) but by adding the contents of the directory to a zip archive. Basically, I removed the upper level directory. AWS Lambda's UI was able to locate my .js then.
It's hard to tell what exactly the problem is with Alexa, did you make sure you filled out the configuration and event sources tab correctly (this would be under the AWS part). Did you update your application ID? This is the biggest pain in the butt. Did you just upload your zip folder and click test? (which is incorrect).
I don't think this is an error, per se. I get this frequently and my skills still work without problem. I believe all this means is that "your Lambda function xxxx is unable to be edited inline". You will have to continue editing in an external editor and uploading the zip instead of being able to edit in Amazons lambda text editor.
I think the TypeError in your update is an unrelated issue.
I was receiving this error and solved it by looking at CloudWatch logs. You will see much more detailed error messages in there, and a log will be created each time you try to run your function.

Unable to upload files; file upload modal displays CP Home

I am tearing my hair out with a file weird file upload issue that I have never run into before. For some reason I’m unable to upload images via the file manager (both in the file manager itself and if I upload with a custom field using the “file” fieldtype). Strangely, if I add files directly to any of the file upload directories, and sync the files, everything works fine.
After selecting the file and hitting “upload file” (see 01_choose_file.jpg) the modal window displays the CP homepage in an iframe (see 02_upload_progress.jpg).
Has anyone else seen this? Does anyone know how I can start troubleshooting this?
Background Info:
I’m running EECMS v2.5.2 - Build Date: 20120606 in MAMP (only 2 out of 15 sites I have set up locally are not working)
I have tried uploading images/files using the latest versions of Chrome, Chrome Canary, Safari, and Firefox (OS X 10.7.5)
This issue is showing up on the two latest sites I’ve started dev’ing locally on, no other site (locally or otherwise)
Things I’ve done:
Checked Apache/PHP error logs; they don’t show anything
Confirmed file upload paths and file upload directory settings are correct – I can sync files that i manually move into the various file upload directories
Permissions are fine; image manipulations and thumbnail creation work fine if I manually add files to the upload directories
Tested various other 2.5.2 installs I dev on locally and they work fine (settings on these two new sites are identical to sites that work)
Only a handful of native add-ons are enabled
“Apply XSS Filtering to uploaded files?” setting Yes or No does not make a difference
Huge thanks for any help!
I can't post images so here are links to the images:
01_choose_file.jpg: http://expressionengine.com/?ACT=51&fid=105&aid=16264_Jiof3p0V1gfEEFrpC55G&board_id=5
02_upload_progress.jpg: http://expressionengine.com/?ACT=51&fid=105&aid=16265_mjGH02xK2fIFZJI6kruP&board_id=5
I have sorted this out. I went back through to make sure I disabled all third party add-ons and I had forgotten to uninstall the "Quickee" extension http://devot-ee.com/add-ons/quickee. For now that seems to be the culprit.
I've submitted the bug to Matt (the developer) and it should be patched up soon.
The ExpressionEngine filemanager sends out a AJAX POST request to the following URL:
http://YOUR_ADMIN_CP_URL?S=0&D=cp&C=content_files_modal&M=upload_file
Have you tried loading that URL yourself? You should get a page like this
But maybe EE is trying to POST to a different URL. You can find it by uploading a large file and while it's uploading using Firebug and in the Network tab at the bottom of the list you will find the URL EE is posting to

MODX Revo - Unable to upload or view files in File section in Manager

I'm having problems uploading and even viewing files in the File section of MODX Revolution 2.2.3-pl. When I try to upload a file, all I get is "Upload error". Nothing shows up in the Filesystem area, just a folder called Media that doesn't let me do anything. Any ideas of what might be going on?
As far as file system permissions go, all folders are set to 755 and all files are set to 644. I'm seeing this behavior logged in as admin/sudo. I just moved my installation of MODX from my local machine, where I believe it worked right, to a shared hosting environment, and that's where I'm seeing this issue.
There has been a recent update to 2.2.4-pl after reported problems with the file manager.
I'd recommend updating to 2.2.4-pl and check if the problem is still present.
Also it could be that your MOD system settings have Use Multibyte Extension enabled but PHP hasn’t been compiled with the –enable-mbstring option.
Hidden away in the MODx Media Browser is a failed response to a JSON request and an error message showing…
Fatal error: Call to undefined function mb_strtolower() in on line 168
If you can’t recompile PHP or just need to get your Media Browser working again, go to System Settings and set Multibyte Extension to No.
All the credit to [Max Mitchell's Post].1

Resources