dizwell

That’s disappointing. I can’t let you look at the migrated site because it’s obviously just sitting on a home PC, uncontactable from the outside world, until such time as I can get this issue resolved. So we’re at something of an impasse, I fear.

An answer to my third question would be appreciated, though: can one switch off the ‘table name/column name verification feature’?

In light of (a) the UTF-8 bug-fix and (b) the vastly improved support and general responsiveness of your replies here, I’ve edited my original review and awarded your plugin the 5-stars it now deserves.

Thank you for the plugin!

Perhaps you fixed it in 2.2.1, which the changelog helpfully says includes “Small improvements”! Or possibly in 2.2.0 which contained “bug fixes”. (A better changelog would be good, by the way!)

I can assure you it was an issue when I first posted the review; I am happy to report that on viewing my problematic web page even just a few weeks ago, the problem persisted.

I’d revise my review to 4 stars in the light of that improvement, and thank you for it.

Well, I reported the lack of UTF-8 support ages ago, via the link you’ve already included… and because I’m not a premium support customer, it seems that nothing has ever been done about it. Not sure why you’d offer a free version at all if you’re not going to pay attention to what your free customers then tell you about the product.

So, by all means: make me really happy and include proper and full UTF-8 support in your next plugin update… but I shan’t be holding my breath!

Hi Peter: get well and don’t bother looking in to the issue. The problem is me not understanding CSPs, which (as you say) are simply not really ever going to sensibly work with Javascript-heavy websites.

I’ve now reverted to a fairly minimal default-src https: ‘unsafe-inline’ ‘self’ data:; base-uri ‘self’; frame-ancestors ‘none’; object-src ‘none’;, which is effectively ‘This is a CSP which doesn’t do much, but does at least require code to be executed via https and doesn’t allow the site to be click-jacked in other people’s frames etc’, but *does* count as a CSP of some sort.

It at least means I now pass the security scanning tests at sites like observatory.mozilla.org with a B+ rating (which is rather better than my starting F fail grade!), but I don’t break my site in the process.

The fault was mine not really understanding what CSPs did or set out to do. I’m much more informed now, and realise aiming for an A rating with much stricter limits on script sources and so on would be practically impossible without a lot more effort than I’m prepared to throw at a hobby site!

Anyway: look after yourself and get well soon!

Best wishes,
Howard

Following up: Having done some reading around the subject of CSPs, it seems that they are destined to not work whenever a site uses a lot of Javascript and so on. So, I’ve now implemented the bare minimum:

default-src https: 'unsafe-inline'

The effect is not to really have much by way of an *effective* security policy, but it at least keeps WP Data Access (and everything else!) working. And that seems to be quite a common outcome of attempts to implement a CSP, so I’ll live with it!

So unless you have further insights on the matter, please don’t waste any time looking into this!

Many thanks for all you do,
Howard

Bingo. Guess which dummy had removed the primary key on a column and forgot to put it back?!

Thank you. I felt sure you’d be able to diagnose my errors fairly swiftly!

Regards
H

The DOM options (which I can never remember, but I kinda-sorta knew that a string of letters let me switch bits on and off) do the trick, so thanks for that. I doubt anyone much cares what music I listen to, so I don’t imagine the problem of ‘unwanted rows’ is going to be something to worry about, really!

Thanks for all your help, as ever,
Howard

Oh: one quick final thought. Would it be possible for the plug-in to consider a ‘Allow Paging’ off to be treated as ‘Switch paging on, but to a row limit of 999999999999999999′, or similar? So that, it is seen as being *effectively* off, in practice, but still actually performs the query on the server which causes dates to be regarded as such?

The real reason I wanted the pagination off, I think, was simply to see what a table without the “Previous – 1.2.3.4 – Next’ buttons would look like in the footer.

So then, if your plugin saw the row limit for a query set to some stupidly high special value, it would also need to know to switch of the pagination buttons.

But… that’s the kind of cludgy workaround I’d knock up. It’s probably not up to your standards!

Anyway: Vivaldi is looking fine once more, with proper ‘pretty’ dates.

Thanks again,
H

Thanks Peter: that explanation makes perfect sense. Especially as I know I’ve never previously fiddled with the WordPress default date format… but this was, indeed, ny first ever attempt at turning off pagination!

I think I’ll be able to turn pagination back on (the reason it was ever off was because of a long and complicated series of experiments, none of which remain valid, but whose after-effects persist!)

I’m glad the answer turns out to be ‘yes, there’s actually an issue’ *AND* ‘yes, you’re doing it wrong!’ ??

Since the problem is in the way the browser works, I’d say your work here was done, to be fair!

Best wishes,
Howard

Hey, I did a ‘drop database’ on a production database once. After having deleted all backups.

To err is human. To really stuff things up, you need an over-confident DBA who’s not paying attention!

??
HJR

Oh good! At least it’s not me being stupid!

And the patch is perfect: everything is looking normal once again.

Thanks for the excellent support work, as usual.

Take care,
Howard

Sorry if I’m getting the wrong end of the stick, but

https://absolutelybaching.com/testpage.html

…will get you the code cut-and-pasted out of that page, showing the shortcodes I’m using.

Sorry, Peter: Not really sure what you mean.

https://absolutelybaching.com/catalogue-of-johann-sebastian-bachs-works/cantata-bwv-1-wie-schon-leuchtet-der-morgenstern/

…is the page. Directly accessible, no menus involved.

Can you not get to it or something?

Cheers,
HJR

Hi Peter,

As I said, in Settings -> WP Data Access -> Front End, the radio button ‘Show only selected tables’ is selected and the bachtrans table is then highlighted. So yes, I think I have granted the relevant permissions.

In case we’re not talking about the same things, I have added a screenshot of those Front End settings to the page I’ve previously linked to, so you can see exactly what’s set, selected and what have you.

But none of that has changed recently, anyway.

Regards
HJR