After ages of being lazy, StapleButter has finally updated the server. So, what do we get?

* the latest shiny distro, Ubuntu 16.04
* PHP7
* a new (and more picky) MySQL version
* security updates


Let me know if anything shits itself. There were a number of issues caused by the new system being more picky, like logins not working, but this is fixed now. You will need to login again.


KNOWN ISSUES

* board chokes if the URL is too long (buying/selling items, deleting posts...) THERE IS STILL A LOT OF CODE TO FIX
* gfx/status.php is broken

____________________
NSMBHD - Kafuka - Jul

communism

Posted by NintendoFan

Oh, is this why the RPG stat thing on your profile doesn't work anymore? Or is that an entirely separate issue?

... Regardless, good to hear that things are improving.

Oh, good sight. Another thing to fix. fdbdfgf

Posted by maor322

What were we using before?

Older shit.

Also, PHP5. But for whatever reason, it didn't feel like working again after the update. And PHP7 is said to be faster.

____________________
NSMBHD - Kafuka - Jul

communism

post edited, you had given away your token. anyway, yeah, same issue with long URLs.


the new MySQL version is picky. old MySQL would simply truncate strings that were too long, but this new version throws errors instead. we'll need to update the board to sanitize things properly.

____________________
NSMBHD - Kafuka - Jul

communism

no idea what's breaking status.php, but for the rest, MySQL is the one to blame.


anyway, two solutions.

1. set MySQL to run in 'old' mode, where it truncates shit like before
+ it would work. it has always worked so far.
- 'bad'. shouldn't be relied upon.

2. fix the board
+ 'good'. we would be following the right practices.
- effort.

the URL one should be an easy fix, users.url can only hold 100 characters. except when I tried to change it to varchar(1024), it complained that a record was too long. wtf??

shit like editprofile would need fixing -- it will throw an error if you make shit too long by altering the fields' maxlength value, or even if you put characters in fields like 'posts per day'.

another good thing to do would be transactions for shit like posting. so we don't end up in a half fucked up state if a query fails during the process.



oh by the way, status.php is back. we were just missing the GD library for PHP7.


and the issue with long URLs is 'fixed'... it will still blow up if your URL is longer than 65535 characters, but that should be enough for everyone.

I still have a lot of code to fix. blarg.

____________________
NSMBHD - Kafuka - Jul

communism

more fun facts: PHP7 removed support for evaling preg_replace. it had been deprecated for security reasons, and now it's gone.

anyway, I had found that the old K64 archive showed blank posts. that is now fixed.


the current board won't be exploding if you feed it oversized strings or bad integers.

I used the 'bad', easy fix, but I guess that doesn't surprise you.

____________________
NSMBHD - Kafuka - Jul

communism

MySQL error: Expression #7 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'kuribo64.v.user' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by

oh my god. more SQL mode shenanigans.

will fix it after my dinner.


edit- fixed the ugly way.

also seems PHP7 isn't a big fan of divisions by zero.

____________________
NSMBHD - Kafuka - Jul

communism

<insert nerd speak here>

anyway, we had a weird query for counting poll votes. I made it less weird and now it works in strict mode, no more need to tweak the MySQL modes.

oh and while I was at it messing with the poll code, I made it possible to retract a vote from a non-multivote poll.

____________________
NSMBHD - Kafuka - Jul

communism

I don't think running a server on Windows Vista would be a very good idea anyway

However, the server versions of Windows are said to be pretty good at it, but Microsoft yadda yadda capitalism yadda.

____________________
NSMBHD - Kafuka - Jul

communism