Posts

Nigel:

See attached. Works fine when I hide the Stories tab.

Roy

Roy

Apache 2.4.27  PHP 7.19 MariaDB 10.2.8

… and no error message anywhere?

While you are around, can I get access?

Nigel
My personal kiwitrees site is www.our-families.info

Nigel:

Sorry but I had closed down to grill a steak. This install is local so your access would be difficult.

This morning I cleaned out my logs and created the issue again. After rechecking all logs. Found the following PHP error which should be helpful:

[11-May-2017 10:17:24 UTC] PHP Fatal error: Uncaught PDOException: SQLSTATE[HY000]: General error: 3065 Expression #1 of ORDER BY clause is not in SELECT list, references column ‘ourtree.kt_block.block_order’ which is not in SELECT list; this is incompatible with DISTINCT in C:\wamp64\www\Ourtree\library\WT\DBStatement.php:87
Stack trace:
#0 C:\wamp64\www\Ourtree\library\WT\DBStatement.php(87): PDOStatement->execute(Array)
#1 C:\wamp64\www\Ourtree\modules_v4\stories\module.php(130): WT_DBStatement->__call(‘execute’, Array)
#2 C:\wamp64\www\Ourtree\individual.php(276): stories_WT_Module->getTabContent()
#3 {main}
thrown in C:\wamp64\www\Ourtree\library\WT\DBStatement.php on line 87

Roy

Roy

Apache 2.4.27  PHP 7.19 MariaDB 10.2.8

Roy wrote:

Expression #1 of ORDER BY clause is not in SELECT list,

Ah, so it is actually another MySQL 5.7 issue 🙂 Slightly different to the others, but still related so I have moved it to this ongoing thread.

Can you try this for me please:

In the file kiwitrees/modules_v4/stories/module.php line 122 (or close by) should be

"SELECT DISTINCT ##block.block_id" .

Just remove the word DISTINCT and see if that resolves this issue.

Nigel
My personal kiwitrees site is www.our-families.info

Nigel:

The edit worked perfectly. Never would have guessed it to be a SQL issue.

Found something else. I started a Widget journal to track things I was doing for you. Tried to delete an entry; clicked on “Delete”, got the confirmation block and clicked “OK”, Widget closed. The entry is still there. Reloaded the page but that didn’t help. There are no errors in any of the logs.

Should this be posted as a bug and which area should it be posted?

Roy

Roy

Apache 2.4.27  PHP 7.19 MariaDB 10.2.8

Roy wrote:

Found something else. I started a Widget journal to track things I was doing for you. Tried to delete an entry; clicked on “Delete”, got the confirmation block and clicked “OK”, Widget closed. The entry is still there. Reloaded the page but that didn’t help. There are no errors in any of the logs.

Should this be posted as a bug and which area should it be posted?

Yes, definitely a bug. Not MySQL related though. ‘ll start a new thread for it, in your name 🙂

Nigel
My personal kiwitrees site is www.our-families.info

Nigel:

Did a review of what I have done to find MySQL errors. I cannot think of anything else to check. If there is any other errors, they have to be pretty obscure.

Never appreciated how many “nooks and crannies” there were in Kiwitrees. Don’t know how you keep track of them all much less how they interact. Ever think of getting rid of some duplicated data access points such a 2 for Research Tasks, report and widget? I think I even saw one with 3 ways to access the info.

Thanks for all the hard work.

Roy

Roy

Apache 2.4.27  PHP 7.19 MariaDB 10.2.8

1 user thanked author for this post.

kiwi

Roy wrote:

Ever think of getting rid of some duplicated data access points such a 2 for Research Tasks, report and widget? I think I even saw one with 3 ways to access the info.

It really depends on the nature of and reason for the duplication. In most cases it is literally only two alternate display options. All the underlying code is common so only has a single point of maintenance.

Usually, and research eases are a good example, the duplication is the result of users asking for a different way to access the data. Perhaps they don’t want to use the widget bar at all. The extra code to provide both was negligible and only took an hour or so to implement. But having provided two access points I’m not forcing anyone to use both of them.

What I try to encourage is a carefully considered set up, using only what you need, not just enabling everything. I have a half-written FAQ about the process that “should” be followed after a site is installed, covering the thought processes that might determine what should be enabled, what might be left out, and why. I have also started in 3.3.0 to limit the modules that are enabled on initial setup, which might (hopefully) encourage more thought into the use or not if duplicate tools.

But you do raise a valid point. There’s a fine line between the benefits of simplicity and flexibility.

Nigel
My personal kiwitrees site is www.our-families.info

Status changed to “Fix committed” as (we believe) all MySQL 5.7+ issues have now been found and addressed.

Thanks Roy.

Nigel
My personal kiwitrees site is www.our-families.info