peterdeegan

We removed the old/legacy jobs – OK.

But there’s no action when we start a simple DB backup, click the green Start button then nothing — no error, no log entries, no Backup History, nothing saved to the folder etc.

Honestly, we’ve put it aside for the moment since there are other more pressing matters. Will let you know when we can return to this matter.

Peter Deegan

I take your point about RegEx and HTML. The code we have is very old and we’ve been happy with things the way they are. To say nothing of the difficulties understanding the DOM model.

But I’ve taken the plunge and added a DOM object. FWIW, this is the code I’m using to remove SimpleTOC block from a posts HTML.

// removes the SimpleTOC block - finds any UL tag with the class=" as shown and remove entire block including nested UL's.
$xpath = new DOMXPath($dom);
foreach($xpath->query('//ul[@class="simpletoc-list"]') as $div) {
$div->parentNode->removeChild($div);
}

Not many people will need this, our exporting posts scenario is quite rare.

Danke,

Further to Marc’s suggestion of Reusable Blocks — which works like a charm.

I suggest using Lock Reusable Blocks https://ww.wp.xz.cn/plugins/lock-reusable-blocks/ which prevents accidentally changing a reusable block when it’s in a post.

That ensures the block settings aren’t altered unless you really mean it!

Peter Deegan

OK thanks. We’ll continue to look

Regards,

Forgot to mention … tried some of the obvious/standard JS workarounds — disabled front.min.js in WP-Rocket Javascript deferred.

Alas … not luck

Cheers,

Tobias,

Always good to hear your words of wisdom.

Changing wp-content to another name seems to be a common WP security measure.

WP-Rocket or other caching is always a possibility. I’ll try that and hopefully be able to report back.

Peter D/

This CSV encoding problem with Excel is a real nuisance … I see there’s lot of discussion and confusion in the forums. I’m writing it up for Office-Watch.com

My suggestion to you, and all developers saving to CSV is to have a UTF-8 BOM export option (or make UTF-8 BOM the default). That’s the same as UTF-8 but with a non-printing marker to indicate the encoding used. With UTF-8 BOM, Excel will import correctly from a direct double-click on the CSV. In the case of TablePress a BOM option should be simple to add and hopefully save a lot of hassle for your customers.

Otherwise, use Get & Transform or Text Import Wizard to select the encoding when importing a CSV.

How does TablePress handle importing CSV with UTF-8 BOM (just curious, not an issue for us)?

Switching to UTF-8 BOM for export and import would help with round-tripping from Excel.

Just €0.02 cents worth <g>.

Peter D/