aapc
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Virtue] Kadence Blocks plugin can’t updateHi @shaunshaun,
I’m glad you reached out. I’ll be happy to help!
The “Could not create directory” error typically points to one of two common server issues:
- Full Disk Space or Quota Limits: Your hosting account might be out of disk space.
- Folder Permissions: The server might be blocking WordPress from writing new folders inside your site’s directory.
I would recommend reaching out directly to your hosting support team. You can share this exact error message with them, and they should be able to clear up the space or reset the permissions for you very quickly. Let us know how it goes!
Thanks,
AnthonyForum: Themes and Templates
In reply to: [Kadence] .css code seems to have stopped workingHi @larissa67,
I’m glad you reached out. I’ll be happy to help!
To override the default theme spacing, you can use the following custom CSS to your Customizer Additional CSS area:
:root {
--global-md-spacing: 0.5rem;
}Give that a try and let us know if that works for you.
Thanks!
AnthonyForum: Themes and Templates
In reply to: [Kadence] Spacing HelpHi @larissa67
Thank you for clarifying. The screenshot was very helpful!
The spacing your are seeing is due to the fact that the WP Group (when using Kadence) has a default bottom margin. To change it, select the group (not the text inside the group) and click the Styles tab in the settings. Scroll down to the MARGIN section where you’ll see a slider. You can either drag it to the middle and back to the left to set it to none, or you can click the “Set custom size” to the right of the slider and manually set the margin size. To control the top/bottom margins separately, click the “Unlink” icon just above the field to view separate controls. (view screenshot here).
I hope that helps! Please let me know if you have any trouble or if we can do anything else to assist.
Thanks!
AnthonyForum: Themes and Templates
In reply to: [Kadence] Spacing HelpHi @larissa67
Just checking in on this issue. It looks like you may have resolved the problem. If not, can you further describe the issue and/or provide a screenshot or screenshare? We often use Zight to make it easier to share (just copy/paste a link to your image/video).
If your issue has been resolved, please go ahead and mark this thread as resolved.
Thanks!
AnthonyForum: Themes and Templates
In reply to: [Kadence] User Support Forum – closed?Hi @alathea9
Anthony here. Yes, the old Kadence Forum was retired some time ago in favor of our direct support system. It remains accessible for historical purposes but I think you’ll find that the information is quickly out dated and may not apply to our current products.
For free products, you are welcome to post here on ww.wp.xz.cn or you can access our support directly here: https://www.kadencewp.com/help-center/free-support/
Of course, our documentation is always available 24/7 here: https://www.kadencewp.com/help-center/
I hope that helps!
Forum: Themes and Templates
In reply to: [Kadence] Menu updates and section anchors don’t workHi @alathea9
I’m glad to hear you’ve made progress on solving your issues. I know learning new things can be maddening. I’ve had to learn many new products over the years and I understand your frustration. I do hope you’ll stick with Kadence. Yes, there are many things to learn. But just like any theme, plugin and even WordPress, it becomes much easier the more you use it.
In the future, for quicker responses, I would suggest submitting a ticket directly to us here: https://www.kadencewp.com/help-center/free-support/
I wish you all the best!
AnthonyForum: Themes and Templates
In reply to: [Pinnacle] Footers Not WorkingI’m sorry I do not have a timeline on the next release for Pinnacle. Being a “classic” theme, the priority for non-security issues is somewhat lower than our current products. Your best bet would be to stay with 1.8.8 for the time being.
Thanks!
AnthonyForum: Themes and Templates
In reply to: [Kadence] Menu updates and section anchors don’t workHi @alathea9
That’s a lot to follow! But I’ll try! 🙂
The first thing to clarify is the use of the term “header”. Kadence has a header builder that’s built into the theme and configured via the Customizer. You could call the the “Classic” header. With the advent of WordPress’ Full Site Editing (FSE) environment, we introduced a new header builder we called the “Advanced Header”. This created a new type of header that allows you to use standard editor blocks rather than the fixed blocks included in the classic header. We have a good document on this here: Using Advanced Header / Navigation Blocks vs Kadence Theme Header Builder. If you’re building a simple one-page site, it may not be necessary to use the Advanced Header as the classic header can easily handle this. But the Advanced Header works great too! Here’s another good document that might help: How to use Advanced Headers Globally and Conditionally.
For the anchor issue…it looks like you have your HTML anchor set correctly for your Row Layout blocks. Step 2 is to correctly configure your button. I can see by your screenshot that you’ve added “contact” to the button HTML anchor. This is incorrect. You first need to remove that and then set the button link to #contact. See the this edited screenshot. Note that all HTML anchors (also known as IDs) must be unique on a page. So if you have two “contact” anchors, the button linking to #contact will not work properly.
I hope the above helps clarify some of the issues you are having. Tutorials and AI are great but they can sometimes lead you down a rabbit hole if you’re not careful. I’ll be glad to provide some more guidance and/or documentation if you need it. And be sure to visit our Resource Hub for more help.
Thanks,
AnthonyForum: Themes and Templates
In reply to: [Kadence] Menu updates and section anchors don’t workHi @alathea9
I’m sorry you’re struggling with getting your menus working. I’m trying to follow along to identify where exactly you are having an issue. I’ll do my best to cover the possible issues to check.
First, a little direction on how to show/hide the header on an individual page. While the Customizer will allow you to set global settings (i.e. settings for every page or post), you can set individual page features by editing the page and clicking the Page Settings icon in the upper-right of your screen (near the Publish/Update button). Here’ a quick screenshare that shows you how: https://share.zight.com/jkuGX9DB
As for the menu anchors, it’s not clear on which menu system you are using and perhaps this is where the disconnect is occurring. If you’re using the classic headers (i.e. edited via the Customizer) then you would typically edit the menu via Appearance → Menus. However, if you are using the Kadence Headers, you may need to edit your menu by going to Kadence → Navigations. While you can import classic menus into Navigations, the two are separate and distinct. Editing one will not update the other.
Here is a doc link that might help: The Kadence Navigation (Adv) Block
See also: The Kadence Navigation BuilderI hope that helps! If you’re still having trouble, please take a minute to explain how I can recreate the issue on my end and I’ll see if I can identify the point of failure. I’m sure we can get this working.
Thanks,
AnthonyForum: Themes and Templates
In reply to: [Kadence] Header issueHi @alathea9
Thank you for following up. I can certainly understand how frustrating it is to feel like the tools you’re using are “hiding” things from you, especially when you’re deep into the design process.
To clear up any confusion: our product design does not use AI to decide when to hide or show settings. What you’re experiencing is “Conditional Logic.” Our developers purposely designed the interface this way to prevent the sidebar from becoming a mile-long list of irrelevant settings.
For example, in the Header (Adv) block, the sidebar changes based on your Background Type selection:
- Color: Only shows color pickers.
- Gradient: Shows color sliders, type and angle.
- Image: When an image is uploaded/selected shows “Fill,” “Contain,” and “Cover”, etc…
Without an image selected: https://share.zight.com/9Zu1mbbO
With an image selected: https://share.zight.com/p9uJ6W0YIf those settings vanished, it’s usually because the “Background Type” was toggled back to Color or the image was cleared. To find the background image settings again:
- Select the Header (Adv) Block (or the specific Row inside it).
- Go to the Style tab in the sidebar.
- Ensure Background Type is set to Image.
- Once an image is selected, additional options are shown where you’ll find Image Size (Cover, Contain, Auto), Attachment, and Position.
As requested, here is the primary documentation for the Header (Adv) block which outlines the various tabs and where settings live:
- The Kadence Header (Adv) Block Guide
- Creating Sticky and Transparent Advanced Headers (This is helpful because “Transparent” and “Sticky” states have their own separate background tabs that appear only when enabled).
We strive to make Kadence intuitive, but we know “context-sensitive” design has a learning curve. If you find yourself stuck in the future, please let us know and we can provide screenshots and/or screenshare to point you in the right direction! For self-help, our Resource Hub is a great place to start.
Please let us know if there is anything else we can do to help.
Thanks!
AnthonyForum: Themes and Templates
In reply to: [Kadence] Header issueHi @alathea9,
I responded to your other thread. Please close this one when you have a moment.
Thanks!
AnthonyForum: Themes and Templates
In reply to: [Kadence] Header(Adv) width issueHi @alathea9,
I’m sorry to hear you had so much trouble! We don’t normally have support coverage over the weekend. I do see your other thread so it was definitely not deleted.
The Header (Adv) block doesn’t actually have a full-width option which explains why you didn’t find it in the documentation. In order to make the header full-width, you would insert it into a full-width container such as a Row Layout or Section block. The header would then fill 100% of the container (up to your max-width if you set one). So steps to do a full-width header:
- Insert a Section block
- Set the Section block to full-width
- Insert your Header (Adv) block into the Section
I hope that makes sense! Please let us know if you have any questions or if there is anything else we can do to assist. If you’re all set, please mark this thread as resolved (we cannot do that for you). If you would mark your other thread as resolved too, we would very much appreciate that as well.
Thanks!
AnthonyI have not been able to replicate your issue. If you’re still having trouble, feel free to open a ticket on the Kadence site for more in-depth support.
I’ll go ahead and close this ticket.
All the best!
Anthony@mirkolofio this was fixed in Kadence Blocks v3.6.5. Thank you for your patience.
I’ll go ahead and mark this as resolved.
All the best,
AnthonyHello @throwaway111
Thanks for reaching out and providing such a detailed report. We appreciate you taking the time to share these logs from your sandbox environment.
The notices you’re seeing are PHP 8.4 Deprecation Notices. Specifically, PHP 8.4 no longer allows “implicitly nullable” parameters. These are “Deprecated” notices, not “Fatal Errors.” Your site’s functionality remains intact, and these notices will not break your pages.
Since you have WP_DEBUG enabled, these notices are visible to help developers prepare for future PHP versions. On a live production site, we always recommend keeping display_errors off to prevent these from appearing to visitors.
Our team is continually working on auditing the codebase (including the StellarWP libraries used in both the free and pro versions) to ensure full compatibility with newer versions PHP. I assure you we are on the case!
Note that WordPress currently recommends PHP 8.3 and considers 8.4 and above as “beta” only. See here: https://make.ww.wp.xz.cn/core/handbook/references/php-compatibility-and-wordpress-versions/
Please let us know if you have any questions or if we can do anything else to assist.
Thanks!
Anthony