miarr0wporg

Thank you, you might be right. I rolled back Neve, but not Orbit fox. Thanks for the link!

I recreated the affected post grids using a new (or renamed old) Elementor widget. I don’t know what originally caused them to vanish, but I found a solution that worked.

Hi Stefan, thank you, I already tried. It wasn’t a Neve problem after all, but an Elementor problem (or an Orbit fox problem, as Rodicaelena pointed out here). I recreated them using an Elementor widget, and everything looks fine. Sorry for adding to your work load.

• This reply was modified 3 months, 3 weeks ago by miarr0wporg.

This question was moved by an admin to this forum. Since I am a Pro-User I got help from the support. For those who experience something like this: Apparently the post type grid widget I used when I created the pages was an Orbit fox widget, that for some reason doesn’t show in Elementor any longer.

https://github.com/Codeinwp/themeisle-companion/issues/878

• This reply was modified 3 months, 3 weeks ago by miarr0wporg.
• This reply was modified 3 months, 3 weeks ago by miarr0wporg.

Adding this after a rollback: It didn’t help. All the custom post type lists are simply gone. I don’t know what to do. It’s not that they’re there when I try to edit the pages in Elementor and just don’t show, they are gone. Has anybody else had this happening? Any ideas?

RTL probably means right to left writing direction (as used in Arabic e.g). That would require a different layout, hence two css files. Just an uneducated guess.

If the update to version 3.8.15 was supposed to fix the problem: It didn’t.

I used Elementor to create the landing pages, and I simply don’t remember how I created those specific elements. If I remember correctly I used Otter and something called a “post type grid” to insert something like “show latest blog posts”, I used the options available to make them look like cards with the title, the featured image and a few lines of text. On this page https://resinrapture.com/dollfamily/ all the post preview cards below or next to the family names vanished. When I run an inspect on the section, there seems to be a problem with a “flex” definition, but I can’t even find the elements in the inspect-window. I hope this helps. When I open the pages in Elementor, the container where the grid was appears to be empty.

• This reply was modified 4 months ago by miarr0wporg.

Thank you for asking, it seems to work now.

Thank you, I will check that.

Thank you!

I am sorry for all the posts, but I found this in the support forum of wp fastest cache. I hadn’t set the cache time out, and it looks as if that might have caused the problem. So I guess you were right about a connection.

https://www.wpfastestcache.com/tutorial/wordpress-nonce-cache/

I will try this setting and reactivate the plugin, and hope this will help. Maybe even others who have the same problem ;)-

• This reply was modified 1 year, 4 months ago by miarr0wporg.

I just found an answer to a previous topic:

https://www.wpfastestcache.com/tutorial/wordpress-nonce-cache/

I hadn’t done that, so I will reactivate and try if that works first.

@threadi

Unfortunately I have another “problem” when deactivating the plugin, my site health check tells me it should be improved by using a cache plugin. I just don’t know how to solve both problems.

@threadi Thank you for the suggestion. I actually installed the plugin about a year ago to solve the first series of this particular problem, and it seemed to work. I will try it the other way round now. What I also tried is deleting all blocked emails from spammers and changing the avatar for those without their own.

ETA: I deactivated the plugin and a test comment seems to work.

Would you be so kind to try on this post? I approve manually, but when you get the message “comment submitted” it worked (and I can see it waiting for approval). I will delete it, but I know it worked then. Thank you!
Testing post

• This reply was modified 1 year, 4 months ago by miarr0wporg.
• This reply was modified 1 year, 4 months ago by miarr0wporg.

@hardeepasrani You are right. Deactivating Gutenberg did the trick. Thank you!