Ted

I had a few minutes to take a quick look at this, and my theory about the proximity of the “Purge SG Cache” element doesn’t appear to be valid, and relocating the anchor point for the global ditty doesn’t seem to be viable for my desired location within the theme; however, adding the custom CSS…

.ditty-ticker { display: block; }

… seems to be the most efficient resolution.

I don’t understand what I perceived to be a consistent link between the issue and whether the SG Optimizer plugin is activated, but the custom CSS resolves the case of the disappearing Ditty.

Thank you for your assistance.

That’s interesting. I’m using a global ditty placed in the header for replication on all website pages. The SiteGround Optimizer plugin adds a clear cache button to the WP Admin toolbar. It makes sense now that these elements could interact.

Thanks for your recommendations of custom css options. I also suspect locating a different anchor point for the global ditty could also resolve the issue.

I hope to investigate further later this week. And I will post back with my results.

Thank you.

I have identified a plugin conflict with SiteGround Optimizer, but I have not yet determined which component of SiteGround Optimizer creates the conflict.

I don’t see any errors in the console log of the inspector within Firefox; however, I may have identified a property which is affected.

In inspector for the ticker, looking under

<div class="ditty ditty-ticker"

If I drill down to the css properties specified in ditty-displays.min.css… and I use the checkbox in inspector to disable or comment out “display:flex;” so the resulting css in the style-editor tab is as follows…

.ditty {
  /*! display:flex; */
  flex:1;
  flex-direction:row;
  flex-wrap:wrap;
  position:relative;
  width:100%;

…then the ticker works properly while I’m viewing the page through inspector. Of course when I close inspector and reload the page, the ticker content disappears again.

I hope this makes more sense to you than it does to me.

• This reply was modified 1 year, 2 months ago by Ted. Reason: code didn't appear as expected

Interesting additional observation today. Seemingly randomly, I am unable to add a focus keyphrase to some posts without getting a similar error when trying to publish the post:

POST
	https://redacted-hostname/wp-admin/post.php?post=5124&action=edit&meta-box-loader=1&meta-box-loader-nonce=ce8a318cfd&_locale=user
Status
400
Bad Request
VersionHTTP/2
Transferred89.75 kB (89.48 kB size)
Referrer Policystrict-origin-when-cross-origin

Hello @wpsmort,

Any updates? Has the behavior I’m seeing been replicated?

Hello @arnaudbroes,

Interesting – please do keep me posted.

Thank you.

I decided to spin up another site – this time on TasteWP – and I don’t see an issue there. I wonder if this is somehow related to sites hosted on SiteGround.

:Confused:

Hello Prabhat,

Run Shortcodes is NOT enabled.

I followed the instructions to enable debugging, but no debug.log file was created. I manually created one and set permissions 755, and it is not being updated.

When trying to post the Vimeo iframe url, upon publishing the post or saving a draft, there is an error in the Firefox console which does not occur with AIOSEO disabled:

XHRPOSThttps://redacted-hostname.sg-host.com/wp-admin/post.php?post=17&action=edit&meta-box-loader=1&meta-box-loader-nonce=0c61588117&_locale=user
[HTTP/2 400 Bad Request 118ms]

	
POST
	https://redacted-hostname.sg-host.com/wp-admin/post.php?post=17&action=edit&meta-box-loader=1&meta-box-loader-nonce=0c61588117&_locale=user
Status
400
Bad Request
VersionHTTP/2
Transferred89.72 kB (89.48 kB size)
Referrer Policystrict-origin-when-cross-origin

Hello Prabhat,

Thanks for your reply. I have some additional information but ran out of time to get all the details I wanted. I have confirmed the issue occurs on a new WordPress site with only the bare minimum components installed.

A general outline of steps to duplicate the issue…

1. Spin up new WordPress installation.
2. Download, install, and activate the Exodus theme from ChurchThemes.com
3. Download, install, and activate the Church Content plugin.
4. Download, install, activate and configure the AIOSEO plugin.
5. Deactivate and remove all un-necessary plugins – particularly the Monster stuff.
6. From the WordPress admin console go to Sermons – Add New.
7. Create a title and short description.
8. Copy and paste Vimeo embed code into the Sermon Media – Video field.
9. Publish the page.
10. The video does not appear.
11. Click Edit Sermon.
12. Scroll down and the pasted Vimeo embed code is gone.
13. Disable AIOSEO.
14. Repeat steps 6 through 9 and the video posts normally.

I have also checked with the PDF embed field and the same problem occurs. It appears that recent patches to address the cross site scripting vulnerability may have resulted in disabling any meta boxes that appear in the editor page below the AIOSEO fields.

I hope this help. I also hope to have more time to test this evening. Please let me know if you are able to reproduce and troubleshoot the issue.

Thank you.

Thank you, Yann. This is good news, especially the local by default for block themes! I will definitely check out the update.

Hello Ash,

Thanks for the follow-up. I still haven’t learned much about PHP, though I find myself having to figure out some CSS. I guess I’m looking for this “no-code” solution of Full Site Editing but often finding some form of code and/or plugin is required for many tasks.

There are also a couple of plugins mentioned in the WP Tavern article I referenced above which I’m also going to try.

Thanks,
Ted

Sorry. Newbie here. Forgot to check the box to be notified of replies via email and just learned I can’t do that after the fact with an empty post.

I would like to use Twentig, but I’m concerned about using Google hosted fonts. I just read the article on WP Tavern where, “www.ads-software.com Strongly Urges Theme Authors to Switch to Locally Hosted Webfonts.”

Do you have plans to allow Twentig to host fonts locally rather than relying on Google’s CDN? Also perhaps support hosting custom fonts as part of the plugin?

I have found something that works, but there must be an easier way! It appears the cover block overlays the content with a transparent background layer (background-dim) which blocks clicking on links behind the layer.

@media screen and (max-width: 700px) {
	#page-cover-block {
		display: contents !important;
		padding-left: 0px !important;
		padding-right: 0px !important;
    }
	.wp-block-cover-image.has-background-dim:not(.has-background-gradient)::before, .wp-block-cover-image .wp-block-cover__background, .wp-block-cover-image .wp-block-cover__gradient-background, .wp-block-cover.has-background-dim:not(.has-background-gradient)::before, .wp-block-cover .wp-block-cover__background, .wp-block-cover .wp-block-cover__gradient-background{
		opacity: 0;
		z-index: -1 !important;
	}
	.wp-site-blocks {
		padding-left: 0px;
		padding-right: 0px;
	}	
}

I’m concerned that the complexity of this custom CSS could come back to haunt me later.

Since my original question has been answered and I have a working resolution for the resulting problem of navigation links not working, I will mark this as resolved. However, I’m open to suggestions of a better resolution.

Thanks,
-taw

**Update**
I believe I have replicated the issue on this test site: https://melodicbottle.s4-tastewp.com/

Some of my edits are not yet available on my mobile device, but I think that’s a caching issue. When the media query kicks in and changes the display mode of the cover block the navigation links in the header no longer work.

I hope this helps identify the issue.

Thank you,
-taw