Hi,

I install the plugin "performance boost k2" following an advice from a friend in order to improve the speed of search in the search module. and sincerely the plugin worked well but he creates a problem with some additional fields.

after installing two other extra fields does not appear in the results of research (there are empty since the administration page) but I'm looking these fields from the database I find the values ????

Any ideas ?

It is probably a caching issue.
Clearing the extension's or the site's cache might do the trick.

However since we are not affiliated with this extension I would suggest that you refer this issue to the extension's developer.

Hi,


no it does not have the cache because when I disable the plugin additional fields appear in the result and when i active they disappear. I contact the developer of the extension but it could not solve the problem.

the plugin works very well but I don't know why he hides that two additional fields and not others !!

Hi,


no, it does not have the cache because when I disable the plugin additional fields appear in the result and when i active they disappear. I contact the developer of the extension but it could not solve the problem.

the plugin works very well but I don't know why he hides that two additional fields and not others !!

Since the fields are showing up without the extension, this means that the issue is related to the extension and not K2.

Exactly, but why it shows 2 fields and hides 2 field knowing that the 4 fields are the same type "dropdown list"

and here's remark developer ( It is little strange as the booster plugin is only using the PHP built in json decoder and encoder instead of the K2 library. Was some sort of importer used for the creation of the articles or the fields? )

is there a relationship between the response and the 2 settings "management library jQuery" and "Management of the library jQuery in the administration" ?

I would not know since I do not know how the "performance boost k2" extensions works.

However since this is a K2 extension it should work with K2 seamlessly not the other way around.