Skip to content
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

Issue #3485: Add options_element in backdrop_merged_modules() #2564

Merged
merged 7 commits into from
Apr 10, 2019

Conversation

klonos
Copy link
Member

@klonos klonos commented Apr 2, 2019

@backdrop-ci
Copy link
Collaborator

Related to: backdrop/backdrop-issues#3485

@backdrop-ci
Copy link
Collaborator

Website: http://2564.backdrop.backdrop.qa.backdropcms.org
Username: admin
Password: UcckEf6b

@herbdool
Copy link
Contributor

herbdool commented Apr 2, 2019

@klonos this part of PR looks good but you also need a hook update in system.install with db_query to disable the old options_element module if it exists.

@klonos
Copy link
Member Author

klonos commented Apr 2, 2019

Hey @herbdool, I have updated the PR, but went with file.install instead of system.install, since the PR for backdrop/backdrop-issues#1005 changed the Field module.

core/modules/field/field.install Outdated Show resolved Hide resolved
@quicksketch quicksketch merged commit 45032cb into backdrop:1.x Apr 10, 2019
@backdrop-ci
Copy link
Collaborator

Website: http://2564.backdrop.backdrop.qa.backdropcms.org Removed

@quicksketch
Copy link
Member

Thanks! Merged into 1.x and 1.12.x.

// While the contrib module remains in the filesystem, this entry will be
// recreated, but it will have status 0 (disabled), and schema -1
// (uninstalled), so it is safe to remove.
db_query("DELETE FROM {system} WHERE name = 'options_element' AND type = 'module'");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not calling module_disable here ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

module_disable() would call options_element_disable(), as well as allowing other modules to perform uninstall actions. Since we're replacing Options Element with an equivalent, we don't want any modules to react to the change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair enough ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants