Re: ElkArte 1.0.5 - Release announcement Reply #15 – September 14, 2015, 06:56:13 am @Spuds ,Successfully updated. ThanksQuoteVersion Information:This version: ElkArte 1.0.5Current version: 1.0.5 bug fix update(more detailed)
Re: ElkArte 1.0.5 - Release announcement Reply #16 – September 14, 2015, 06:57:24 am Congrats everyone, great work
Re: ElkArte 1.0.5 - Release announcement Reply #20 – September 29, 2015, 05:50:22 am I am getting the following error when trying to update from 1.0.4 to 1.0.5.Trying the second option, packages directory is writeable, sub folder temp does not exist?
Re: ElkArte 1.0.5 - Release announcement Reply #21 – September 29, 2015, 12:44:19 pm Try creating the temp directory inside the packages directory and see if that fixes the issue. The system should do that automatically but perhaps there is a permissions issue. Once created try the package install again.
Re: ElkArte 1.0.5 - Release announcement Reply #22 – October 07, 2015, 11:39:54 am Installed the patch in two boards and both show 1.0.4 in their footer. Oh, I checked the version number in SSI.php right at the top. It seems I have the same problem I had with SMF. It seems the package manager couldn't change the files but says: "patch installed, all good!"
Re: ElkArte 1.0.5 - Release announcement Reply #23 – October 07, 2015, 02:19:00 pm Not unlikely, though it's always odd to think that you updated since 1.0.4 without problems and then the problem appear... Anyway I tracked that one a while ago, though not being sure the "fix" is right, I postponed it.https://github.com/elkarte/Elkarte/issues/1463
Re: ElkArte 1.0.5 - Release announcement Reply #24 – October 08, 2015, 01:53:01 am I can provide full access if you want to examine this situation?
Re: ElkArte 1.0.5 - Release announcement Reply #25 – October 08, 2015, 02:30:51 pm Honestly, I wouldn't know what to look for.I think I know the problem (i.e. when files are not writable the package manager doesn't return an error and goes on without doing anything), but I'm pretty sure I wouldn't be able to find out why files switch from writable to non-writable...