I'm trying to update my forum from 2.0.15 but 2.0.16 lists numerous failures and the large update fails to upload.
2.0.16:
QuoteError in Package Installation
At least one error was encountered during a test installation of this package. It is strongly recommended that you do not continue with installation unless you know what you are doing, and have made a backup very recently. This error may be caused by a conflict between the package you're trying to install and another package you have already installed, an error in the package, a package which requires another package that you don't have installed yet, or a package designed for another version of SMF.
2.1.4 Large Update
QuotePackage upload failed due to the following error:
"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 tried all the suggestions in the error notice.
Is this a known issue?
You cannot upgrade from 2.0 to 2.1 using package manager.
https://wiki.simplemachines.org/smf/Upgrading
Quote from: Kestryll on May 24, 2024, 06:07:57 PMI'm trying to update my forum from 2.0.15 but 2.0.16 lists numerous failures and the large update fails to upload.
Are you trying to update your forum to 2.0.16 or 2.1.4.? It' a bit unclear. To update to a subsequent version you can do it through the Package manager in your Acp. i.e. going from 2.0.15 to 2.0.16 and up to 2.0.19. Whereas large upgrades such as going from 2.0.x to 2.1.x as mentioned above, are best done manually.
The OP is trying either/both.
Failures in the update oackage/mod are just like a mod. If it can't find and exact match to the target code, it can't apply the update.
Just like a mod, that means that you would have to manually apply the code updates, taking into account changes that may have been done by mods
Alternatively, do the full upgrade per the link given above
IIRC, weren't some people experiencing errors (including me) in upgrading from 2.0.15 to 2.0.16 and all it was was a year problem that could easily be manually fixed? My memory not so good anymore.
As the OP has been here after my last post without further input, marking this paused/abandoned.