Request for Update Thread

[WB]

Michael P.:

Can you all keep a running 'update' thread about any updates made when the build information is kept the same? Unless I missed it in my search, I don't think one exists.

For example, the current build is:

PhotoPost PHP Pro, v4.86 (1/3/05 7:03 PM Build)

Other than the upgrade.php update that I mentioned in another thread, I think there's also been an update to some files referenced in '4.86 Patch did not included manually fixes..' in this forum.

Not sure if there are others but those appear to be the two that have been updated since the build date.

An example:

__

Current PhotoPost build:

PhotoPost PHP Pro, v4.86 (1/3/05 7:03 PM Build)

Updates made after 1/3/05, 7:03 PM:

1/4 - Updated upgrade.php.- Only needed if you were not able to upgrade from 4.8.2.

1/4 - Updated whicheverfileswereupdated.php to include manual fixes.

Please note that if you downloaded your build after said dates, you already have the updated files.

__


That would be *extremely* helpful so that we can have one place to check to make sure we have the latest updates when the build version doesn't change.

Thanks.

[Chuck S]

I think the announcement threads detail every changed file

http://www.photopost.com/members/for...d.php?t=111296

http://www.photopost.com/members/for....php?p=1084957

[WB]

omegatron:

Thanks for the response but I'm referring to files that have been updated since the build was made available, not what files have changed between versions.

According to various threads that I've run across there have been changes to the current build (but the build name and time remain the same).

For those customers like me who downloaded the build early on, there may be changes that we don't have with no way of finding all of said updates.

Thanks.

[Michael P]

I've made the comment several times in threads, but only post information about the updated files when I am comfortable that people who already have PhotoPost installed need to update their files. Anything before that could be premature; so its a balancing act between helping someone with a specific issue who doesn't feel comfortable modifying their code and posting a change that would cause thousands of people to feel they need to update their files at every change.

[WB]

Michael:

Thanks for the response. I understand and appreciate the need to balance.

I'm only requesting that the information be made available in one easy to find place. That way should any of us experience a specific issue, we can check that one thread and decide for ourselves if we want to update said files.

If you don't want to make the information generally available in the member forums, perhaps the thread could be cordoned off and access given per request. That would accomplish both goals since only those who are interested in keeping track of the changes would see the updates.

I think that there is a contingent of PhotoPost users that would very much like to see such information available.

Thanks.