search

sulu / SuluArticleBundle

Bundle for managing localized content-rich entities like blog-posts in the Sulu content management system
MIT License
57 stars 80 forks source link

Different language articles in Italian smart content #379

Open tislars opened 6 years ago

tislars commented 6 years ago
Q A
Bug? yes
New Feature? no
Sulu Version 1.6.2 (c0c04cd95ea6e4ef9a514d1b8ceb4742003c610b)
Browser Version Google Chrome Version 69.0.3497.100 (Official Build) (64-bit)

Actual Behavior

All articles are visible in the smart content block, despite different languages. screen shot 2018-10-17 at 09 00 30 screen shot 2018-10-17 at 09 00 48

Expected Behavior

I expect that the English articles are not visible in the smart content block on the Italian environment.

Steps to Reproduce

Start up a Sulu (version 1.6.2) environment with the sulu-article-bundle (1.0.0-RC7) Create a Sulu webspace with multiple locales, e.g. English and Italian, and create articles in both languages. Go to a page with smart content and observe the result.

danrot commented 6 years ago

Is this only happening for articles? Or do you experience the same wrong behavior with the smart content for pages as well?

tislars commented 5 years ago

@danrot I apologise for the late response. However, this only occurs with articles on my end as far as I can see.

alexander-schranz commented 5 years ago

@TisLars @danrot As it seems to be an Article Bundle issue I transfered this to the correct repository. /cc @wachterjohannes

alexander-schranz commented 5 years ago

@TisLars when reading the changelog there where some fixes in for ghost and shadow article behaviour in the 1.0 Release can you check if your error does also appear in the current 1.0.1 release?

tislars commented 5 years ago

@alexander-schranz In the meantime we are already running version 1.0.1. The problem also occurs in that version.

gisostallenberg commented 5 years ago

When publishing an article in one language the ArticleGhostIndexer also indexes, resulting in the article being in indexes of other languages, resulting in the article being available in smart content of the wrong language (presented with the locale of that language). I understood this should be indexed in the admin index only, see image