EDK 4.2.37.0 (YC-112-3 1.0)

[Salvoxia]

\o guys,

EDK 4.2.37.0

This release updates your database to YC-120-3 1.0.

Also, the auto updater has been equipped with a PHP version check. Since the next major EDK release for ESI will require at least PHP 5.6, the auto updater will check if that prerequisite is met before applying the update.




Download:
Full Install Package 4.2.37.0: Download (MD5: 6CE6C0B6BE3F2EBE7C220DD2DEC2885A)
Update 4.2.36.0 - 4.2.37.0: Download (MD5: 7FE2109899C9FC7179C228BB77E31B37)


Database only:
Download the standalone database update for of EDK4.2+ here: Download (MD5: F7ACB77CE4D11B94769AAB803BB42906)



Release Notes:

List of new features

• Updated EDK to 4.2.37.0 and CCPDB to YC-120-3 1.0.20180323

Enhancements:

• Added PHP version check to auto updater (at least 5.6 for EDK 4.3 and above)

Installation Instructions:
Requirements


New Installations

• Upload the whole package to a webhost
• Point your webbrowser to /install inside the EDK directory
• Follow the instructions
• Delete the install folder after installation
• If no pilot images are displayed check that the server has write permission to the cache folder.

Manual upgrade

• Backup the existing database and files
• Remove or rename all files in the killboard folder other than [kbfolder]/kbconfig.php
• Upload the new package to the killboard folder
• Remove install folder
• Move your mods back from the backup to the mods folder.

Update from 4.2.36.0:

Auto Updater

• Backup the existing database and files
• Enter the admin control panel
• Select the option "Upgrade" from the menu on the right
• If the code update to Version 4.2.36.0 doesn't show up in the list, select the link at the bottom saying "retrieve update description file now"
• Click "Download"
• Click "Apply"
• Database update process starts, follow instructions
• DONE \o/

Manual upgrade

• Download the Update 4.2.36.0 - 4.2.37.0 (see above)
• Backup the existing database and files
• Upload the contents of the update package to your webhost
• DONE

Known issues:


Regards,
Salvoxia

[Redhouse]

Looks good, thanks.

[Salvoxia]

Thank you, your feedback is very valuable.

[alghara]

I have updated from 4.2.36.0 to 4.2.37.0 but i don't have menu for ESI. I need to make something to have it ?

[Salvoxia]

Hi,

ESI integration is still in the test phase, see this thread:
http://www.evekb.org/forum/viewtopic.php?f=1034&t=22057

Any test results and feedback is appreciated.

Best Regards,
Salvoxia

[mccrashman]

Hi,

i have updated our killboards today from version 4.2.36 to 4.2.37. So far the update went well but all FOB killmails are gone.

Is there any way to restore those killmails or prevent loosing those killmails in the update process (have made an backup before update, so i can rollback changes).

Best Regards,
mccrashman

[Salvoxia]

Hi,

what do you mean by "FOB killmails"?
Updating the killboard should NOT result in any loss of kills. If the kills are really gone (not just a display/caching problem), something went terribly wrong there.
I'll need some more information, though.

How did you update (auto updater / manually uploaded the code update)?
Was the kbconfig.php file changed in any way?
Does your killboard no longer contain any kills? What does it same about the number of kills on the "About" page?

Best Regards,
Salvoxia

[mccrashman]

Hi,

what i mean with FOB is "Guristas Foreward Operating Base".

I have installed the backup on an other server. So you can see the difference more easily. The most expensive mod still tries to show the lost killmails.

updated killboard: http://www.avaricious-cartel.de/kb/
backup killboard: https://home.mrprotokoll.de/ava/

link to one of those killmails: https://avaricious-cartel.de/kb/?a=kill ... l_id=15629 - https://home.mrprotokoll.de/ava/?a=kill ... l_id=15629

Best Regards,
mccrashman

[Salvoxia]

Hi,

thank you very much for providing the backup, that's very helpful!

First the good news - these killmails are not gone, they're still in the database.
However, I wasn't aware that these structures generated killmails as well, which is why EDK doesn't know about them as "ships".
When posting such a kill, and the victim's ship is unknown to EDK, it simply adds that item as "ship" with an "Unknown" ship class.

When updating EDK and the database, that table gets deleted and replaced by the one shipped with the update. And since I didn't know about them, the updated table no longer contains that item, which is why EDK no longer lists any kills with that item as victim's ship.

To restore the previous state, you can execute the following SQL script on your updated killboard's database:

Code: Select all

INSERT INTO `kb3_ships` (`shp_id`, `shp_class`) VALUES ('46363', '18');

You might have to clear your cache (in ACP -> Cache at the bottom) after that.

edit: As an alternative, you could kill another one and post the kill - that should yield the same result


Since I'm now aware of it, I'll add it for future releases with a proper ship class. I'm just not sure if it will make it into the ESI release..

Best Regards,
Salvoxia

[mccrashman]

Thanks alot, the query was the easier way than setup a fleet today for another FOB

I have to mention that there is another FOB type, which should also be noticed (Blood Raider Foreward Operating Base, see https://wiki.eveuniversity.org/Pirate_f ... ating_base).

Best Regards,
mccrashman