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

scrum-1195: Set menu structure. #133

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

scrum-1195: Set menu structure. #133

wants to merge 1 commit into from

Conversation

thet
Copy link
Member

@thet thet commented May 10, 2023

This commit sets the recensio portal tabs menu explicitly via actions.xml which was apparently set manually before.

Also, it adds these Documents:

  • /rezensionen/rezensionen (for German)
  • /rezensionen/reviews (for English)
  • /rezensionen/recensions‌ (for French)

to reflect the old URL structure on https://www.recensio.net/

All of those Documents are set to have the layout "latest-review-items"

This solves scrum-1195.

However, I'm not 100% sold on this.

Some problems I see:

  • Having content items just to reflect the old URL structure without any other purpose feels odd.
  • This is not using any translation machinery, so switching from fr to de wouldn't switch from /rezensionen/recensions‌ to /rezensionen/rezensionen.

I'm not sure if there is a better solution. I'm open to suggestions.

<property name="description"
i18n:translate=""
/>
<property name="url_expr">string:${portal/rezensionen/absolute_url}/rezensionen</property>
Copy link
Member

@ale-rt ale-rt May 11, 2023

Choose a reason for hiding this comment

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

I see this contains rezensionen a couple of times.
Does it make sense to change it to:

Suggested change
<property name="url_expr">string:${portal/rezensionen/absolute_url}/rezensionen</property>
<property name="url_expr">portal/rezensionen/rezensionen/absolute_url</property>

?

Copy link
Member Author

Choose a reason for hiding this comment

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

Shouldn't it rather be string:${portal_url}/rezensionen/rezensionen ?

Copy link
Member

Choose a reason for hiding this comment

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

I was proposing that form because you had in your original PR portal/rezensionen/absolute_url.
Do whatever you like, but be consistent.
Or just don't be and ignore this nitpicky comment

Copy link
Member Author

Choose a reason for hiding this comment

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

${portal/rezensionen/absolute_url} was from the actions.xml export I did on the testing database from https://recensio50.fe.rzob.gocept.net/
But actually I didn't understand whey it was constructing the URL like that.

<property name="description"
i18n:translate=""
/>
<property name="url_expr">string:${portal_url}/ueber-uns</property>
Copy link
Member

Choose a reason for hiding this comment

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

Will this work:

Suggested change
<property name="url_expr">string:${portal_url}/ueber-uns</property>
<property name="url_expr">portal/ueber-uns/absolute_url</property>

?

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think so - we do need ${portal_url}, no?

Copy link
Member

@ale-rt ale-rt left a comment

Choose a reason for hiding this comment

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

I see you are creating content.
Did you think about how this will impact the migration process?

@thet
Copy link
Member Author

thet commented May 11, 2023

Did not much think about the migration process except that I‌ think it would skip existing items.

But I'm not convinced about this PR myself.

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.

2 participants