Search Results for 'cache'

[joaojacko010]

joaojacko010

#290472

f the date is not appearing on Google search results for posts using the Kadence theme, it might be due to how the theme or your WordPress setup handles date metadata. Here are some steps to ensure the date is visible:

Enable Date Display in Theme Settings:

Go to your WordPress dashboard.
Navigate to Appearance > Customize.
Look for the Blog Post Settings or Single Post Settings (this might vary slightly depending on the exact version of the Kadence theme).
Ensure that the date is enabled to display on posts.
Use Structured Data Markup:

Google often relies on structured data to display dates in search results. Ensure your theme uses proper structured data for posts.
You can use plugins like Yoast SEO or Schema Pro to add or enhance structured data.
Check Post Metadata:

Edit a post in WordPress.
Ensure that the publication date is set and visible in the post settings.
Ensure Proper Date Format:

Sometimes, the date might be set but not in a format recognized by Google. Ensure it follows the standard date format (e.g., YYYY-MM-DD).
Update or Regenerate Sitemap:

If you’ve made changes, update your XML sitemap and submit it to Google Search Console.
Navigate to Yoast SEO > General > Features and ensure the XML sitemaps feature is enabled.
Go to Google Search Console, select your property, and resubmit the sitemap.
Check for Caching Issues:

Sometimes, caching plugins or server-side caching might prevent updates from reflecting. Clear your website cache and server cache.
Manual Date Check:

If you’ve recently updated the date settings, it might take some time for Google to recrawl and index your posts with the updated date information.
By following these steps, you should be able to troubleshoot and resolve the issue of dates not appearing in Google search results for posts using the Kadence theme.

Additionally, if you’re looking for quality entertainment while managing your website, consider downloading the LokLok APK app. LokLok offers a seamless experience for watching and sharing precious videos. It provides an extensive library of movies and shows, ensuring you have quality entertainment at your fingertips.

You can download the LokLok APK app. The app is user-friendly and perfect for unwinding after working on your site. Highly recommend checking out LokLok APK to enhance your digital experience!

[Eze]

Eze

#290251

Hi there,

Glad you reached out, happy to help.

Your website doesn’t appear jumped on my mobile phone. Here is a screencast for your reference:
https://share.zight.com/wbuxBovA

To troubleshoot this, please clear your browser cache on mobile:
https://supportcenter.lexisnexis.com/app/answers/answer_view/a_id/1080838/~/%E2%96%B6%EF%B8%8F-clear-cache-and-cookies-on-most-common-mobile-browsers

See more troubleshooting steps:
https://www.kadencewp.com/blog/how-to-troubleshoot-your-website/

I hope this helps. Please let us know how we can help further.

Cheers,
Eze

[Eze]

Eze

#290219

Hi there,

Glad you reached out, happy to help.

I am unable to replicate this issue. Here is a screencast of me adding the Kadence Accordion Block and the panes opening and collapsing as expected:
https://share.zight.com/o0uLJ2YR

To troubleshoot this, please clear your website and browser cache and also check for plugin conflict:
https://www.kadencewp.com/blog/how-to-troubleshoot-your-website/

I hope this helps. Please let us know how we can help further.

Cheers,
Eze

[Solace]

Solace

#290204

Hi there

today 27/6/24 @ 10.15am NZST I upgraded to the latest plugin updates and now getting a weird blocks javascript error;

TypeError: Cannot read properties of undefined (reading ‘length’)
at kt (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:47438)
at Vt (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:51285)
at Bt (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:51447)
at Object._t [as useSyncExternalStore] (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:49847)
at e.useSyncExternalStore (example.com/wp-includes/js/dist/vendor/react.min.js?ver=18.2.0:10:10112)
at Qe (example.com/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:2876)
at Ye (example.com/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:3157)
at ZS (example.com/wp-includes/js/dist/block-editor.min.js?ver=868d782fcb169133c92b:26:557337)
at wt (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:47637)
at vr (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:56452)

This happens when trying to using the block builder in a new post or page, have tried with Chrome, Edge, Opera and tried switching PHP to 8.1 (was 8.2) and 8.3. Same issue.

