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

When building with --destroy, the ES index is not rebuilt #198

Closed
Swader opened this issue Jun 15, 2017 · 1 comment · Fixed by #211
Closed

When building with --destroy, the ES index is not rebuilt #198

Swader opened this issue Jun 15, 2017 · 1 comment · Fixed by #211
Milestone

Comments

@Swader
Copy link
Contributor

Swader commented Jun 15, 2017

Q A
Bug? yes
New Feature? no
SuluArticleBundle Version All
Sulu Version All

Actual Behavior

If you execute bin/adminconsole sulu:build --destroy, the ES index remains. This leaves behind artifacts in /admin which lead to non-existing articles.

screenshot 2017-06-15 11 58 39

Expected Behavior

If the database is destroyed its indexes should be, too.

Steps to Reproduce

  • Have articles.
  • Issue a rebuild with destroy.
  • Notice orphaned links in /admin.

Possible Solutions

Extend the sulu:build command to execute a recreation of the index if --destroy was passed in.

@wachterjohannes wachterjohannes added this to the 1.0.0 milestone Jun 16, 2017
@wachterjohannes
Copy link
Member

I can confirm this issue. We have to add a new ArticleIndexBuilder which will be called in this case.

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 a pull request may close this issue.

2 participants