Hi @mesmer7
I’m glad you reached out. I’ll be happy to help!
Can you tell me which starter template you used? I would like to check it on my server to see exactly what is included.
On a related note, I have tried to manually migrate sites from staging to live and it rarely goes smoothly. Menus and sidebars in particular always seemed to be an issue. I would highly recommend looking into a migration plugin such as All-in-One WP Migration, WPVivid, WP Migrate or similar.
I hope that helps. Let me know which template you used.
Thanks!
Anthony
Hi Anthony, Thanks for the reply. I started with Print Shop, but then imported the home page from Outdoor Shop. Then of course, made a bunch of changes to that.
About the migration: It did NOT go smoothly. Took two days for me to get everything working on the live site. I have All-in-1, but I chose not to use it because I didn’t want to migrate the database. I’d tested a dozen themes and each one made a mess of my menus and widgets, plus all the images that I don’t need. So I’m sure my database tables in my development environment are a mess
-
This reply was modified 10 months ago by
mesmer7.
H @mesmer7
I’m glad to hear you got things working. And I’m very happy to hear that you went with Kadence!
I did confirm that several of our free starter templates do use legacy widgets. Some were most likely designed before sidebar blocks were standard and to ensure compatibility in either environment, legacy blocks were used. If you just need to export/import widgets, this is a good plugin: Widget Importer & Exporter
Please let us know if there is anything else we can do to assist.
Thanks!
Anthony
P.S. If you’re all set, please go ahead and close this thread. Thank you!
But you didn’t answer the important question: Why did they work on my development environment where I downloaded the starter template, and not on my live environment where I didn’t.
In my live site, I had to download and activate Classic Widgets plugin to get the widgets working, but I didn’t need that plugin in the development environment where I downloaded the starter template. Why?
What part of the starter template do I need to download to eliminate my dependence on the Classic Widgets plugin? And if I download it after I’ve got the site working, will it make a mess?
Hi @mesmer7
It’s possible that the Starter Template process may have code to properly handle the sidebars during import.
I imported the Print Shop Starter Template on a test site and most, if not all, of the legacy widgets have similar block replacements available. It might make more sense to replace the legacy widgets with blocks during development and before migrating to your live environment.
I will suggest to our developers that we re-visit some of the older templates and update them to include blocks.
Please let me know if you have any questions or if I can do anything else to help.
Thanks!
Anthony
Hi @mesmer7
Just a quick update. I heard back from our design team and they do plan on updating the starter templates and design library patterns. It will most likely be later this year before it’s done.
All the best,
Anthony
P.S. If you’re all set, please go ahead and close this thread. Thank you!
@aapc thanks for the update.
I’ve run into another weird bug, that suggests my migration method may have failed to include some important background code. So I think I might have to download the starter template to my live site anyway.
One of the pattern templates (hand chosen products) causes the block editor to crash in Firefox, but works perfectly in Chrome or Safari.
Hi @mesmer7
Apologies for the slow response. Are you referring to “Hand-Picked Products”? If so, I tried it on both Chrome and Firefox and I’m not able to replicate any crashes. Are you still having trouble with it?
Anthony
@aapc
Hi Anthony, Yes. I’m referring to Hand-Picked Products, and yes, I’m still having problems with this block refusing to load when editing an existing page in Firefox. Displays fine on the front end in all browsers. Loads fine on the back end in Safari and Chrome. But in Firefox, ‘almost’ every time I try to go back and edit a page where I’ve previously inserted this block, this block crashes the editor.
Hi @mesmer7
I have tested the Hand-Picked Products block on Firefox, Chrome and Safari and they all work as expected. I’m using the latest versions of Firefox, WooCommerce and WordPress. Here’s a screenshare showing the block in Firefox: https://share.zight.com/L1ulyzpp
Keep in mind that this is actually a WooCommerce block, not Kadence. That said, we do try to make sure popular third-party blocks perform well on Kadence sites but sometimes issues arise that are beyond our control. A few things you can try:
- Make sure WordPress, WooCommerce and your browser are all up to date.
- Clear your server and browser caches. See this doc for help with that.
- Check your browser console for errors. See this doc for help.
- Restart your browser and/or computer.
Since I can’t replicate the issue, it’s difficult to troubleshoot. You may need to reach out to WooCommerce support for additional assistance.
I hope that helps!
Anthony
Hi @aapc
I see two differences between what you did in that video and what I did.
First, you added the block from the block library. I added it from Kadence’s pattern library. I used Product Loop 21.
Second, I waited a week before going back to edit the page. The problem didn’t show up when I created the page. But showed up a week later when I tried to edit the page.
Hi @mesmer7
I imported the Product Loop 21 pattern and so far I haven’t been able to replicate the issue. When you do run into an issue, be sure to check your browser console log for errors. It’s not uncommon to see a few warnings, but errors should be marked in red. If and when you do see any errors, please copy and paste the error(s) or take a screenshot and post it here.
Just out of curiosity, what version of Firefox are you using? Mine is 139.0.1 on MacOS.
Thanks!
Anthony
Just my luck, today it’s working. However, I do see a dozen depreciation warnings.
wp.editPost.PluginSidebarMoreMenuItem is deprecated since version 6.6. Please use wp.editor.PluginSidebarMoreMenuItem instead. deprecated.min.js:2:582
wp.editPost.PluginSidebar is deprecated since version 6.6. Please use wp.editor.PluginSidebar instead. deprecated.min.js:2:582
wp.editPost.PluginPostStatusInfo is deprecated since version 6.6. Please use wp.editor.PluginPostStatusInfo instead. deprecated.min.js:2:582
wp.editPost.PluginPostPublishPanel is deprecated since version 6.6. Please use wp.editor.PluginPostPublishPanel instead. deprecated.min.js:2:582
__unstableIsPreviewMode is deprecated since version 6.8. Please use isPreviewMode instead. deprecated.min.js:2:582
wp.blockEditor.RichText onSplit prop is deprecated since version 6.4. Please use block.json support key: "splitting" instead. deprecated.min.js:2:582
Bottom margin styles for wp.components.ToggleControl is deprecated since version 6.7 and will be removed in version 7.0. Note: Set the __nextHasNoMarginBottom prop to true to start opting into the new styles, which will become the default in a future version. deprecated.min.js:2:582
downloadable font: Glyph bbox was incorrect (glyph ids 4 5 9 14 21 22 23 28 32 34 35 36 40 44 46 54 55 56 57 58 59 61 62 65 69 73 75 80 81 83 85 88 89 95 96 98) (font-family: "Rank-Math" style:normal weight:400 stretch:100 src index:0) source: https://www.hypnoticdreams.com/wp-content/plugins/seo-by-rank-math/assets/admin/fonts/Rank-Math.ttf?v1.0.94
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. wp-tinymce.js:3:8857
MouseEvent.mozInputSource is deprecated. Use PointerEvent.pointerType instead. wp-tinymce.js:3:8857
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://firefox-source-docs.mozilla.org/performance/scroll-linked_effects.html for further details and to join the discussion on related tools and features! post.php
I’m also using the latest versions of FireFox (139.0.1) and MacOS 15.5
Hi there,
This topic has been inactive for awhile.
Do you still need help here?
Please note Deprecated/Warning messages are not like fatal errors, so they should not affect the website functionality. Generally, they don’t break your site and are notices, not errors. Usually, the best way to stop receiving deprecation notices is to disable debugging: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
These are safe to ignore and are only showing up because of having wp-debug enabled in your wp-config.php file. You may want to disable wp_debug by adding the below code in the wp-config.php file:
define( ‘WP_DEBUG’, false );
If you have further questions or need additional assistance, feel free to start a new topic or refer to our Kadence Help Center here: https://www.kadencewp.com/help-center
Please note that you can also submit a support ticket via these channels.
Thank you for your understanding!
Kind Regards,
Michael Taro
