Re: [XAseco] Fufi Menu v0.31
Posted: 04 Sep 2009 18:01
There is no latest awards feature in the current TMX API, therefore not in XAseco, and therefore not in the Menu either.SchNaake wrote:or you can "Latest Award" to add?
There is no latest awards feature in the current TMX API, therefore not in XAseco, and therefore not in the Menu either.SchNaake wrote:or you can "Latest Award" to add?
BUMP!jimos94 wrote:I got the same error again after a long time.Is there anyone having the same problem? I'm using the latest release of the plugin (v0.31) as well as XAseco v1.09.Code: Select all
Fatal error: Call to a member function isGroup() on a non-object in /TMF/ronserver2/ronxaseco2/plugins/plugin.fufi.menu.php on line 342
Change line 342 into:Skysurfer wrote:We're getting this error (exact message and line number).jimos94 wrote:I got the same error again after a long time.Is there anyone having the same problem? I'm using the latest release of the plugin (v0.31) as well as XAseco v1.09.Code: Select all
Fatal error: Call to a member function isGroup() on a non-object in /TMF/ronserver2/ronxaseco2/plugins/plugin.fufi.menu.php on line 342
Code: Select all
if ($entry && $entry->isGroup()){
I already updated the v0.32 download link with this change, but I'll hold off changing the version number pending confirmation that the problem no longer occurs... which may take a while since it's a rare issue.jimos94 wrote:Thanks for the reply too. It happens to my servers now and then but now it will be ok i guess. Is it possible to update the Fufi menu with this change?
"once" he's absent? He's already been absent since Feb 2009, apart from a brief life sign, that's why I've making a few menu updates as per the first post. I'll make another when releasing the next XAseco version, as that has some changes which affect the menu.jimos94 wrote:Let's say Fufi Menu v0.32a, once fufi is absent somebody should do it.
I'll get you an answer sooner than you think Xymph, I wouldn't call it rare in our case... It's happened almost every day since we updated last week.Xymph wrote: I already updated the v0.32 download link with this change, but I'll hold off changing the version number pending confirmation that the problem no longer occurs... which may take a while since it's a rare issue.
Okay the good news is this one hasn't come back since I updated the code. Our server has been incredibly stable and hasn't needed a restart for three days now.Skysurfer wrote: I'll get you an answer sooner than you think Xymph, I wouldn't call it rare in our case... It's happened almost every day since we updated last week.