Potential RC 5 Now Available

[David]

I wanted to let you know that I added Release Candidate 5 to the Downloads section. All of the WebSVN releases have proved to be at least as stable as RC 4, so I'm calling this one the latest stable release. It includes pagination of links in the category pages, and makes the ID tag optional for reciprocal links. If you have time, it would be appreciated if you could test it on your system, and let us know if you hit any snags. I have already installed this release on a couple of sites and it is working to my satisfaction.

If you want to wait until we make the Final Release of 2.0, I would estimate we are 2-4 weeks away still (though please don't hold me to that).

Thanks,
David

[ksbhati]

Hi David,

There seems to be some error in your download link. You may like to check it out....! I am getting the following error message on the Download page.

Content visible to registered users only.

regards,

Karni

[MSM]

Would like to download the newest version, but there seems to be an error with your database or else......

please be so kind to fix the download link to RC5

thx,
Mike

[David]

Ok, sorry about that...the file is now in place.

[David]

RC 5.2 is now added to the Downloads section. :)
Note: We tend to have a new release at least every week, so don't feel inclined to update your script every time. We will have more updates coming soon, including the addition of an Editor's mod and an @links mod.

[vkaryl]

Li'l suggestion: I know it's extra work, but a changed-files log in the distro would be really nice....

[Ap0s7le]

Oh stinkin' thing... I meant to do that, with a list of current files.

Geesh!!!

I'm leaving, if I'm not heard from again it was natural causes LOL!

-Casey

[latino]

Hi:

Content visible to registered users only.

Any time estimate for the release of v2? The addition of editors is a major feature so congratulations for that.

Later

:wink:

[David]

Content visible to registered users only.

Any time estimate for the release of v2? The addition of editors is a major feature so congratulations for that.

Later

:wink:[/quote]

Hi Latino,

Since we are starting to look pretty stable now, we may elect to just remove the RC and start calling the releases 2.05.2
I have been hesitant to do this without dcb who was on his honeymoon, and who wrote a very large percentage of the code. The WebSVN (where the development version is stored) will continue to be updates, and then periodically we will add downloads to the downloads section.

[kservik]

Are there any upgrade instructions?

Kim

[Mike77]

Many of us have our designs in our directories so it is really hard to update it. Also if you install any mods or do some modifications it is relly easy to screw entire script.

We cant mess with the actual script and expect everything to work with new updates - I underand this. But what about design? I added a few things in header and footer (tpl) and also placed entire "directory"in table (so i can resize directory) so when I updated to latest release (not 5.2 that came out yesterday) my design was of course lost(which is normal of course since the files were overwritten :) ). Then I just copied the custom header,footer.tpl files and then it really messed up entire design. So I had to manualy add design code which took me 1 hour. Now there is another update and I am afriad that it will mess up my design again.

that is why i think we would need detailed info on what changed and which files etc on every new release. One problem can also be when we add something on php files for example and then with new update this php file is changed and we do not know this and just upload the old modified php file and then of course things are missing and script is not working. As i said I only uploaded my old tpl header and footer and this not only messed up my design - also the new pagination stoped working. Now I manually step by step copied custom design code an it is ok now. However when I go to second or third etc page of some category and then click on small XML pic I get this error:

http://erogs.com/list/rss.php?p=2

I do not know if this is bug of the new release or something that came out when I changed tpl files.

So what I am saying is that now,that directory is getting new and new features , we should think about some better way to apply all those updates than just overwritting everything. (Also documenting everything , no matter how time consuming it is, should be priority). Is it posible for example to issue two different packlages - one for new instalations (all files) and one just updates from LAST version? That way we could see what files are changed and also we would only need to update few files instead of entire directory.

Also I would like to ask what is the easiest way to keep or import your design to new release? Should i join them all and then edit all in dreamweaver. How do you people bring back entire design after you upgraded everything?

Maybe it is just me that has these problems - did anyone have any design or funcionality problems when upgrading to latest version? :)

[Nobody]

I totally agree. I'm lost with all these confusing new releases with no detailed information attached what so ever.

[vkaryl]

Here's what I did to upgrade my local install (and I see no reason why the web install shouldn't follow the pattern):

I set up RC5.2 in a new folder. I copied main.css and /templates/ from the working install of RC5 into RC5.2, overwriting the same file and folder. I copied the mods out of RC5 index.php into RC5.2.

It's fine. It worked first time OOB. No glitches at all. So now I'm going to upload (which I admit IS a pain, due to me only having dial-up *sigh*).

[Edit: one thing that would make this less painful for me personally would be if you could note whether anything changed in the Smarty libs folder - that sucker is over 2.5 meg.... takes FOREVER to upload on dial-up!]

[kickass]

You should always have your template mods and css file mods backed up on your hard drive, so that if anything gets screwed up during an upgrade you can just upload your mods and overwrite the "screwed up" files with your nicely backed up version. It's also always a good idea, just for safety's sake, to back up you database before upgrades. If this had been done you'd be in an easier position to fix things, just a minute or two to upload the template and css and/or the dbase.

Re the upgrade file suggestion versus complete install- David and Casey, I think this is a VERY good idea. It's been one of the headaches with another piece of software I use that requires frequent updates is that you have to search high and low for a changefile list if you want to do the upgrade that way. We should make this available to the community either as a separate file download OR as a list so people can choose to just update changed files.

[vkaryl]

Content visible to registered users only.

Aye that! I'm another user of "that" software....

[Ap0s7le]

CHANGELOG shall come one way or another, I tell ya it will :)

Normally we have the WebSVN, which has all this built in so you know what files were changed, and can see what they were etc.

If that doesn't get fixed soon we'll stick with a normal changelog.

Thanks

-Casey

[David]

Hi there, once we get WebSVN running again, you will have a ready reference of changed files.