To isolate the issue, I cleared cache everywhere, deactivated all plugins etc, followed all steps, even reinstalled WP. I found the issue to be with the kadence blocks or blocks pro – I was not able to find the root cause – appears to be a react issue. But when deactivated, the issue no longer occurs. Obviously inconvenient not to be able to use blocks pro so please advise fix.

Video: *Login to see link

Kadence Blocks – PRO Extension: Version 2.3.11
Kadence Blocks – Version 3.2.46
WordPress – 6.5.5
Kadence Theme – 1.2.6

Chrome Dev Console:

Error: Minified React error #311; visit *Login to see link for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at zt (react-dom.min.js?ver=18.2.0:10:48516)
at Object.useState (react-dom.min.js?ver=18.2.0:10:116562)
at e.useState (react.min.js?ver=18.2.0:10:10043)
at zp (components.js?ver=761379c942a778958fa1:28:77066)
at B (element.min.js?ver=cb762d190aebbec25b27:9:6435)
at Z (element.min.js?ver=cb762d190aebbec25b27:9:7430)
at Y (element.min.js?ver=cb762d190aebbec25b27:9:6890)
at B (element.min.js?ver=cb762d190aebbec25b27:9:6189)
at Z (element.min.js?ver=cb762d190aebbec25b27:9:7430)
at Y (element.min.js?ver=cb762d190aebbec25b27:9:6890)
ar @ react-dom.min.js?ver=18.2.0:10

[Solace]

Solace

#290204

Hi there

today 27/6/24 @ 10.15am NZST I upgraded to the latest plugin updates and now getting a weird blocks javascript error;

TypeError: Cannot read properties of undefined (reading ‘length’)
at kt (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:47438)
at Vt (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:51285)
at Bt (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:51447)
at Object._t [as useSyncExternalStore] (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:49847)
at e.useSyncExternalStore (example.com/wp-includes/js/dist/vendor/react.min.js?ver=18.2.0:10:10112)
at Qe (example.com/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:2876)
at Ye (example.com/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:3157)
at ZS (example.com/wp-includes/js/dist/block-editor.min.js?ver=868d782fcb169133c92b:26:557337)
at wt (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:47637)
at vr (example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:56452)

This happens when trying to using the block builder in a new post or page, have tried with Chrome, Edge, Opera and tried switching PHP to 8.1 (was 8.2) and 8.3. Same issue.

To isolate the issue, I cleared cache everywhere, deactivated all plugins etc, followed all steps, even reinstalled WP. I found the issue to be with the kadence blocks or blocks pro – I was not able to find the root cause – appears to be a react issue. But when deactivated, the issue no longer occurs. Obviously inconvenient not to be able to use blocks pro so please advise fix.

Video: *Login to see link

Kadence Blocks – PRO Extension: Version 2.3.11
Kadence Blocks – Version 3.2.46
WordPress – 6.5.5
Kadence Theme – 1.2.6

Chrome Dev Console:

Error: Minified React error #311; visit *Login to see link for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at zt (react-dom.min.js?ver=18.2.0:10:48516)
at Object.useState (react-dom.min.js?ver=18.2.0:10:116562)
at e.useState (react.min.js?ver=18.2.0:10:10043)
at zp (components.js?ver=761379c942a778958fa1:28:77066)
at B (element.min.js?ver=cb762d190aebbec25b27:9:6435)
at Z (element.min.js?ver=cb762d190aebbec25b27:9:7430)
at Y (element.min.js?ver=cb762d190aebbec25b27:9:6890)
at B (element.min.js?ver=cb762d190aebbec25b27:9:6189)
at Z (element.min.js?ver=cb762d190aebbec25b27:9:7430)
at Y (element.min.js?ver=cb762d190aebbec25b27:9:6890)
ar @ react-dom.min.js?ver=18.2.0:10

[mattjameslondon]

mattjameslondon

#290190

that’s so strange, both issues are still showing for me on mobile. I’ve tested it in various browsers and cleared the cache, so I guess it must be something to do with the device? I’ll see if I can test on a different device. Thanks for your help anyway.

[kristin.williams]

kristin.williams

#290042

