Topic: Elevayta plugins issue

Viewing 4 posts - 1 through 4 (of 4 total)
  • April 23, 2012 at 14:23 #2737
    kingtubby
    Participant

    Something changed in Podium 3.1.1 that disagrees with Elevayta freeq_boy and space_boy plugins and causes Podium to crash every time. To be fair they haven’t been updated since 2006, so current compatibility could be an issue though they did work in v3.1.0. It’s not a pressing problem as I’ve not tried to use them for quite a while – the problem arose when I did plugin database rebuild – I reinstalled v3.1.0 to check and they were ok, but I’ve removed them for now and was wondering if there’s an obvious change that might have caused the problem…

    April 24, 2012 at 06:12 #21728
    The Telenator
    Participant

    Sorry all, but I posted a thorough bug report just now over in the VIP lounge concerning my own experiences and testing of 3.11 alpha. Probably should have posted in SUPPORT, so feel free to move it, Frits, if you need to.

    April 24, 2012 at 22:18 #21733
    The Telenator
    Participant

    I retested everything this afternoon and received the exact same results as at first. I ran a virus scan just to be sure and all detections=null. I’ve picked up another copy of v3.1.0 and will roll back to that very stable version just like you have, kingtubby, in a few minutes.

    I found 3.1.1 beta2 to have no issues, so whether I’ll return to running that EXE over the top of 3.10 or not I can’t say. I may simply wait for needed fixes to the alpha. I see other issues with the latest showing up on the forum, so I suggest sticking with 3.1.0 until we hear more. Cheers!

    April 28, 2012 at 15:38 #21759
    Zynewave
    Keymaster

    @kingtubby wrote:

    Something changed in Podium 3.1.1 that disagrees with Elevayta freeq_boy and space_boy plugins and causes Podium to crash every time. To be fair they haven’t been updated since 2006, so current compatibility could be an issue though they did work in v3.1.0. It’s not a pressing problem as I’ve not tried to use them for quite a while – the problem arose when I did plugin database rebuild – I reinstalled v3.1.0 to check and they were ok, but I’ve removed them for now and was wondering if there’s an obvious change that might have caused the problem…

    I haven’t tried these specific plugins, but I have found an issue that causes some older plugins to fail during plugin scan/load. I expect to release 3.1.2 tomorrow, with just this fix.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.