Skip to main content
Topic: ElkArte 1.0.5 - Release announcement (Read 7634 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: ElkArte 1.0.5 - Release announcement

Reply #15
@Spuds ,

Successfully updated. Thanks

Quote
Version Information:
This version: ElkArte 1.0.5
Current version: 1.0.5 bug fix update
(more detailed)

Re: ElkArte 1.0.5 - Release announcement

Reply #16
Congrats everyone, great work :D

Re: ElkArte 1.0.5 - Release announcement

Reply #17
Awesome!

Re: ElkArte 1.0.5 - Release announcement

Reply #18
Congrats :)

 

Re: ElkArte 1.0.5 - Release announcement

Reply #19
great release.

Re: ElkArte 1.0.5 - Release announcement

Reply #20
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
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.
Be safe, Be kind, Happy Programing

Re: ElkArte 1.0.5 - Release announcement

Reply #22
Installed the patch in two boards and both show 1.0.4 in their footer.  :o

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!"  :-X  >:(  :-X

Re: ElkArte 1.0.5 - Release announcement

Reply #23
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
Bugs creator.
Features destroyer.
Template killer.

Re: ElkArte 1.0.5 - Release announcement

Reply #24
I can provide full access if you want to examine this situation?

Re: ElkArte 1.0.5 - Release announcement

Reply #25
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... :-[
Bugs creator.
Features destroyer.
Template killer.