Thread

Running EE 2.1.2 (build 20101215) I ran into an issue with a required custom field (File fieldtype). I uploaded a PDF, which worked fine (that is, it was uploaded successfully). But when I went to submit, the entry didn’t submit but instead refreshed and showed an error message that the field is required and no file was actually there. I also noticed that on publish, the custom file field is collapsed despite the setting for the custom field is set to show the field by default.

That is the only field this is occurring on, though. There are only two other custom fields (in two different field groups) that use the File fieldtype and both of those are set to accept images only. But when I upload, everything works as it should.

Because I knew that if I posted a support question I’d be asked what version of EE I’m running I figured I’d upgrade. But I ran into even bigger problems there. I tried three times to upgrade to 2.1.3 and every single time got a blank home page and a blank CP after the upgrade was supposedly complete.

I’ve since rolled the site back to 2.1.2.

I need to get the file upload issue fixed ASAP (I’m turning the site over to the client in the next couple days). Ideally I’d like to be able to upgrade to 2.1.3 as well, but that’s secondary at this point. Any help would be greatly appreciated!

Thanks!
.angie

In terms of the upgrade - it does work, as i have done it across a few sites. However, i do understand there is always different setups, and other bugs. Just be sure when you upgrade to follow the docs word for word and make sure your doing a full upgrade not a build update and you upload new themes too, clear cache in browser and EE.

In terms of the file field and upload issue. Firstly, a bug i have found and has been fixed for the next release is when you modify anything in channel fields, or channels, the custom channel layout gets messed up - typically this means a field you told not to be collapsed gets collapsed. You can either modify this and then re-save it, or reset it to default, re-configure it, then re-save it.
Upload issues, you saying the file definitely uploads - can you confirm this via FTP?
I would also suggest that you check 1. permissions to upload for your member group, 2. permissions for the upload location (check also file or image), 3. when you upload via the channel, when you return to publish does it actually show the filename in the field, or does it leave it blank, etc.

Angie,

Under your Security and Session Preferences turn off Apply XSS Filtering to uploaded files?. Does that help?

I tried three times to upgrade to 2.1.3 and every single time got a blank home page and a blank CP after the upgrade was supposedly complete.

Was this after running the Upgrade wizard in your browser?

In terms of the upgrade - it does work, as i have done it across a few sites.

As have I as this is not my first or second EE build. But for some reason this one does not.

In terms of the file field and upload issue. Firstly, a bug i have found and has been fixed for the next release is when you modify anything in channel fields, or channels, the custom channel layout gets messed up - typically this means a field you told not to be collapsed gets collapsed. You can either modify this and then re-save it, or reset it to default, re-configure it, then re-save it.

I’ll be sure to try reconfiguring the layout, thanks.

Upload issues, you saying the file definitely uploads - can you confirm this via FTP?

Yes.

I would also suggest that you check 1. permissions to upload for your member group, 2. permissions for the upload location (check also file or image), 3. when you upload via the channel, when you return to publish does it actually show the filename in the field, or does it leave it blank, etc.

1. Permissions is the first thing I checked. And it shouldn’t matter as I’m seeing the issue as a Super Admin.

2. Checked permissions here too, everything good (otherwise I would wager that the file wouldn’t upload in the first place).

3. No, it does not show the filename; leaves it blank.

Under your Security and Session Preferences turn off Apply XSS Filtering to uploaded files?. Does that help?

It’s already set to “no”. :/

Was this after running the Upgrade wizard in your browser?

Yes. I go through the entire upgrade process without issue and get nothing. I may try upgrading again tomorrow night just in case I missed something.

Hi, Angie. A blank control panel can be caused by several things.. one is a suppressed PHP error, the other is a lack of memory allocated to PHP.

Have you tried the following:

Change the debug = setting to:

$debug = 1;

in your /system/index.php file?

Have you seen: EEWiki:// HowTo Determine Memory Limits

-and-

EEWiki:// HowTo Override Memory Limitations

How much memory is allocated to PHP?

Okay, so I tried to upgrade again from 2.1.2 to 2.1.3 tonight. After several tries I finally got to the success message in the wizard where it asks you to delete the installer folder. So I did and I now have a blank CP and a blank home page.

I changed the debug setting in the /index.php to 1 and get this:

Fatal error: Call to undefined method CI_Config::site_prefs() in /home/[removed]/public_html/[myrenamedsystemfolder]/expressionengine/libraries/Core.php on line 152

I’m going to have to roll back again shortly. This is getting really, really frustrating. I’m now afraid to upgrade any EE site. :/

Yes, please roll back and try again. What exactly does “several tries” involve? If you’re encountering any issues please tell us about them immediately.

“Several tries” involves quite a bit. 😊

I’ve actually installed from scratch (no data or anything) on my local setup and then imported the database into that. Got it working. So next step is to get it onto the production server. Here goes… 😊

Okay, so both issues are resolved. Starting from scratch locally with 2.1.3, importing the database from the 2.1.2 and then moving it to the live server did the trick. Everything is good and working. Hopefully this site was just an anomaly when upgrading.

Thanks!

Excellent! Please don’t hesitate to post again as needed.