Posted on: 01/04/05 08:29pm
By: Tor
I have a several web sites running Geeklog and I`m very happy with this system. But..
Now I have installed 1.3.11 on two of them and I run into same problems on both. They are both on the same server, php version is 4.3.10.
I`m using the proffesional theme following the downloaded version.
My problem is where the menu should be, it viewing {menu_elements}instead. Menu settings in config.php is
$_CONF['menu_elements'] = array
(
'home', // link to homepage
'contribute', // contribute / "submit a story" link
'links', // link to the links section (aka web resources)
'polls', // link to past polls
'calendar', // link to the site calendar
'search', // link to advanced search
'stats', // link to site stats
// 'prefs', // link to user's preferences
'plugins' // links added by plugins, like {plg_menu_elements}
// 'custom' // for custom links (see lib-custom.php)
);
Both web sites is acting in same way.
Also I have a problem with prferenses for user functions. If I select this menu " preferences" I get following error message on top of the site:
Warning: preg_match() expects parameter 2 to be string, array given in /home/mywebsite/public_html/usersettings.php on line 418
If I delete language files with name like "english_utf-8.php", the error message disappear.
Also in theme setting box in prefernces window, it show " array" instead of "proffesional"
if I keep the language file called "english_utf-8.php", its written "english(array)" in the language selection box.
I need some hints to solve this problems...
Regards
Tor
Where is my menu
Posted on: 01/06/05 03:52am
By: Tor
Is it possible that nobody have a simular problem ???
I will be very happy of any respons...
Tor
Where is my menu
Posted on: 01/06/05 04:45am
By: JohnVanVliet
hi did you eddit the theme files with dreamwever
or it may be a prob with the quote marks you might have a
doubble quote [ " word " ] where a single is neaded [ ' word ' ]
Where is my menu
Posted on: 01/20/05 07:44am
By: Tor
This problem is related to a server problem. This problem is now fixed, and my website is up running again.