2.0.7 Upgrade package Problem

[iaccountant]

I get the same problem without any portal instal...but I do have the "articles" mod installed

This is the message I get....


Although the package was downloaded to the server it appears to be empty. Please check the Packages directory, and the "temp" sub-directory are both writable. If you continue to experience this problem you should try extracting the package on your PC and uploading the extracted files into a subdirectory in your Packages directory and try again. For example, if the package was called shout.tar.gz you should:
1) Download the package to your local PC and extract it into files.
2) Using an FTP client create a new directory in your "Packages" folder, in this example you may call it "shout".
3) Upload all the files from the extracted package to this directory.
4) Go back to the package manager browse page and the package will be automatically found by SMF.

[Arantor]

Yup, probably the same problem, same cause and another reason I don't want to try to work around this sort of thing in the base package - precisely because the list of mods that will be similarly affected is quite long (SP, TP, probably EP and DP, also Project Tools, the Arcade, Articles and probably more that I can bring to mind right now on top)

Mind you, 2.0.7 is as understood now should be uninstalled pending us fixing it properly.

[DarkAngel612]

I get the same problem without any portal instal...but I do have the "articles" mod installed

This is the message I get....


Although the package was downloaded to the server it appears to be empty. Please check the Packages directory, and the "temp" sub-directory are both writable. If you continue to experience this problem you should try extracting the package on your PC and uploading the extracted files into a subdirectory in your Packages directory and try again. For example, if the package was called shout.tar.gz you should:
1) Download the package to your local PC and extract it into files.
2) Using an FTP client create a new directory in your "Packages" folder, in this example you may call it "shout".
3) Upload all the files from the extracted package to this directory.
4) Go back to the package manager browse page and the package will be automatically found by SMF.

I have the same message and thought to put in  the list of my mods, hope it helps some too

[Arantor]

And as has now been stated a number of times, the 2.0.7 packages were all withdrawn because we found some late breaking issues which are currently in the process of being dealt with. Not surprising that the packages are empty.

(And there are issues with Tiny Portal compatibility in particular but that would not give you this issue)

[DarkAngel612]

And as has now been stated a number of times, the 2.0.7 packages were all withdrawn because we found some late breaking issues which are currently in the process of being dealt with. Not surprising that the packages are empty.

(And there are issues with Tiny Portal compatibility in particular but that would not give you this issue)

If directed to me I am aware of this, I just added my list to help the ones that are working on this item. Not to rush people but to hopefully help a bit.

[CMOBOSS_OLD]

Wouldn't it be far more logical to broadcast the fact that there is an update that is necessary, but that update is not yet ready for distribution?

Rather than have people attempting to update only to come here and find out after all that fuss to update: that the update is not actually ready? I mean... that to me seems like a pretty simple way to save a lot of people the headache of trying to update with no possible hope of doing so successfully.

Just sayin...

[Arantor]

Because the problems with the update weren't discovered until most of the notices had already gone out. Also without wishing to feel any more bad about the problem, it's really not actually as simple as you make out. Aside from the small details of the emails that had already gone out before the patch was found to have issues, SMF automatically updates itself with the details of the current patch pulled from the servers here... and we can't fix THAT without screwing many more things up.

How would you feel if you were the one responsible for this by signing off on code that you thought was OK but wasn't because you had already spent a lot of hours testing and missed a few missing characters out of tens of thousands? And then, to compound it, were actually asleep when it all went down, only to wake up and know you'd have to wait hours before you could actually do anything useful about it? Yeah. I screwed up. Thanks for reminding me how much I fail.

[DarkAngel612]

I personally am not pointing fingers at anyone...god I wish I could code too instead of copy/paste code given to me to fix things. I understand your predicament and wish you luck in squashing the bugs...love your tagline under you ava.

[Illori]

locked for further information check http://www.simplemachines.org/community/index.php?topic=517205

[Kindred]

Hey, Arantor...   as PM I signed off on it too....
I'm also the one who confirmed that CoreISP should pull the update when we realized it was bad.

So, if anyone wants to play the blame game... come see me first (but I hope you are wearing your fireproof underwear if you do...)

[kat]

****** happens.

Nobody's died.

It'll soon get fixed.

Tsk...