Sebastian

Hi Nick,

thank you very much for your super fast reply and the link to your integration plugin.
I will definitely check it out and try to add the functionality!

Best,
Sebastian

Working as hoped with “page attributes”!
Thanks for the support and valuable input!
Please keep up your great work with ASE!

Thank you very much for the quick answer and solution! It never crossed my mind that it is so easy. Are there any drawbacks one should consider when converting a normally non-hierarchical post type (a team member should not be able to have “sub-members”) to a hierarchical post type?

Great plugin! I’m a happy user of the pro version!

Hallo Torsten,

vielen Dank für den Hinweis. Auf den beiden betroffenen Seiten war tats?chlich das Standard-Tracking in Kombination mit Page-Caching konfiguriert. Ich habe die Einstellungen korrigiert und werde die Werte die n?chsten Tage beobachten. Ich bin mir aber sicher, dass das Problem damit gel?st ist. Danke für die schnelle Hilfe!

Viele Grü?e
Sebastian

Hallo Torsten,

vielen Dank für die schnelle Reaktion.

Hier der Link zu einer der Seiten: https://www.winkler-online.de/

Am 13.01.23 sind die Aufrufe von ca. 250 am Vortag auf 8 gefallen. Seit diesem Tag werden für die Seite maximal 65 Aufrufe angezeigt. Davor lag der Schnitt bei ca. 200-250 Aufrufen. Die Search Console zeigt durchgehend ca. 200 Impressionen, ohne einen erkennbaren Abfall zum genannten Datum.

Am 11.01. wurde das Plugin Yoast SEO von der Version 19.13. auf 19.14. aktualisiert (inzwischen auf 20.1). Ansonsten gab es an der Seite keine ?nderungen.

Viele Grü?e
Sebastian

Hi!

The problem with v1.0.7 was solved for us by deactivating and reactivating the plugin. Now the plugin works as expected again, not sending entries directly to spam.
Thanks for the update!

Kind regards

Version 1.0.7. also didn’t fix the spam issue for our website.
New entries keep going straight to spam, with no notifications sent and no redirects after form submission.

Thanks for your help in advance!

Hi Hannah, Hi Ben,

thanks for getting back with me concerning the problem.
Indeed it had to do with the asset optimization configuration.
We never had issues with these settings, so it didn’t come to my mind, that this could be the source of the problem. Thanks for pointing me in the right direction.

Sebastian

Hi Ben,

did you have the chance to check your email yet?
Haven’t heard back from you.
Thanks for a quick feedback.

Sebastian

Hi Ben,

I just sent you an email with screenshots and further informations.
Please check your inbox and let me know if you can track down the issue.
Thanks!

Sebastian

I found a solution for this problem:

The row layouts that had the above mentioned layout problems were set to ‘Vertical Align Middle’. I had to set them back to ‘Vertical Align Top’ to get them back to display correctly after the update to v1.7.17.

Thanks Ben for your help!

Thanks Ben,

to make the dots visible in the frontend I had to add the following CSS:

.kt-blocks-carousel .slick-dots li button:before {
	content: '';
}

This will be added in the next update.

Thanks for your support!

Hi Ben,

yes I always do a hard refresh in Chrome after any changes in the backend.
This is really strange because it definitely seems to be connected to v1.7.17.
When I downgrade to v1.7.16 the frontend display is correct again.

In another post I also mentioned an issue happening on another site where a headline is positioned next to a carousel instead of being above the carousel after the 1.7.17 update. Same scenario here – if I downgrade to v1.7.16 the headline is in the correct position again.

Again, this only happens in the frontend. Backend editor is always correct.

Maybe it has something to do with the Theme-Plugin constellation. It is the same on both installs I mentioned. I didn’t have the time to test other sites yet.

Sebastian

Hi Ben,

I’m not using any caching or minify plugins on this site since it’s still in development.
I always do a hard refresh in Chrome after any edit in the backend.
I can provide admin access for you to check.
How can I send login details as private?

I just double checked:

Switching back to v1.7.16 puts the headline above the gallery carousel like it’s set up in the backend editor.

WordPress 5.3.2
GeneratePress 2.4.1
Gutenberg 7.3.0
Kadence Blocks 1.7.17 > now back on 1.7.16