EDK 4.2.35.0 (YC-119.10 1.0)

EDK releases + Open discussion and chat about EDK.
Post Reply
User avatar
Salvoxia
Developer
Posts: 1531
Joined: Wed Feb 22, 2012 12:11

EDK 4.2.35.0 (YC-119.10 1.0)

Post by Salvoxia » Mon Oct 30, 2017 17:48

\o guys,

EDK 4.2.35.0 (2017-10-24)

This release updates your database to YC-119.10.

This database update introduces a new ship class for Refineries and recognizes the CONCORD Marshal Black Ops Battleship as well as the new Guristas Capitals.


Download:
Full Install Package 4.2.35.0: Download (MD5: 99ADF87452641DEE9306AB70C2306EB7)
Update 4.2.34.0 - 4.2.35.0: Download (MD5: FA84D30B9149521D2C7FFF8A772D8D06)


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



Release Notes:

List of new features
  • Updated EDK to 4.2.35.0 and CCPDB to YC-119-10 1.0.20171024
Enhancements:


Bugfixes:
  • Fix: PHP7 compatibility for signature mod
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.34.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.34.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.34.0 - 4.2.35.0 (see above)
  • Backup the existing database and files
  • Upload the contents of the update package to your webhost
  • DONE


Known issues:


Regards,
Salvoxia

celagon
Apprentice
Posts: 40
Joined: Mon Oct 07, 2013 01:50

Re: EDK 4.2.35.0 (YC-119.10 1.0)

Post by celagon » Thu Nov 02, 2017 06:23

Did anything at all change ?

Cause after the update i can no longer import from zkillboard. No idea what happend.

User avatar
Salvoxia
Developer
Posts: 1531
Joined: Wed Feb 22, 2012 12:11

Re: EDK 4.2.35.0 (YC-119.10 1.0)

Post by Salvoxia » Thu Nov 02, 2017 20:56

No, nothing changed on EDK's side.

The orderDirection modifier of the zKB API is temporarily disabled - that's what it says. EDK uses this modifier, but after taking a closer look at the zKB API Docs that shouldn't be necessary.
So you can try to remedy the situation by opening common/includes/class.zkbfetch.php, find the following lone

Code: Select all

$this->fetchUrl .= "startTime/$timestampFormattedForZkb/orderDirection/asc/";
and replace it with

Code: Select all

$this->fetchUrl .= "startTime/$timestampFormattedForZkb/";
If the API really implictly orders the kills ascending by timestamp, all should be fine. Otherwise, you might miss kills.

Best Regards,
Salvoxia

User avatar
Dism0
Active Author
Posts: 155
Joined: Fri Jul 06, 2012 01:42

Re: EDK 4.2.35.0 (YC-119.10 1.0)

Post by Dism0 » Sat Nov 04, 2017 03:26

updated. no problems here.

User avatar
SnakeTheBest
Apprentice
Posts: 43
Joined: Tue Feb 02, 2010 00:30

Re: EDK 4.2.35.0 (YC-119.10 1.0)

Post by SnakeTheBest » Fri Dec 01, 2017 17:19

hi guys, im making a restore from an old edk (4.2.2x) with my old DB backup, i dit somewhat like a fresh install but pointing to the old DB, the whole process made an update to my db and all tables passed , instal completed succefully and everything like normal, but when i click on the "go to your new board" link i got this error

Code: Select all

Database error: Expression #30 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'list.fbcrp_name' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by
SQL: SELECT list.* , count(distinct com.id) as comments, count(distinct ind.ind_order) as inv FROM (SELECT kll.kll_id, kll.kll_timestamp, kll.kll_external_id, mdn.itemID, mdn.itemName, plt.plt_name, crp.crp_name, crp.crp_id, ali.all_name, ali.all_id, kll.kll_system_id, kll.kll_ship_id, kll.kll_dmgtaken, kll.kll_victim_id, plt.plt_externalid, kll.kll_crp_id, kll.kll_points, kll.kll_isk_loss, shp.shp_class, shp.shp_id, scl.scl_id, scl.scl_class, scl.scl_value, sys.sys_id, sys.sys_name, sys.sys_sec, fbplt.plt_name as fbplt_name, fbplt.plt_id as fbplt_id, fbplt.plt_externalid as fbplt_externalid, fbcrp.crp_name as fbcrp_name, fbali.all_name as fball_name, fbcrp.crp_id as fbcrp_id, fbali.all_id as fball_id FROM kb3_kills kll STRAIGHT_JOIN kb3_pilots plt ON ( plt.plt_id = kll.kll_victim_id ) STRAIGHT_JOIN kb3_corps crp ON ( crp.crp_id = kll.kll_crp_id ) STRAIGHT_JOIN kb3_alliances ali ON ( ali.all_id = kll.kll_all_id ) STRAIGHT_JOIN kb3_pilots fbplt ON ( fbplt.plt_id = kll.kll_fb_plt_id ) STRAIGHT_JOIN kb3_inv_detail fb ON ( fb.ind_kll_id = kll.kll_id AND fb.ind_plt_id = kll.kll_fb_plt_id ) STRAIGHT_JOIN kb3_corps fbcrp ON ( fbcrp.crp_id = fb.ind_crp_id ) STRAIGHT_JOIN kb3_alliances fbali ON ( fbali.all_id = fb.ind_all_id ) LEFT JOIN kb3_mapdenormalize mdn ON (kll.kll_location = mdn.itemID) STRAIGHT_JOIN kb3_systems sys ON ( sys.sys_id = kll.kll_system_id ) STRAIGHT_JOIN kb3_ships shp ON ( shp.shp_id = kll.kll_ship_id ) STRAIGHT_JOIN kb3_ship_classes scl ON ( scl.scl_id = shp.shp_class ) INNER JOIN kb3_inv_crp inc ON (inc.inc_kll_id = kll.kll_id) WHERE inc.inc_crp_id in (1 ) order by inc.inc_timestamp desc limit 50 OFFSET 0) list join kb3_inv_detail ind ON (ind.ind_kll_id = list.kll_id) left join kb3_comments com ON (list.kll_id = com.kll_id AND (com.site = "NEWKB" OR com.site IS NULL)) group by list.kll_id order by kll_timestamp desc /* kill list */
the server where is running was implemented by myself, so i wonder if maybe im missing a service or something that should be running on server side?.

User avatar
Salvoxia
Developer
Posts: 1531
Joined: Wed Feb 22, 2012 12:11

Re: EDK 4.2.35.0 (YC-119.10 1.0)

Post by Salvoxia » Fri Dec 01, 2017 17:54

Hi,

this is due to a new default setting in MySQL 5.7.5+.
Please refer to this issue for further information: https://github.com/evekb/evedev-kb/issu ... -294426653

Best Regards,
Salvoxia

User avatar
SnakeTheBest
Apprentice
Posts: 43
Joined: Tue Feb 02, 2010 00:30

Re: EDK 4.2.35.0 (YC-119.10 1.0)

Post by SnakeTheBest » Fri Dec 01, 2017 18:06

woah thanks you man i tought it was something bad on my restore or my server, but i see is a mysql newly relased problem =)

thanks you bro

Post Reply

Return to “General Killboard Chat”

Who is online

Users browsing this forum: No registered users and 6 guests