-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid serial number for shell descriptor #16019
Comments
This looks like a bug indeed, so your workaround is what you need to do currently. Declaring dependencies in your module's manifest is recommended anyway if your module indeed depends on them. |
This was referenced Jun 1, 2024
The same error for me on v2.0.2.
|
I'm on 2.0.2 and I'm currently getting this error also |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I get an "Invalid serial number for shell descriptor" error if I have a module with two data migrations, and each migration executes a recipe with a "Feature" step. Example from DataMigration class:
Both recipes ("0001_migration.json" and "0002_migration.json") contain a "Feature" step that is meant to ensure certain core features are activated. If both of these migrations run back-to-back, which would happen when activating the feature for the first time, I get this error when the second recipe runs:
Works fine if I just have the one recipe run.
I'm running on OC 1.8.2. Is there something I'm doing wrong here? Other than abandoning the use of the RecipeMigrator to activate features, is there a way to make this work?
Thank you.
UPDATE: As a work-around for this issue I declared all the features I want activated as dependencies of my module. Orchard activates them automatically, meaning I don't need a migration recipe step. Adding additional dependencies after the feature is activated also seems to work fine, as Orchard will pick up on those and activate them. This meets my need at present, but the original issue presented seems to stand.
The text was updated successfully, but these errors were encountered: