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

Smart Search - Content lock saving articles #20423

Closed
GarryMoveOut opened this issue May 16, 2018 · 5 comments
Closed

Smart Search - Content lock saving articles #20423

GarryMoveOut opened this issue May 16, 2018 · 5 comments

Comments

@GarryMoveOut
Copy link

GarryMoveOut commented May 16, 2018

Steps to reproduce the issue

Make sure that plugin Smart Search - Content is enabled.
Install official Polish Language Pack (3.8.7v2) from joomla.org
Create new article or edit existing, write something and click "Save".

Expected result

Saved article without errors.

Actual result

Oryginal error message:
"Error
Save failed with the following error: BŁĄD: kolumna "t" relacji "i5c7v_finder_terms" nie istnieje LINE 2: SET t.links = t.links - 1 ^
"
translated:
Error
Save failed with the following error: ERROR: column "t" relation"i5c7v_finder_terms" do not exist LINE 2: SET t.links = t.links - 1 ^

Original log from pgsql:
BŁĄD: kolumna "t" relacji "i5c7v_finder_terms" nie istnieje przy znaku 40
WYRAŻENIE: UPDATE "i5c7v_finder_terms" AS "t"
SET t.links = t.links - 1
FROM "i5c7v_finder_links_terms0" AS "m"
WHERE "m"."link_id" = 7 AND m.term_id = t.term_id
translated:
ERROR: column "t" relation "i5c7v_finder_terms" do not exist near sign 40
STATEMENT: UPDATE "i5c7v_finder_terms" AS "t"
SET t.links = t.links - 1
FROM "i5c7v_finder_links_terms0" AS "m"
WHERE "m"."link_id" = 7 AND m.term_id = t.term_id

System information (as much as possible)

Platform
CentOS 7 + Apache2 + PostgreSQL 9.2 + PHP 5.14.6 + Joomla 3.8.7 (3.8.6 also)

Additional comments

When I disable Smart Search - Content plugin all works fine. Also SQL statement is wrong.

@brianteeman
Copy link
Contributor

If i recall correctly the key issue here is that it is using postgres

@csthomas
Copy link
Contributor

The patch is at #19964

@joomla-cms-bot
Copy link

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/20423

@ghost
Copy link

ghost commented May 16, 2018

closed as known issue. @csthomas thanks for searching for Pull Request.

@GarryMoveOut can you please test #19964?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/20423.

@GarryMoveOut
Copy link
Author

@franz-wohlkoenig yes of course.
I tested and it works great. No errors.

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

4 participants