I fixed it through directions from Kadence to remove and add plugins. I discovered in test mode that the free version of the blocks would load, but then if I activated the pro plugin add-on it would stop working. After removing and re-adding and then clearing browser cache and website cache I got it to work. Fast forward after more edits… had the same problem again. However, this is the interesting part, I have now found a browser compatibility issue. I was using Mozilla as my default browser and this was where I was having issues. When I log in to my website using Chrome instead, then I am not getting this error. How does this makes sense, this is above me! But it continues to happen. So I advise, try switching browsers and see if the problem persists. Also, Kadence… please test your product on Mozilla as maybe there is some script loading issue??

• This reply was modified 1 year, 10 months ago by kristin.williams.

[Karla]

Karla

#290029

Hi, Michelle.

There are a couple of errors (400 and 500). The 400 error can have numerous causes, but it might be mainly because of incorrect URLs. Error 500 on the other hand, is more related to the server.

Here are some posts to refer to:
– https://www.prontomarketing.com/blog/how-to-fix-400-bad-request-error-wordpress/
– https://www.cloudways.com/blog/wordpress-500-internal-server-error/

To fix these, you may reach out to your hosting provider and ask for a copy of your website’s PHP error logs. This will give us more information and trace of the errors.

Also, try to flush your permalinks:
1. Go to Dashboard > Settings > Permalinks.
2. Click the “Save Changes” button right away, no need to change anything.

Lastly, clear or purge any website cache you have enabled.

I hope this helps, and let us know how it goes. You may also submit a premium support ticket here.

Regards,
Karla

[architabasandrai]

architabasandrai

#290007

Hi @saggausackeym,

I tried to recreate the issue you mentioned, but couldn’t replicate it. I can edit/customize the pages and posts at my end without any error. You can refer to the screencast for reference: https://share.zight.com/ApumDPYy

Currently, I am using latest version of Kadence plugins and themes.

To troubleshoot, please follow these steps:

• Try to deactivate the plugins one by one and see if there is any plugin that is causing conflict. Check this article to troubleshoot: https://www.kadencewp.com/blog/how-to-troubleshoot-your-website/
• Can you check for console errors you are getting while trying to load the second page? Check this article to troubleshoot: https://www.kadencewp.com/kadence-theme/knowledge-base/troubleshooting/how-to-view-console-log-errors/
• Check the article to clear the cache: https://www.kadencewp.com/kadence-theme/knowledge-base/troubleshooting/clearing-your-website-cache/
• Check the article to clear the browser cache and cookies: https://support.google.com/accounts/answer/32050?hl=en&co=GENIE.Platform%3DDesktop

Could you give us your actual website URL so we can check the issue at our end?

Please let us know how it goes.

Regards,
Archita

[chitocamacho]

chitocamacho

#289995

Hey Matt,

Thanks for writing in.

I tested it on my website, but was unable to replicate the issue.

Can you please send here the link to the page, so I can check the frontend?

In the meantime, please clear website and browser caches and recheck it on your mobile browser.

Thanks,
Chito

[chitocamacho]

chitocamacho

#289994

This reply has been marked as private.

[dmjhar]

dmjhar

#289101

This reply has been marked as private.

[Eze]

Eze

#289097

Hi there,

Glad you reached out, happy to help.

To better help with this, please send us a link to your website. You can check “Set as private reply” when replying with the link.

In the meantime, to further troubleshoot this:
1. Please test your site on multiple mobile browsers to identify if the issue is browser-specific.
2. Clear your website and browser cache:
https://www.kadencewp.com/help-center/docs/kadence-theme/clearing-your-website-cache/
3. Clear any server-side cache if you have access to it.

Please let us know how we can help further.

Cheers,
Eze

[chitocamacho]

chitocamacho

#289078

Hi Joanne,

Thanks for writing in.

I checked the website you referenced and indeed you have fonts that are not saved locally.

Kindly note that uploading fonts in Kadence Custom Fonts automatically saves them locally.

I see you’re using the Kadence theme. You can enable the “Load Google Fonts Locally” option in Customizer > General > Performance. Then, clear the website and server caches.

If the issue persists, kindly turn off the “Load fonts from Google Fonts?” option in WP Admin > Pricing Tables > Font Options.

The Kadence Slider also has that option. You can turn it off in WP Admin > Kadence Slider > Kadence Slider Fonts.

Then, clear the caches again and recheck it.

