Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: Migration problems from 2.6x

Migration problems from 2.6x 13 years 9 months ago #12766

  • quarterstaff
  • quarterstaff's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 11
  • Thank you received: 0
I recently upgraded from 2.6.8e to 2.7.3c (using the most current download) and several user related fields have not migrated properly:

- Registered events are mostly incorrect - it appears to just to be randomly picking events to migrate. Most other information is correct - transaction ID, confirmation number, status, etc, so it should be possible to manually update the events that the users have registered for (hundreds of records), but not a task I'm looking forward to. Which brings up another, bigger problem:

- The process also seems to randomly decide whether or not to migrate some user fields - such as the user's first name, which is just a standard text field. This one will be more difficult to repair manually - for the records where the first name did not transfer, there appears to be nowhere to manually add it. Going into the records, if the users first name did not migrate, the first name field does not even appear. Other fields that did not migrate correctly (ie are just left blank) do appear as editable fields. The fields that seem to be migrated with random information include The Payment Type, State/Province (chosen with a dropdown list), and phone number

- This is a much bigger issue - if I go into the records to update the event, if the first name field is not shown (and actually in come cases the first name is in the database, but chooses to not show on the record editing page, but does show on the main records list page) as soon as I save the record, the first name disappears from the database as well, and of course no longer shows on the main record page.

It also seems to be a crapshoot whether fields will appear on the Record details page - for some users it will show all information, for others it doesn't show such things as address, city, etc.

On a test server, I have tried using every possible upgrade variant - upgrade to 2.6.9 first, upgrade to 2.72 before upgrading to 2.7.3, unsync jevents or not, etc, etc, and every time the results are the same. Upgrading to 2.6.9 keeps the records intact, but as soon as I move to 2.7x the data is corrupted.

Has anyone else run into this?

Please Log in or Create an account to join the conversation.

Migration problems from 2.6x 13 years 9 months ago #12906

  • quarterstaff
  • quarterstaff's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 11
  • Thank you received: 0
Sorry, but I have to bump this. I tried again with the new 2.7.4 with no success, and discovered another big problem - the proper amounts are not being sent to PayPal. Along with the other random errors, the amount from a different event was sent to PayPal, and was then accepted by the system and registered the user in the event - an error in this case of over $500.

I opened a ticket a week ago on this issue, which so far remains unread. The only replies have been from me with updates on the problem.

Please Log in or Create an account to join the conversation.

Migration problems from 2.6x 13 years 9 months ago #12957

  • IRedsell
  • IRedsell's Avatar
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 15
  • Thank you received: 0
I too have a similar problem Jevents 1.5.5 and dtregister 2.6.6. to 2.6.9 to 2.7.4 the events migration has mixed up events and users. I have tried this in various configurations on the test server and each time I end up with users and events mixed up.

It was ok from 2.6.6 to 2.6.9 and then went west in the 2.7.4 records migration

Also the select events drop down seems to show random order, neither sorted in titel, date or as far as I can tell ID. It is therefore tricky to see if the events are pulled through properly

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.123 seconds