This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
September 06, 2012 2:18am
Subscribe [1]#1 / Sep 06, 2012 2:18am
We’ve got some custom code that we built for uploading files into individual directories based upon the user, and following the upgrade to 2.5.2 this past week it seems to have broken the upload, and now the files won’t upload. What types of changes were made to that part of the system with this upgrade so we can try to diagnose the problem?
Thanks.
#2 / Sep 07, 2012 2:28pm
Hi tableture,
Generally speaking, you’ll want to investigate the changes noted in the change log and the version notes. Which version were you upgrading from? And how did you custom code go about adding the uploaded files’ information to the database? Let me know and I’ll see if I can’t figure out what’s going on for you.
#3 / Sep 23, 2012 7:33pm
In looking at bug fixes, I found this one in 2.5.0 “Fixed a bug where the currently selected upload folder on the File Manager page was not used as the default in the Upload File dialog” that may have been the one that caused the error, because I did a rollback to 2.4.0 and the uploads are working again. This one may also be a culprit: “Fixed a bug (#17510) where the file entires tag wouldn’t honor the directory_id parameter if the directory ID belonged to another site.
” From what I can tell, my now-long-gone developer created a plugin to handle all of the file upload directories.
Not sure where to go from here without having a lot more work done to fix this unless I don’t upgrade…
#4 / Sep 23, 2012 11:50pm
One other issue that came up with my rollback to 2.4: I now get the “Your system folder path does not appear to be set correctly. Please open the following file and correct this: index.php” error, but my index.php and admin.php files both have the correct system path and permissions are all set as defined on the update page in the user manual. Any thoughts on that one?
#5 / Sep 24, 2012 4:54pm
How did you perform the roll-back to 2.4.0? Did you clear the files and database from the upgrade and import the 2.4.0 database backup and restore the files from your 2.4.0 backup? That’s the only way that a roll-back should really be performed, since a database downgrade is not supported.
Since it sounds like your former developer has sadly flown the coop, you might need to look at working with a new developer to make sure the custom work you’ve had done is compatible with the updates to EE as of 2.5.3.