1 nabster Sep 22, 2015 10:49
3 nabster Sep 23, 2015 07:48
It is a fresh new install. I simply unzipped the file in the web directory, went through install process and have an empty system. Planning to migrate the content from an old forum manually later.
Server CentOS 6.5 with standard LAMP modules.
4 fplanque Sep 23, 2015 13:15
Ok, can you tell us the exact version number of your DB and tell us if it is MySQL or mariaDB? So we can reproduce the problem.
Thanks.
5 nabster Sep 23, 2015 13:19
Server version: 5.5.44-log MySQL Community Server (GPL) by Remi
Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
6 fplanque Sep 23, 2015 14:59
Ok, we'll fix this. Maybe your MySQL is forced to run in strict mode or something like this, which makes it extra picky about SQL standards.
Can you please post your other errors too so we can address them all?
Thanks.
7 fplanque Sep 23, 2015 23:55
OK, we researched this.
This error appears only if you have set your SQL MODE to ANSI
or more specifically ONLY_FULL_GROUP_BY
:
https://dev.mysql.com/doc/refman/5.0/en/sql-mode.html#sqlmode_only_full_group_by
We have never seen this before.
Did you set your SQL MODE yourself? If not, please tell us who your hosting company is so we have a better understanding of where this is coming from.
We will probably solve this (and all your other errors) by forcing the SQL MODE back to its default value.
8 nabster Sep 24, 2015 01:45
Thanks for your response. That would be definitely the answer. It is a self hosted VPS server so no service provider used. I just got the admin to check its settings.
This is a prod server with the ONLY_FULL_GROUP_BY and other options for strict SQL standards ON
Please let me know if b2evolution can specifically be fixed for this as changing this global settings would possibly not be approved.
9 fplanque Sep 24, 2015 02:10
We are considering adding code to b2evolution to automatically switch to TRADITIONAL sql mode and it will likely be in the next release. (As far as I understand, MySQL always allows that. It is not a security measure in any way to have this one way or another.)
However, can you please explain why you do this and why changing this setting would not be approved?
What is the size of your organization.
Please give us some context so we can better understand your use case and use environment.
We always try to understand such scenarios as it helps us take them into account for the future.
Thank you.
10 nabster Sep 24, 2015 02:26
As I understand it, it is set so the code portability between different databases is possible. Without strict standards, these will need to be edited if the backend DB was to be changed. So the organisation does all the development with the strict modes already in-place.
Its a small organisation still in its development phase of its product.
11 fplanque Sep 25, 2015 00:31
Ok, I see.
Here's the change you can make to have b2evo work on your server:
https://github.com/b2evolution/b2evolution/commit/a694c0bb4f0fd52bcb435510e171bfeb758db287
If you try it, please confirm how it works for you.
Thanks.
12 nabster Sep 25, 2015 02:28
Thank you. That worked perfectly for the users. I'll continue to check but I am confident that there will be no more issues.
Is this a fresh install or an upgrade?
Did you use a third party tool to install or upgrade it?