Please let me know how it goes.

Best,
Chito

[Michelle Jensen]

Michelle Jensen

#289047

Hey Karla,

Thanks for getting back to me about this. I actually set them to 400 x 400 a couple of weeks ago (see attached), so I’m awfully confused as to why it’s generating as 768 × 576 px. Do you have any ideas?

I’ve just gone in and manually regenerated the first two images on the slider with the plugin you suggested to ensure they were created to the 400 x 400 size. I’ve also cleared the cache.

[chitocamacho]

chitocamacho

#289005

Hi Marla,

Thanks for writing back.

If the mobile version looks fine on other devices, it could be the browser cache that’s causing the issue on your end.

Here’s a guide on how to clear the browser cache:
https://www.wikihow.com/Clear-Your-Browser%27s-Cache

If the issue persists on your end, please try checking it on a different browser or in an incognito window.

If it does not make a difference, can you send me a screen recording of how it’s displayed on your end?

Thanks,
Chito

[Karla]

Karla

#288965

Hi, Michelle!

Thanks for the file.

After more tests, I think the main reason for the CLS for mobile views is coming from your slider at the top of the home page.

To reduce the CLS impact, add this custom CSS code to the Row Layout block where you added the Post Grid/Carousel block:

@media ( max-width: 767px ) { 
selector .kt-post-grid-layout-carousel-wrap:not(.is-initialized) { 
 height: 409px;
 overflow: hidden;
} 
}

Here’s a screenshot of where you can find the setting – https://share.zight.com/Z4uNKWbY

After saving the changes, make sure to purge the WP Rocket cache.

I hope this helps, and let me know how it goes.

Regards,
Karla

[Nantz]

Nantz

#288913

Yes, I’m guessing you’re right: it’s a plugin conflict. This morning, the larger images suddenly reappeared in Chrome (!) even though I had replaced the slide images with the exactly-cropped ones. So, I purged the cache AGAIN, and all is well again—I hope.

The only plugin recently added is Quick View for WooCommerce by ShapedPlugin LLC.

When I added it, Ii did wreak some havoc by vanishing all the other site icons (like arrows at product titles, the menu icon on mobile, etc). I was able to resolve the problem when I found an old reply in this forum (to another issue!) by Hannah with this code:

/*this shows site icons again that Quick View plugin wipes out!*/
}
[class^=”icon-“]:before, [class*=” icon-“]:before {
font-family: virtue_icons;
}

Since it’s the only thing recently changed, I’m guessing it somehow had some effect on the Home Slider too? (because both seem influenced by jquery? I don’t know that code, so can’t be sure, but have noticed other comments along those lindes about Quick View).

Anyway, will mark this question as resolved now. Thanks for your response!
~n

[Michelle Jensen]

Michelle Jensen

#288885

Hey Karla,

Thank you so much for your response and detailed explanation I’m still learning here, haha.

I gave your suggestion a try and I’m still seeing the layout shift error when I run a test. I’ve cleared the cache too.

https://pagespeed.web.dev/analysis/https-www-travelherstory-com/x11nvuynie?form_factor=mobile

[Eze]

Eze

#288882

Hi there,

Thank you for reaching out and providing such detailed information about the issue you experienced. I am glad to hear you found a workaround by creating new images for your home slider.

The discrepancy you are seeing between Chrome and the other browsers (Safari and Firefox) is likely due to differences in how these browsers handle CSS and image rendering. Since you have updated the images, I can’t test the slider in these browsers directly.

In the meantime, you mentioned that the slider’s max height and width are larger on Safari and Firefox. Here are some possible reasons and solutions:
1. Cache: Your browser or website cache might be holding onto old CSS rules. Clearing the cache can often resolve display issues.
2. Plugin Conflict: A plugin might be overriding the settings. Temporarily disabling the plugins one by one can help identify any conflicts.

I hope this helps. Please let us know how we can help further.

Cheers,
Eze

[kristin.williams]

kristin.williams

#288881

I was having this same error – based on the last comment I realized the only change was going from 8.0 to 8.3 PHP. I downgraded to 8.2 PHP and opened in new browser to deal with cache, it seems to have fixed the error. Is there some compatibility issue with the latest version of PHP?