I’ve tried upgrading Meteor from 2.2.3 to 2.3.5 and noticed that I’m getting errors when inserting data from our seed data XLS spreadsheet:
Error: module is not allowed by the schema at getErrorObject (packages\aldeed_collection2-core.js:480:15) at ns.Collection.doValidate (packages\aldeed_collection2-core.js:462:13) at ns.Collection.Mongo.Collection.<computed> [as update] (packages\aldeed_collection2-core.js:214:25) at ns.Collection.Mongo.Collection.<computed> [as update] (packages\babrahams_transactions.js:1047:16) at OptionsObject.update (lib/options.js:32:32) at Object.readSeedDataFile.InsertIntoOptions (server/readSeedDataFile.js:373:17) at FetchSeedData (server/main.js:358:26) at server/main.js:18:3
The XLS workbook which is read into a Options collection:
module fieldName fieldValue Feature Subscription 1 Feature ClearServerSession 1 Feature Caching 1 Feature ClearLegacyDocuments 0
This has all been working fine for several years.
I’m thinking it could be to do with the downgrade to babrahams:transactions or dburles:mongo-collection-instances? There’s a lot of junk in this inherited project and I potentially want to get around rewriting massive chucks of transaction code and schema definitions to get to 2.3.5+ if those are the culprit.
Is there a way to prevent packages from being downgraded?
Here is the upgrade message:
meteor update --release 2.3.5 Changes to your project's package version selections from updating the release: accounts-base* upgraded from 1.9.0 to 2.0.1 accounts-password* upgraded from 1.7.0 to 2.0.1 babrahams:transactions downgraded from 0.8.10 to 0.6.7 blaze upgraded from 2.4.0 to 2.5.0 callback-hook upgraded from 1.3.0 to 1.3.1 dburles:mongo-collection-instances downgraded from 0.3.5 to 0.3.1 ddp-client upgraded from 2.4.0 to 2.5.0 ddp-rate-limiter upgraded from 1.0.9 to 1.1.0 ddp-server upgraded from 2.3.3 to 2.4.0 dynamic-import upgraded from 0.6.0 to 0.7.1 ecmascript-runtime-client upgraded from 0.11.0 to 0.11.1 ecmascript-runtime-server upgraded from 0.10.0 to 0.10.1 email upgraded from 2.0.0 to 2.1.1 fourseven:scss upgraded from 4.12.0 to 4.15.0 id-map upgraded from 1.1.0 to 1.1.1 iron:controller added, version 1.0.12 iron:core added, version 1.0.11 iron:dynamic-template added, version 1.0.12 iron:layout added, version 1.0.12 iron:location added, version 1.0.11 iron:middleware-stack added, version 1.0.11 iron:router added, version 1.0.12 iron:url added, version 1.0.11 lai:collection-extensions removed from your project lamhieu:meteorx removed from your project lamhieu:unblock removed from your project launch-screen upgraded from 1.2.1 to 1.3.0 matb33:collection-hooks upgraded from 1.0.1 to 1.1.0 meteor-base upgraded from 1.4.0 to 1.5.1 minifier-css upgraded from 1.5.3 to 1.5.4 minifier-js upgraded from 2.6.0 to 2.6.1 minimongo upgraded from 1.6.2 to 1.7.0 mizzao:user-status upgraded from 1.0.0 to 1.0.1 mongo upgraded from 1.11.0 to 1.12.0 mongo-id upgraded from 1.0.7 to 1.0.8 montiapm:agent removed from your project montiapm:agent-binary-deps removed from your project montiapm:meteorx removed from your project montiapm:profiler removed from your project nimble:restivus downgraded from 0.8.12 to 0.6.6 npm-bcrypt removed from your project npm-mongo upgraded from 3.9.0 to 3.9.1 promise upgraded from 0.11.2 to 0.12.0 react-fast-refresh upgraded from 0.1.0 to 0.1.1 routepolicy upgraded from 1.1.0 to 1.1.1 service-configuration upgraded from 1.0.11 to 1.1.0 socialize:server-time removed from your project socket-stream-client upgraded from 0.3.2 to 0.4.0 spacebars upgraded from 1.1.0 to 1.2.0 srp removed from your project standard-minifier-css upgraded from 1.7.2 to 1.7.3 standard-minifier-js upgraded from 2.6.0 to 2.6.1 templating upgraded from 1.4.0 to 1.4.1 templating-compiler upgraded from 1.4.0 to 1.4.1 templating-runtime upgraded from 1.4.0 to 1.5.0 url upgraded from 1.3.1 to 1.3.2 webapp upgraded from 1.10.1 to 1.11.1 zodern:meteor-package-versions removed from your project
Any thoughts would be appreciated.