WP Data Access 5.5.x Breaks SQL Reports

  • Resolved newwebcreative

    (@newwebcreative)


    3 days, 19 hours ago

    One of the recent WP Data Access Plugins seems to be breaking SQL reports or the ability to load them into the query editor. I have several reports that I use to support a client and after the 5.5.x update that started asking whether I want to convert the visual query, some of the report won’t load–the screen is blank and there is just a Create new query button at the top. It isn’t and has never been a visual query, so not sure why it is offering that.

    Is there a way to recover the reports that have been affected?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter newwebcreative

    (@newwebcreative)

    3 days, 18 hours ago

    One additional observation that may help narrow this down.

    I first noticed this after updating to the 5.5.x series. I’m currently running WP Data Access 5.5.76, but I believe the issue may have started in an earlier 5.5.x release.

    The SQL itself does not appear to be lost. The queries are still listed under Open Query, and I can click the View (eye) icon to view the complete SQL.

    When I try to Open certain SQL Queries for editing, the Query Builder offers to convert them to a Visual Query. I always choose No because these are hand-written SQL Queries and I do not use Visual Queries.

    Most of my SQL Queries open correctly after selecting No, but certain ones do not. The editor opens with a blank screen.

    When this happens, the Query Builder interface also becomes unresponsive. The menus no longer function, and I have to refresh the browser before I can continue working.

    I also copied the SQL from one of these queries using the View option, created a brand-new Query (not a Visual Query), pasted the SQL, and saved it successfully. The newly created SQL Query exhibits the same behavior and cannot be reopened for editing.

    This makes me think the issue is related to the SQL Query editor rather than the stored SQL itself.

    If it would be helpful, I can also provide the SQL that reproduces the issue or a short screen recording demonstrating the behavior.

    Plugin Contributor Kim L

    (@kimmyx)

    3 days, 2 hours ago

    Hi @newwebcreative,

    Thanks so much for letting us know about the issue you encountered. We’d appreciate it if you could send us more details by sending us a message via Contact | WP Data Access.

    We’ll wait for your email! 🙏

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    2 days, 1 hour ago

    Hi @newwebcreative ,

    We were able to identify and solve the problem. The fix will be available after the next update.

    Thank you for reporting!!

    Thread Starter newwebcreative

    (@newwebcreative)

    1 day, 22 hours ago

    Thank you very much for the quick investigation and fix! I appreciate the excellent support. I’ll keep an eye out for the next release and will test it once it’s available.

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.