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

Missing Glossary Element für [language] leads to Exceptions #5

Open
keinvorbild opened this issue Jul 24, 2018 · 2 comments
Open

Missing Glossary Element für [language] leads to Exceptions #5

keinvorbild opened this issue Jul 24, 2018 · 2 comments

Comments

@keinvorbild
Copy link

Issue started with migration to typo3 8 and produced an empty-array-exception when viewing english pages. THe issue was fixed by adding a single Dummy glossary Element in english.
Up to date the glossary was and is not used on the few english pages. I am not sure why this is happening, but i guess it should not be this way.

Reproducable: yes
Wanted behaviour: No exception on [language] pages, even if no Glossary Elements of [language] exist.

@rnakielski
Copy link

the same happens when there was no storage set in the constants. Array was not initialized in frontend Hook.

/**
   * function that does the DB calls to fetch all glossary entries
   *
   * @param string $pidList idlists set by configuraion
   * @return array glossary items
   */
  protected function fetchGlossaryItems($pidList): array
  {

When there was no storage Found (or for other reasons) the function returns null and not an array.

@sypets
Copy link

sypets commented May 23, 2019

The array $items did not get initialized in the fetchGlossaryItems() function in the release version (from TER).

It looks like this problem is already fixed in the latest version here in "master" branch.

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

No branches or pull requests

3 participants