Page 1 of 1

Admin backend dropdowns suddenly inactive

Posted: Thu Aug 31, 2017 2:16 pm
by Huhu
After installing the Multilingual plug-in, suddenly all dropdown and even link buttons of the Admin interface became inactive. I did not change the before that smoothly working config other than that. Template: Clean Blog.
After deleting Multilingual Entries, the links are clickable again, but the error message persists.
Error message:

Code: Select all

 Error: . Does it exist? Please check your privileges to this table; triggered in serendipity_event_multilingual, setupDB() method.

Re: Admin backend dropdowns suddenly inactive

Posted: Thu Sep 14, 2017 1:39 pm
by garvinhicking
Hi,

the error message refers to a non existing variable; what it should show you is that the database table "serendipity_entryproperties" is missing. Usually that one is created with the serendipity installation; is it missing on your installation?!

Re: Admin backend dropdowns suddenly inactive

Posted: Tue Oct 03, 2017 11:28 am
by Huhu
garvinhicking wrote:what it should show you is that the database table "serendipity_entryproperties" is missing.
Ah. I renamed the prefix of the tables during the s9y installation, from "serendipity_" to "ml_" .
maybe the plug- in does for some reason not adapt to the custom table names?

PS Nice flickr stream btw. Reminds me that my last holiday worth it's name is some years past ...

Re: Admin backend dropdowns suddenly inactive

Posted: Tue Dec 05, 2017 7:03 pm
by sde
I have the same problem, directly after a clean installation with version 2.1.1. Table "serendipity_entryproperties" does exist. Is there anything else I can check or try?

Re: Admin backend dropdowns suddenly inactive

Posted: Wed Jan 10, 2018 12:19 pm
by garvinhicking
sde wrote:I have the same problem, directly after a clean installation with version 2.1.1. Table "serendipity_entryproperties" does exist. Is there anything else I can check or try?
Does your prefix mismatch? That table should always exist with a fresh s9y installation; the SQL creation statements for it are listed in db/db.sql - maybe an error occured for its creation?