Thread

For the record, I’ve tested this EE installation running both lighttpd (my preferred default) and Apache2, and the results are the same. Can’t insert images from the publish page, upload hangs, but is successful from the File Manger.

I’m having the same problems as above too. In file manager I get this error message.

Fatal error: Using $this when not in object context in /home/*******/public_html/system/expressionengine/config/mimes.php on line 62

I have the same problem. my post

HotLimbo,

Can you go ahead and replace system/expressionengine/config/mimes.php with the latest from your 2.1 download and see if that makes a difference for you

I’m having the same issue. I’m trying to upload a flash file that’s about 7 meg and get two differenet errors depending on where I try to uplaod it. From the file manager I get “upload_no_file_selected”. From editing a channel entry I get “You do not have access to this upload directory.”. If I try to upload a jpg in the same ways I have no problems.

I’ve confirmed the file upload preferences will allow me to upload any file type and size. I’ve also double checked my php.ini and everything looks as through I should be able to upload 40 meg, plenty of space and time set aside there.

I’m running Build: 20100810 on apache 2.0

thanks
summer

I had a similar experience. Using the File Manager, I uploaded two 6MB PDF files. Both times it continued to say “uploading” and the filename field never populated with either filename. But when I clicked upload, I received the “upload_no_file_selected” error. However, both files uploaded and appeared in the file list.

I’m also running Build 20100810 on a Windows server.

After a pretty grueling upgrade process that’s lasted a few days, I’ve decided to call it a ‘learning experience’ and keep all our existing and new sites running on 1.6.9. This is actually the second time I’ve spent many hours attempting to migrate to a 2.x branch — the first a few months ago — but it appears things still aren’t ready, at least for me.

Even if we figure out this File Manager issue, I’m not a big fan of how file insertion works on the publish pages now, with no way to sort files by date added or file type within the modal box. Also, no telling where the next hiccup or show stopper will be.

Thanks to the EE Mods for their help.

PNCA_webteam,

I apologize the upgrade process has been such an issue for you. The hardest part here is that I cannot replicate the issue you or indeed others are having so it’s become quite hard to troubleshoot. I have created an internal request for my colleagues to see if they can replicate any bit of this thread and we will try and get this one resolved as soon as possible for you.

I found the problem actually to be limited to Safari. The file manager actually worked very rarely for me in Safari, I think the time I saw it work first (in the clean install) was almost a fluke. It seems to me the problem has to do with the File <input> in the file manager. For me, in Safari, after selecting a file, the file input field is never populated with a value (it always reads “no file selected”). Every once in a while I would get an error from EE saying “no file selected,” and every great once in a while it would actually just work, and upload a file. But, a majority of the time it would just hang, neither giving an error nor uploading a file. It seems to work fine for me in FF, however.

That exactly describes my experiences right now, as I (try to) upload PDFs.

However, I think I’ve finally broken Safari’s will to misbehave and I’m now uploading with impunity .. for now!

We have been able to replicate to a degree internally so I created a bug report here. If anyone has anything further to add to it feel free to do so.

Hey John,

I wasn’t able to come back to this problem since I posted last week. I followed your suggestion to replace the “mimes.php” file in expressionengine/config/ folder with an “updated” version…. And voilá! Everything works!  :cheese:

So my problem is resolved now. Thanks!

I don’t know about the others. But maybe they fell under the same misconception I did. I initially downloaded the current version of ExpressionEngine v2.1.0 Build 20100810 on 22 July (which is weird - since the build, I think, is the date of release. In that case August 10. no?) However, I would have disregarded your suggestion since when I return to the “my downlaods/my purchases” area of this site I saw that the build number was still exactly the same.

But, as I discovered today, there were changes made to the contents of the zip file I downloaded on 22 July and the one that was now on the “my downloads” section. Normally I would question the value in downloading the same files all over again. Anyways, I did. Lo-and-behold, the mimes.php file in the latest download of the “same” build was smaller than the one I downloaded on 22 July.

So my question now is, to avoid confusion, shouldn’t the build number then have changed too? From Build 20100810 to maybe Build 20100825? I don’t know. What policy or guidelines are followed to indicate that some change was made to the latest build?

I can imagine if you always changed the build number when you change just one line of code in one file every other day a lot of people would get frustrated if they then thought they had to reinstall each and every time a small change was made. But as a non-developer (for now, I hope) I am not sure what else I should read into the build number. Is it a major release number?

Oh hang on. My mistake!!!

The mimes.php files were exactly the same between the 22 July download and the download of today. It was the mimes.php file on the server I replaced that was different. The original one replaced was 6kbytes big approximately. While the latest one was 4Kbytes aproximately. Interesting. Does mimes.php get altered during installation?

No, mimes.php should not ge altered during installation although it might be possible somebody did so manually, perhaps? You’re up and running I take it?

Yes. Up and running. Thank you.

HotLimbo,

Usually the config folder which contains the mimes file is carried over for an update of a build or a version but if you have been updating since the beta or very early on there have been a few changes to that file hence me asking you to refresh it.