Melpomene

It doesn’t work either. If I try and change a background colour it simply rejects the code in the HTML editor. I did make some sort of progress using the visual editor and succeeded in creating a background block colour which is automatically inserted at the foot of the page rather than as an edit. This in itself generates some convoluted HTML which obviously drives its display which only becomes apparent when you switch editor. It automatically centres text rather than aligning left though (despite inserting an instruction to align left). It also wipes out the paragraph tag. It also changes the font size and font style, and simply removes the instruction to use Verdana.

All I need I think is a useable string of code to change a background colour by way of block (the very thing that Gutenberg is supposed to good at!) and some indication as to where to put the text, a colour and style that I also have to change each paragraph as it over-writing what already exists with some style that it’s pulling through, rather than carrying the existing HTML preferences it into the edit.

At least if I had that I could indulge in some massive copy and paste exercise which given that we’re talking about 200 pages, and probably 20 paragraphs means I’m going to have perform about 4000 separate edits. It’ll probably take a month, but I can’t even get past the very basics.

And another thing it’s doing is breaking the <p></p> paragraph tag every time I perform an edit and bunching all the text into continually string with no spacing between paragraphs.   appears to work, although I’ve found myself having to reset and entire page using that code as well each time I try and edit anything. Doing this also seems to damage the Yoast SEO too.

I honestly haven’t seen a single redeeming feature in Gutenburg yet

OK, I’ve tried to experiment a bit, and now realise that no one is likely to reply to the first question(s) because the answer should be self-evident (apologies for that).

The first one is answered it pulls through all PNG files that have ever been posted to the domain (which came as a surprise to me). I thought these were long ago gone and didn’t realise they were still rattling around the system. I could do with a whole load of them exterminating rather than taking up memory. Is there any way of doing this?

The second question concerns the default setting of 90%. Why would anyone want to reproduce a JPG image that is 90% of the quality of the PNG? Should I not set it at 100%? or is the 90% setting something to do with compressing the image, and the image quality itself doesn’t look any different?

Thanks for that

I was aware of the styling issue and had taken steps to avoid that (copy and paste!) so am happy to eliminate that explanation, as its occurred right across the board.

I think your second explanation however about image coding corrupting the page analysis is almost certainly correct, that would explain everything and it makes sense, so thanks for that, as I believe you’ve diagnosed it as a ‘known issue’ with no particularly good work round this case

I suppose the supplementary question (if anyone knows the answer?) would be whether or not your SEO is penalised for not returning the key word in the first paragraph by virtue of the first being read as a PNG file?

Or come to think of it what would happen if I used a series of full stops with a font colour identical to the background colour to try and link the PNG files with the beginning of the text? Would it then read the PNG file and text as one continuous first paragraph?

For reasons I can’t explain (possibly something to do with the WordPress install) I came back about 6 hours later, repeated the process and it uninstalled. Remains to be seen if this is what’s been causing the issue though

Thx

This is what I’ve now done (instinctively it feels wrong)

When I deleted the plug in, and reinstalled it, I kind of expected that I’d have to reload all 300 images and make out a whole load of new sliders? For some reason this didn’t happen. It came back again with all the old sliders in tact, the warning message still showing, but the plug-in page seemingly indicating that I had the most up to date version

Wordfence had a link to restore the old file (some previous code). I clicked these and the warnings went away, but the caption was still displaying at the top and ruining the way the images had been built

I’ve duly decided to simply delete the captions now and treat it as a broken function. Visually it works, albeit it’s clearly sub-optimal, but I somehow suspect that this isn’t the correct answer and if there is something more sinister lurking around the plug in, then it might not have gone away?

I deactivated it, and deleted the plug-in, reinstalled it, and it’s made no difference. The captions still on the top of the image and are now taking about 10 times longer to load

Just quickly then, to prevent me making an error. Is this a short code that should be used to replace the existing one in amongst the HTML? or is it something that I should try and insert elsewhere in a function file? I’m guessing its the former, but I did crash all three sites once mucking about with PHP and have be too scared to use it ever since

My host had deactivated the plug in for me and the functionality has restored. I note however that there is an update pending to be processed on the plug in. Is this a revision of the update that appears to have caused the issue? or is it likely the same one that didn’t complete fully the first time?

Tried that. Would I be correct to assume that your contact form doesn’t do send confirmations? Instinctively it just doesn’t look to be working either

I’ve got the same issue. Monsterinsights have pretty well shut the website admin down. Unfortunately asking me to use the contact form isn’t that much help either. How exactly are you even supposed to create an account to even begin communicating with you?

In answer to some of my own questions. I naviagted to the page that has the Rubic Cube on it and clicked on Firebug. From there I clicked on the tab called ‘script’ and that brought up a series of what looks like PHP with line numbers. This seemed to be consistent with how the other enquiry was resolved. I couldn’t however see anything that screamed error at me. Is there a way of isolating errors, or do I have to spot them?

The best candidate I can come up occurs on line 7 and 8 and has something to do an ajaxError and name checks Wordfence and something called AJAXWatcher block warning

Ok, I’ve downloaded it from your link, installed, activated, but it appears to be DOA. All I get is a Rubic cube twisting about. It’s as if I’ve got the paid version that needs Woo?

Many thanks for your guidance on this, I’ll try and get this working and if it works (or more to the point, if I can get it working!) I’ll happily consider paying the equivalent that the original Woo based platform would have cost.

Incidentally, I assume this wouldn’t be the place to ask any further questions? or would it?

I’ve got the same issue with the Pro version. The plug in is simply ignoring the box checks and tweeting out what ever it feels like doing