Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.


If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping


Answers may be delayed for posts that do not include sufficient information.

Upgrade Collective Access from version 1.4.0 to version 1.7.8

Hi,
we are using the production version of Collective Access
Application version 1.4.
Schema revision 96
Release type GIT
We would like to realize upgrade to Application version 1.7.8

When I looked into the table ca_schema_updates, I saw, that there is the last update 103 but the update *.sql 1, 2, 3, 4, 5, 6, 87, 98, 101, 102 was not accomplished.

Should we do manually the application of missing update *.sql 1, 2, 3, 4, 5, 6, 87, 98, 101, 102 from /support/sql/migration/ and after that realize the upgrade to the new version 1.7.8?

Could you tell me please, what is the recommanding procedure of upgrade to the highist Application version 1.7.8?

ca_schema_updates
Modify version_num datetime
edit 7 1261071214
edit 8 1266001584
edit 9 1266001594
edit 10 1266001598
edit 11 1266001602
edit 12 1271862575
edit 13 1271862710
edit 14 1271862714
edit 15 1291565075
edit 16 1291565126
edit 17 1291565157
edit 18 1291566019
edit 19 1291566770
edit 20 1291566774
edit 21 1291566778
edit 22 1291566781
edit 23 1291566841
edit 24 1291567148
edit 25 1291567177
edit 26 1291567287
edit 27 1291567415
edit 28 1291567422
edit 29 1291567427
edit 30 1291567463
edit 31 1291567469
edit 32 1300563236
edit 33 1300563240
edit 34 1300563326
edit 35 1300563355
edit 36 1301256657
edit 37 1302732000
edit 38 1302732003
edit 39 1310501848
edit 40 1310501853
edit 41 1310501857
edit 42 1310502217
edit 43 1315604123
edit 44 1315604331
edit 45 1315605553
edit 46 1315605592
edit 47 1323559164
edit 48 1323560136
edit 49 1323560241
edit 50 1325794057
edit 51 1327446865
edit 52 1327446889
edit 53 1327446910
edit 54 1332359487
edit 55 1332359560
edit 56 1332359572
edit 57 1332359956
edit 58 1344541069
edit 59 1344541370
edit 60 1344541382
edit 61 1344541397
edit 62 1344541411
edit 63 1344541436
edit 64 1344541448
edit 65 1344541459
edit 66 1344541471
edit 67 1348784950
edit 68 1348784967
edit 69 1393629131
edit 70 1393629140
edit 71 1393629141
edit 72 1393629142
edit 73 1393629143
edit 74 1393689191
edit 75 1393689192
edit 76 1393689198
edit 77 1393689198
edit 78 1393689269
edit 79 1393689272
edit 80 1393689272
edit 81 1393689279
edit 82 1393715232
edit 83 1393737656
edit 84 1393737658
edit 85 1393737663
edit 86 1393737669
edit 88 1393737688
edit 89 1393737688
edit 90 1393737711
edit 91 1393737714
edit 92 1393737714
edit 93 1393737717
edit 94 1393737717
edit 95 1393737718
edit 96 1393737730
edit 97 1464360445
edit 99 1464360914
edit 100 1464361153
edit 103 1464361288

Thanks a lot for your advise and your quick answer it_admins_ca_jmp

Comments

  • You should just run the normal update process. Do not run anything earlier than 103. Your system is very very old and had a fair amount of "experimental" work done on it by Michal :-) I'm sure we skipped some migrations for good reason back in the old days.

    It will probably update normally, but the older you go the more likely some handwork may be required. The oldest we've updated to 1.7.8 in one go without a problem was a 1.5 system. We've also done a bunch of 0.6 systems, which required a bit of handwork to update, but worked out fine in the end. I can say for sure that it will be possible to move your data to 1.7.8. Whether it's automatic or takes an hour of work is the question.

    seth

  • Hello it_admins_ca_jmp,
    I'm having some trouble going from 1.4 to 1.7.8. too. Did the update work automatically for you?
    David

  • If either of you run into errors contact me at seth@collectiveaccess.org and I'll help you sort it out.

Sign In or Register to comment.