I just migrated from Liferay 6.2 to Liferay 7.0. So far Everything looks great. The site's theme still needs a couple of adjustments, but in general, everything looks great.
But now I have a problem. The content of a page was expired, this page is using a Web Content Display, so I went to Configuration in order to select another web content, but in the list of contents, there are no contents listed. In the Web Content section of the site, there are many web contents available. This is also happening in every page of the site that is using a Web Content Display.
So how can I figure out what is happening, why there are no contents listed in the configuration of the Web Content Display?
My problem was solved. Honestly, there was no problem. The full search re-index toke several hours to finish. So after the re-index process finished, all web contents were available again. The first time I run the re-index process, I expected immediate results. What I didn't know was that I have to wait until the process finished.
I want ot create a release for my Github project, but when I try to upload my binary (which is a .zip file) to the release, I get the following error message:
Something went really wrong, and we can’t process that file.
I get the same error message if I try to upload some other files (e.g. my readme file). What could be wrong?
Check first if this issue persists with all browser.
I have seen this error message before, where the upload succeeded with Chrome, but not Firefox.
For the record in my case this was due to an obvious mistake: I had to authorize a github script in NoScript.
If someone encounters this problem in China, and is using ShadowSocks, try turning ShadowSocks off.
I was trying to upload an image file in png format on chrome browser but I was getting the same message.As suggested in one of the answer, I turned off windows firewall and it worked.
But my mind was not satisfied and I turned on Windows firewall and converted that image to jpg format and it got uploaded.
But this stubborn mind was not satisfied and told me to upload this in .png format only.God came to my rescue and accidentally properties tab of png image got opened and at the bottom of tab, it was showing
"This file came from another computer and might be blocked".
So I unblocked it and it got uploaded.
I got that error due to my companies firewall that prevents all file uploads. Might this be the cause of your problems?
The problem occurs during file upload because I was using VPN which doesn't allow file upload hence I disconnected from VPN and then try uploading which work absolutely fine. So my advice to check your firewall/VPN settings as mostly Organization doesn't allow fileupload in GIT due to security concern.
I got the same problem on Opera browser(Ubuntu 18.04.1).
Then I realized that my browser does not have permission to access the related(where your files located) partition. I moved the files that I wanted to upload on Github into accessible partition by Opera browser in my HDD, Thus I could be able to upload my files to Github.
It worked like a charm. Hope this helps.
clear your browser's cookies and cache ..after clearing files will be uploaded easily on git without error
In my case. I'm reuploading two zip files to an existing release. One success and another one failed. Tried in both chrome and firefox.
My solution is to use the hub command-line tool.
I use the below command to edit the existing release and attach files to it.
hub release edit --draft=false --attach FILE TAG
For some reason, I had to change its prefix from .png to .jpg and it worked.
I had the same problem which I solved by disabling my firewall. I hope this will work for you
In my case, it was my anti-virus (AVG) preventing the upload.
In my case, Avast antivirus was blocking the objects-origin.githubusercontent.com site, and made the upload fail.
After disabling the antivirus, I was able to upload the files.
Well! That is because your are uploading some images that you have downloaded from the internet like in my case I have used a favicon that is generated from website to solve the issue Image with security details~img1
Image with detail~img2
Remove personal info ~ img3
To solve the problem
first of all head to the images that you have downloaded from internet and right click on image and click on properties
check the unblock checkbox as shown in image 1 and then
click on the details tab as shown in image 2 and then click on the remove properties and personal information
And then check on the remove the following properties on the file as shown in image 3
And then click on ok and then again ok
The given solution will solve your issue it just worked perfect for me
Files cannot be uploaded because your network provider doesn't allow, use different network or apply vpn for uploading the files.
All of a sudden one of our sites has developed an issue with TinyMCE, specifically it seems, in relation to the advimage plugin.
When trying to browse the image folder via TinyMCE I get an alert with one of these errors:
In Chrome I get:
2can't process ajax,TypeError: Cannot read property 'responseText' of null
In Firefox I get:
2can't process ajax,Invalid XML structure
Nothing has changed on this site for a good few months.
We have upgraded to PHP 5.4 very recently, but I don't see why that would be related.
This could be an issue with overly large images in the plugin's upload directory.
On each request, the advimage plugin scans the upload directory (set in your config) and generates thumbnails of any images it finds in there, then sends a list of images off to the client in the form of JSON or XML. If an image is too large to process, (low server memory or something), then the process quits and doesn't return any JSON/XML, hence the seemingly unrelated error message.
Prune any images over 1MB from the uploads directory. You may need to flush the cached thumbs as well. To stop your users/admins from uploading huge images, set an upload limit in the plugins config.
After reading Steve Sandersons post on swf upload.
http://blog.stevensanderson.com/2008/11/24/jquery-ajax-uploader-plugin-with-progress-bar/
I have implemented the swf upload on a site I am working on, Some users are getting a variety of issues where the progress bar gets stuck, or they get the error message 2038 - with error code -220 (System IO error.) - this is not related to Certificates as in the test below both addresses can be accessed with http or https
I haven't been able to reproduce much of these errors, However when trying to upload large images over 2 mb
It works fine on the test site, But not on the live
UPDATE: I had posted examples here, now removed as the links don't work.
Both sites hosted on App Harbor. exactly the same code.
The Limit for image uploads should be 10 mb - and I have successfully uploaded larger images that the one posted here.
what could be the cause of this?
Can I ask what language the rest of the site is written in?
My first thought is that if it's an IO error it could be running out of space?
Run:
Df -h
On the servers and see what we get, remember that all file uploads are written to /tmp before being moved where you want them, so if that fills upload stops.
This turned out to be a configurations setting at the load balancer level, We have a dedicated load balancer with app harbor to so we can offer full ssl support. It had not been set up to allow requestes of 10mb, they have changed it now.
Just don't forget to have the parameters in php.ini that set :
session cookies to on
and session.use_only_cookies to off
and in the js plugin session are handled this way:
post_params: {
<?php echo "'".ini_get('session.name')."':'".session_id()."',"; ?>
}
Furthermore, don't forget to check the list of images extensions handled by your js plugin
net page to upload a large file and a generic handler to play these large wmv video files of size which can be upto 150 MB's. I have the file content stored in varbinary type in SQL Server 2005.
I have set following settings in httpRuntime in web.config
<httpRuntime executionTimeout="110"
maxRequestLength="2097151"
requestLengthDiskThreshold="2097150"
shutdownTimeout="600"
delayNotificationTimeout="400"/>
The problem is that sometimes my files doesnt play. It get uploaded properly but when playing the request seems to get timeout. I was able to play files upto 100 MB's. It works 9 out of 10 times on local and production but why does it fails sometimes. The same file get played in one instance but on other instance it doesnt. Can anybody suggest where the problem may be. I think there must be some combination of httpRuntime attributes which i am missing. Please suggest. Its a production issue which keeps popping up.
why don't you use IHttpHandler? try this Uploading FIle Using IHttpHandler Might be there will be better solutions to use IHttpHandler if you will search for it.