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

do not touch database if not asked when choosing ezdemo_site_clean package #43

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

crevillo
Copy link
Contributor

@crevillo crevillo commented Oct 1, 2017

This pull request tries to solve a problem when installing legacy bridge on top of ezplatform and you select ezdemo_site_clean as package.

When executing the setup there is a step asking you what to do with the database. One of the options is ' Leave the data and do nothing, but when ezdemo_site_clean is choosen, this is not honoured and the installer tries to execute some sql scripts. t

As those scripts try to create tables and indexes that are already in the db, it fails and installation cannot end.

The patch is the same as e11f15c

Funnily enough, git blame says i am the creator of that patch but i didn't rememeber it ☺️

Let me know if you want me to create a ticket for this or is this pr is enough.

@crevillo crevillo changed the title do not touch database if not asked do not touch database if not asked when choosing ezdemo_site_clean package Oct 1, 2017
@crevillo crevillo force-pushed the donot-touch-db-if-asked branch from 038a0d5 to 9f5ef97 Compare October 1, 2017 11:48
@crevillo
Copy link
Contributor Author

crevillo commented Oct 3, 2017

ping @bdunogier @andrerom
p.s. should i ping other people if i p.r to this repo? thanks.

@andrerom
Copy link
Contributor

andrerom commented Oct 3, 2017

p.s. should i ping other people if i p.r to this repo? thanks.

afaik no, as this repo is kind of not maintained atm, it could be if someone wants to. But for new projects you ideally should rather use platform installers, and somehow generate legacy config if you still rely on legacy for admin part (which imo is not needed anymore for 99% of projects next year with v2, but that another discussion)

There is POC PR on legacy bridge for exposing legacy friendly clean install option (swap RichText content for XMLText basically). This needs some cleanup, but once that is done this install could also for instance generate legacy config based on what has been configured in platform, afaik @emodric has some raw twig based templates for legacy settings that can be used as basis for something like this.

@crevillo
Copy link
Contributor Author

crevillo commented Oct 3, 2017

ok, good to know. yeah, our plan is avoid legacy if possible. this was merely a test i was doing and i find that issue.

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

Successfully merging this pull request may close these issues.

2 participants