Open michaaa opened 1 year ago
@michaaa Please provide us the version of Znuny, Znuny-Search and Znuny-SearchFrontend
Sorry, I forgot to mention:
Znuny 6.5.4 LTS, however there was same result under 6.5.3 LTS
Znuny-Search 6.5.1 Znuny-SearchFrontend 6.5.2
(Latest version available in repository)
Hi @michaaa,
strange, we run the same version(s) and can't reproduce it.
Can you please try to (temporary) disable the JS Loader (Admin->Sysconfig->Search for Loader::Enabled::JS
and set it t o no. This disables the JS compression / minify logic, so we can check where the error comes from.
Then reload the page and paste the error message again.
Thanks and greetings
Johannes P.S: Greetings to Tobias
Hi @hanneshal,
nice to read from you, Greetings back from Tobias and of course all of our team.
Well, setting Loader::Enabled::JS
to "no" makes the Znuny Search Frontend plugin work, so I think the problem must have to do something with the (now disabled) compression logic. However, I don't know how to debug this in deep.
Greetings, Micha
P.S.: Well, "it works" in some way, as it finds stuff, but it's not very fast / responsive and some controls (f.i. sort order) doesn't work either.
Hi,
we have got the same problem on different accounts.
It's seem to be related by loading the past sesrches from the user settings.
If I clean the recent searches in the DB table user_preferences
the values ZnunySearchFrontendLastSearch
and ZnunySearchFrontendSavedFilters
.
So is it an option to make a config setting for loading recent searches from the user settings, so when the agent got an problem, the loading can be disabled.
Greetings, Christian
I had the same problem here, it only worked when I disabled Loader::Enabled::JS
The Znuny Search is configured and index is created. It looks nice so far, but acccesing the frontend always ends in an Browser error message:
"An error occurred! Please check the browser error log for more details!"
In JavaScriptConsole I see:
[ERROR] JavaScriptError: unexpected token: identifier
First I tried to remove js-cache, but it doesn't fix the problem.