Bug 2151564 - Content view in French/Italian language doesn't show
Summary: Content view in French/Italian language doesn't show
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.12.0
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: 6.13.0
Assignee: Maria
QA Contact: Lucy Fu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-07 14:02 UTC by Giovanni Formisano
Modified: 2023-02-11 15:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35329 0 Normal Closed useTableSort should translate initialSortColumnName 2022-12-21 16:50:11 UTC
Red Hat Issue Tracker SAT-14660 0 None None None 2023-01-04 23:09:43 UTC

Description Giovanni Formisano 2022-12-07 14:02:01 UTC 
Description of problem:
If you change the language, selected the French one, and go to Content -> Content View it's not possible read the content view page, actually show up a blank page.
I have also try with the Italian language and there is the same problem.

Version-Release number of selected component (if applicable):
Sat 6.12

How reproducible:
100%

Steps to Reproduce:
1.Login inside Sat 6.12 click Account - > My account -> change the Language parameter

Actual results:
Content View page it's a blank page

Expected results:
Should comes up the Content View created or possibility to create the new one

Additional info:
Comment 3 Jeremy Lenz 2022-12-21 16:50:11 UTC 
I think this is happening because https://projects.theforeman.org/issues/35329 wasn't backported to 6.12. Including that should fix it.
Comment 4 Pavel Moravec 2022-12-21 19:33:33 UTC 
Ah I see, thanks for prompt feedback!
Comment 7 Lucy Fu 2023-01-10 20:16:42 UTC 
Fixed in 6.13 but still exists in 6.12.
Added screenshot of the content view page.
Note You need to log in before you can comment on or make changes to this bug.