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

Possible bug with Relevance Support. #1251

Open
regispicanco opened this issue Sep 8, 2016 · 5 comments
Open

Possible bug with Relevance Support. #1251

regispicanco opened this issue Sep 8, 2016 · 5 comments
Assignees

Comments

@regispicanco
Copy link

Hi,
When Relevance Suport is disabled, I can search a FAQ using only the ID of the FAQ.

When The Relevance Suppoort is enabled, I can not search the FAQ using only the ID of the FAQ.

I tried to put the ID on the Title of the FAQ, like:
Title: (1001) - FAQ example
where 1001 is the ID of the FAQ.

If I search only for "1001" (whitout quotes), nothing is returned, but, if I search for "(1001)" (without quotes) the FAQ is returned.

Our System Information is:
Informação do Sistema

phpMyFAQ Version 2.9.5
phpMyFAQ API Version 1.1
Server Software Apache/2.2.15 (Red Hat)
Server Document Root /sites/base
phpMyFAQ Installation Path /sites/base/homologacao
PHP Version 5.6.21
Webserver Interface APACHE2HANDLER
PHP Extensions Core, date, ereg, libxml, openssl, pcre, zlib, filter, hash, Reflection, SPL, session, standard, apache2handler, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, iconv, intl, ldap, exif, PDO, pgsql, Phar, posix, shmop, SimpleXML, soap, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlwriter, xsl, zip, pdo_pgsql, pdo_sqlite, wddx, xmlreader, xmlrpc, json, mhash
PHP Session path /var/lib/php/session
Database Server pgsql
Database Server Version n/a
Database Client Version 8.4.20
Elasticsearch n/a

PS - Congratulations, PHPmyFAQ is fantastic!

@thorsten thorsten added the Bug label Sep 8, 2016
@thorsten thorsten added this to the 2.9.6 milestone Sep 8, 2016
@thorsten thorsten self-assigned this Sep 8, 2016
@thorsten
Copy link
Owner

It's no bug, it's a feature. It's the search for the solution ID. Every FAQ entry has an unique solution ID, starting with 1001. if you search for numbers, it will try to find the FAQ with this solution ID. You can disable this feature in the admin configuration: Admin -> Configuration -> Search -> Search for solution ID (default: enabled)

@regispicanco
Copy link
Author

regispicanco commented Sep 15, 2016

Hi Thorsten,

I have both options "Search for Solution ID" and "Activate relevance support" enabled.

I did the same test in two different instalations.
In the first one, I used PostgreSQL and I had the behavior I describe in the Issue.
Even if the option "Search for Solution ID" is enabled, I can not find the faq searching by its Solution ID.

In the second installation I used AMMPS and did a fresh install using MySQL.
Now, with MySQL and with both options "Search for Solution ID" and Activate relevance support" enabled, I could search and find faq using just the Solution ID.

I think the different behavior could be related to PostgreSQL.

The strange thing in PosgreSQL installation is when the "Search for Solution ID" is ENABLED and the "Activate relevance support" is DISABLED, I can search the FAQ using only the Solution ID.
But if both are enabled, I can not find the faq using just the solution ID.

@thorsten thorsten modified the milestones: 2.9.7, 2.9.6 Dec 24, 2016
@thorsten thorsten modified the milestones: 2.9.7, 2.9.8 Apr 2, 2017
@thorsten thorsten modified the milestones: 2.9.8, 2.9.9 Jul 11, 2017
@thorsten thorsten modified the milestones: 2.9.9, 2.9.10 Aug 10, 2017
@regispicanco
Copy link
Author

Hi, Thorsten, do you need any more information?

@thorsten
Copy link
Owner

Well, I need a proper PostgreSQL environment, still need to build that.

@thorsten thorsten removed this from the 2.9.10 milestone Feb 17, 2018
@thorsten thorsten added the API label Jan 21, 2019
@thorsten thorsten removed the API label Jan 2, 2020
@stale stale bot added the wontfix label Jan 1, 2023
@thorsten thorsten removed the wontfix label Jan 1, 2023
Repository owner deleted a comment from stale bot Jan 1, 2023
@ernestbuffington
Copy link

Mac or Windows?? All problems that would not appear in a remote developer server running on Linux!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants