Updating and Integrity Checker

[Colp]

I noticed today that the latest version is 2.3.2 so I updated from 2.3.1. All is well. I also updated PivotX Tools and ran the Integrity Checker as advised here. I don't have any of the hack files mentioned here, but I do have some unknown files.

Code: Select all

pivotx/error_log is unknown.
pivotx/includes/js/jquery-1.6.4.min.js is unknown.
pivotx/includes/js/jquery-ui-1.8.16.custom.min.js is unknown.
pivotx/editor_wysi/plugins/media/img/shockwave.gif is unknown.
pivotx/editor_wysi/plugins/media/img/realmedia.gif is unknown.
pivotx/editor_wysi/plugins/media/img/flash.gif is unknown.
pivotx/editor_wysi/plugins/media/img/trans.gif is unknown.
pivotx/editor_wysi/plugins/media/img/quicktime.gif is unknown.
pivotx/editor_wysi/plugins/media/img/windowsmedia.gif is unknown.
pivotx/editor_wysi/plugins/media/img/flv_player.swf is unknown.
pivotx/editor_wysi/plugins/media/css/content.css is unknown.
pivotx/templates_internal/ui-theme/jquery-ui-1.8.16.custom.css is unknown.
pivotx/advconfig.tpl is unknown.

I didn't put any of these files here but I assume that as I copied over the existing PivotX folders to update that these are files no longer used by the new version. (I didn't overwrite any of the files in the root folder (.htaccess etc) or the db, template, images and extensions folders)

Please can you confirm the best way to update (if that wasn't the best way) and if the above files can simply be removed?

Thanks

[Harm10]

If you upgrade you should also look at files that are no longer there (they won't be deleted out of their own...... ). There are several ways to do this (I always use Beyond Compare).

I didn't check all the files that are listed but those jquery files are replaced by new ones in the recent release. And those editor_wysi files are all not in my installation (any more) so I guess these were also used during previous versions.

So start comparing...............

[Colp]

Will do. Thanks.

[hansfn]

Unknown files should be deleted. These files are left-overs from older versions.

@Harm: Please don't tell everybody to start using "Beyond Compare" (or similar tools) to compare versions - that's for developers. It makes upgrading PivotX sound much harder than it really is. (We have been discussing this before.)

PS! There are "better" methods to upgrade PivotX than overwriting the old/existing installation, but they require 4-5 steps (in stead of one). There is a forum thread discussing this, but I don't have time to find it ...

[Harm10]

hansfn probably means this discussion.

As this is not the right place to go into discussion about to compare or not, I won't.

Perhaps this is the right time to ask the users whether they'd like to have detailed instructions on how to upgrade from version to version? Or how they can know whether a file has become obsolete? In the discussion I am pointing to there is mention of upgrade packages but I definitely think that's a bridge too far! (There is no easy way to know what version and/or installation you are upgrading from automatically; this is still open source....... )

So users..................?

[hansfn]

No, I did not mean that discussion at all. It doesn't contain all the steps involved in an upgrade where you don't overwrite the existing installation.

It seems the discussion took place on the dev mailing list and not in the forum. Slightly edited quote from one of the emails in that discussion:

To upgrade follow these steps:
1) Make a backup of your PivotX installation
2) Upload the "pivotx" folder of the new PivotX release as "pivotx_new" (Rename it before uploading.)
3) Set PivotX in offline mode
4) Remove the folder /pivotx_new/db
5) Move/rename /pivotx/db to /pivotx_new/db
6) Move any non-core themes from /pivotx/templates to /pivotx_new/templates
7) Move all extensions from /pivotx/templates to /pivotx_new/extensions (that aren't already present).
8) Rename /pivotx to /pivotx_old
9) Rename /pivotx_new to /pivotx
10) Set PivotX in online mode

This is clearly more work than just overwriting the files. Maybe overwriting and then running the integrity checker and cleaning up afterwards is a better approach?

PS! Yes, for people with shell access on their server, you can write a script that automates this work.

[Harm10]

This is clearly more work than just overwriting the files. Maybe overwriting and then running the integrity checker and cleaning up afterwards is a better approach?

It could be two fold (or maybe even more than that): put hansfn's working list in the documentation, perhaps give a sample for those that want to automate it and create a list with deleted files e.g. with Beyond Compare's orphan summary list. This list could be a text file that's added to the zip.
To give Colp a general idea about the files that were deleted from 2.2.x compared to 2.3.x:

Code: Select all

Folder Compare
Produced: 5-3-2012 10:47:13

Mode:  Right Orphans
Left base folder: ......edited.....svn-branches\2.3.x
Right base folder: ......edited.....svn-branches\2.2.x

Right Orphan Files                                             Size    Modified
-----------------------------------------------------------------------------------------
pivotx\db\blocked_ips.txt.php                                  253     25-6-2011 16:14:02
pivotx\db\ignored_domains.txt.php                              900     25-6-2011 16:14:02
pivotx\editor_wysi\plugins\media\css\content.css               530     25-6-2011 16:14:20
pivotx\editor_wysi\plugins\media\img\flash.gif                 241     25-6-2011 16:14:20
pivotx\editor_wysi\plugins\media\img\flv_player.swf            11.668  25-6-2011 16:14:20
pivotx\editor_wysi\plugins\media\img\quicktime.gif             303     25-6-2011 16:14:20
pivotx\editor_wysi\plugins\media\img\realmedia.gif             439     25-6-2011 16:14:20
pivotx\editor_wysi\plugins\media\img\shockwave.gif             387     25-6-2011 16:14:20
pivotx\editor_wysi\plugins\media\img\trans.gif                 43      25-6-2011 16:14:20
pivotx\editor_wysi\plugins\media\img\windowsmedia.gif          415     25-6-2011 16:14:20
pivotx\includes\js\jquery-1.6.2.min.js                         91.556  2-7-2011 16:06:59
pivotx\includes\js\jquery-ui-1.8.14.custom.min.js              145.050 2-7-2011 16:06:59
pivotx\templates_internal\ui-theme\jquery-ui-1.8.14.custom.css 28.197  2-7-2011 16:06:58
-----------------------------------------------------------------------------------------


[hansfn]

and create a list with deleted files e.g. with Beyond Compare's orphan summary list. This list could be a text file that's added to the zip.

Then you would have to make such a list for every possible upgrade path - example for Pivot 2.3.2 - ... 2.2.5 -> 2.3.2; 2.2.6 -> 2.3.2; 2.3.0 -> 2.3.2, 2.3.1 -> 2.3.2 - since people tend to skip some releases before upgrading.

PS! The list from Beyond Compare is very close to the "unknown" list from the integrity checker

[Harm10]

Then you would have to make such a list for every possible upgrade path - example for Pivot 2.3.2 - ... 2.2.5 -> 2.3.2; 2.2.6 -> 2.3.2; 2.3.0 -> 2.3.2, 2.3.1 -> 2.3.2 - since people tend to skip some releases before upgrading.

I know, but the packager of the official release can create such a list compared to the previous official release. People can look at these list or lists depending on what version to upgrade from and decide what files can be deleted (or can be considered OK when checking integrity). Such a list is very easy created and can be considered an extra service to our users............. Idea?

[hansfn]

No, I don't think it's a good idea. (And it's not enough with one list comparing to the previous release for the reason I stated.) We have a hard enough time doing what we do now - any added operation is unwanted. You are of course free to do it - as always