Geeklog Forums

After a reinstall of this software and attempting to access "Configuration" from the menu I get the following:

2 - array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object @ C:\geeklog\system\classes\config.class.php line 1682

I can access all the other links but the configuration.... help!

What exactly do you mean be "reinstall"? Is this a fresh install, an upgrade from an earlier version or something else?

The error seems to refer to an entry in the language files. Are you using the proper language files for 1.8.0 or is it possible that you're using them from an older version?

bye, Dirk

I initially installed it on the server for the first time....encountered a slight problem ....then decided to to delete and start new installation. That's when I encountered the error.

Thanks

At first glance it does appear to be a language file issue. Did you autoinstall any plugin when you did your fresh install of Geeklog?

---

One of the Geeklog Core Developers.

Geeklog upgrade:
automatically create 2 data in `gl_conf_values' bellow, even if the plugin is old and not requre gl_conf_value's sg_main and fs_main.

`gl_conf_values`:
('sg_main', 'N;', 'subgroup', '<old plugin>', 'N;', 0, -1, 0, NULL, 0),
('fs_main', 'N;', 'fieldset', '<old plugin>', 'N;', 0, -1, 0, NULL, 0);

Delete these 2 data, then configuration.php works well.

---

Geeklog Japan https://www.geeklog.jp

I seem to have the same problems like 'congleal'. I did an update from 1.7.1 to 1.8.1

Did anybody find the reason, is there a fix?

Should I try ivy's hint? Am I to delete the 2 complete lines of the configuration? The lines seem to exist a couple of times per plugin.

If I google this problem, it seems to have something to do with php 5.3

Just a note incase anyone else had this problem.

1000ideen problem was the result of a plugin not removing it's own configuration values from the database when it was uninstalled. It left config values in the gl_conf_values table.

To fix, in phpmyadmin search the group_name column for "newsletter" (in this case) and then delete all those records. After that the configuration should work fine.

---

One of the Geeklog Core Developers.