EDK 4.2.27.0 (YC-118-9 1.0)

[Salvoxia]

\o guys,

EDK 4.2.27.0 (2016-10-17)

This release updates your database to YC-118-9 1.0.

Other than that, a few leftovers of old code in the installer has been updated, that was incompatible with PHP7. If any of you guys encounter problems
when using PHP7 with EDK, please let us know!

There's another notable change in this version, which primarily seems to be interesting for developer, but makes it much more easy for them to create mods using EVE's SSO.
Mods now have the possibility to disable EDK's page caching mechanism when an event is fired by EDK that the mods have subscribed to. For an example take a look a Snitch's SSO Mod,
that lets you log in to your killboard via SSO and controls posting comments, lets you post your own character's kills available via the API and compare your stats against any other pilot!


Download:
Full Install Package 4.2.27.0: Download (please check MD5: 8B7F1484D5A7E326DAB759AE6E674B5D)
Update 4.2.26.0 - 4.2.27.0: Download (please check MD5: 72E586507C1BDBA4957557EBB5C9BEE6)


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



Release Notes:

List of new features

• Updated EDK to 4.2.27.0 and CCP DB to YC-118-9 1.0.20161011

list of Enhancements

• Added possibility to disable page caching via session

List of Bugfixes

• Updated Copyright to 2016 in database update template
• Removed last traces of procedural method calls using mysql

Installation Instructions:
Requirements

• Webserver (e.g. Apache)
• PHP 5.2+ (5.3.7+ recommended)
• MySQL 5.0+
• GD 2 or higher (default on most hosts)
• PHP MySQLi extension (default on most hosts)
• PHP XML extension (default on most hosts)
• PHP openssl extension (default on most hosts, required for API use)
• PHP Safe Mode off. (highly recommended)

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.26.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.26.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.26.0 - 4.2.27.0 (see above)
• Backup the existing database and files
• Upload the contents of the update package to your webhost
• DONE

Known issues:


Regards,
Salvoxia

[Dism0]

anything new and exciting coming up? maybe add daily isk killed and isk loss to the kill/loss/efficiency section.

[Salvoxia]

Hi,

you are right that the last releases did not bring anything new, and I'm sorry for that. RL has been ramping up lately, resulting in a lack of time (and, admittedly, motivation) to develop new features. I'm running in "maintenance mode", so to speak. On top of that, I'll be on a business trip next week and the week after that, so the EDK database update for the Novemeber release will be late as well :-/

However, it seems CCP just released the next milestone for EDK: the ESI API. Since they're planning on shutting down both the XML API and CREST, it seems necessary to focus time and energy on removing CREST and XML from EDK and switching to ESI.
This will take some time and increase the minimum requirements of EDK from PHP 5.2 to at least 5.5 I guess.

So that's definitely an exciting prospect, even if it so mostly for the developer. However, entering API Keys will be a thing of the past, since ESI completely relies on SSO. That's quite some change for the user, that surely can be built on.

Best Regards,
Salvoxia

[Dism0]

nice. look forward to that update.