eicken71

After experiencing other funny things with Firefox, I discarded it completely and switched to Brave. Since then, the issue is resolved – never ask why.

Thank you for following up!

Hi Peter,
Thank you for your detailed and informative answer! Sounds good, though requires more learning on my side. So far I have avoided tinkering with CSS. SQL seemed enough of a challenge for the moment. But I will try to apply what you suggest.

Best wishes,

Matthias

The shutdown situation looked like this:

After deleting SQL Charts files from WordPress via the hosting provider’s interface, the website was open again.
However, the email sent automatically from the WordPress system identifies another plugin as the villain: Table Press. So apparently SQL Charts conflicts with Table Press. After deactivating Table Press, there was no more any problem with installing SQL Charts again.

I attributed the issue to PHP compatibility because I had experienced the same behaviour after updating my PHP version. I could only update after parting with a particular printing plugin. So apparently I was wrong blaming SQL Charts – sorry for that.

This is exactly my experience. And the issue is urgent: When I update the PHP version, backend access to my website is denied. This is not the case on a ‘staging’ subdomain, so it is not a problem on the side of the hosting provider. I would like to find out which plugin is causing this incompatibility. There is apparently no troubleshooting plugin available that would do this. So do I have to deactivate 50 plugins one by one to find out? This is crazy.

Thank you, Peter, but in my use case exporting a single databse table is of little use. Gathering information suitable for analysing H5P user behaviour requires combining information from many tables, including those created by the H5P-plugin that contain information about the exercises presented on my site.

After now having understood WP data access, what it does and what it can’t do yet, the challenge for me is simply learning sql better, exploring the data structure and composing meaningful queries. The ultimate goal would be just one query that creates one table per month which can be CSV-exported from the query builder for import into a statistics tool – a table containining all the information needed for useful analyses but no more.

Best wishes,

Matthias

Hi, Peter,

starting my answer from the bottom of your message:
I’m operating a language learning site – ondaz.de – with interactive H5P exercises. In order to better understand user behaviour (exercises too difficult? how many give up without completing? which exercise nees improving?), I have installed the h5pxapikatchu plugin which collects and stores the xapi statements sent by H5P. It is a very messy tool: Whenever a visitor hits a post in which H5P exercises are embedded, even without actually interacting with the exercise, H5P fires “attempted” statements which are collected. When a user interacts with the exercise, an “interacted” statement is generated. Therefore, a monthly collection of data is around 25,000 rows of ‘interactions’. As I learnt from analysing the data, most of it is white noise of the kind just described. But in order to reduce the amount of data and prepare them for analysis, I must still be able to handle the mass. The h5pxapikatchu plugin itself only allows to delete everything in order to prevent the database to become too large; analysis and selective reduction require sql access.
The problem with the default max. row limitation was that I had taken from tutorials to end queries with “;” – the Data Access editor then places a LIMIT command behind the “;” which causes a syntax error. I have now found out that without the “;” there is no syntax problem. So this issue is resolved.
If I may add one more point: The funktionality for saving queries is not very convenient. I would prefer to build a query library with names of queries and explanations of what they do. It is not clear to me what happens when I click the “save” button and how I can label the query just saved. So I have resorted to collecting queries in an EXCEL sheet.

Thank you,

Matthias

Another problem is that apparently SQL queries read only a maximum of 4,438 rows even though the data explorer shows that the table from which data are selected has many more rows. Why is this? And is there a workaround?

O.K., it was not clear to me that multiple uploads are not possible. You should clarify that in the upload question type template. Now there is a statement “Maximum upload file size: 64MB” plus a menu for setting the maximum file size to as much as 100MB maximum. This made me assume that 64MB is the limit for a single file and that 100MB is the maximum total size of several files. You should at least clarify this in your next update.
Of course multiple uploads would be desirable.

No problem if individual submission data can be retrieved with phpMyAdmin from the WordPress database. But how exactly is it done? Is it enough to export the ayssurvey_submissions table? Or what else would need to be done? Could you give an example for the SQL query that needs to be run?

Resolved by using text editor. There was a jumble of code at the bottom of the page – deleting it solved the problem.

Great, thank you! That does the trick! I was not aware what this settings option is doing.