Forum Replies Created

Viewing 15 replies - 31 through 45 (of 148 total)
  • Thread Starter irishetcher

    (@irishetcher)

    Thanks Carlos. I will keep your suggestions in mind and look to the Pro version if we decide we need this level of granularity. Unfortunately explaining the set up for the North as a van diagram of two cultures is very complex, more complex than it needs to be.

    Thread Starter irishetcher

    (@irishetcher)

    Glad to hear I’m not the only one noticing this small issue.

    Thread Starter irishetcher

    (@irishetcher)

    Ah Hello!

    would you call that resolved?

    Thread Starter irishetcher

    (@irishetcher)

    Thanks for the prompt. I didn’t seem to be getting email notifications. I found a plugin to do this but, now I see Lorro’s suggestion above. I was tempted to change that 25 number but though it referred to something else!

    Cheers.

    Thread Starter irishetcher

    (@irishetcher)

    But…

    I distinctly know that on some of the sites that the Status panel was firmly present before the update, so the latest update definitely swapped in, what to my eyes, is a new setup panel.

    Very annoying!

    Thread Starter irishetcher

    (@irishetcher)

    Ok, you need to step through that setup process and then it transforms into the status panel.

    Very suspiciously though it looks very tricksy and sticky around the JetPack section.

    Thread Starter irishetcher

    (@irishetcher)

    Ok, so the my-account page is generated by WooCommerce on install. The shortcode [woocommerce_my_account] is added to the page and this in turn adds a login form and user related details when logged in.

    There are a number of things you can do. If you want to avoid customers having accounts you can delete the page, or, if you want to retain the page, change the permalink to something different, i.e. token-path-account.

    Thread Starter irishetcher

    (@irishetcher)

    At this stage I am just rolling with these browser alerts. But not good that the WP devs are not fixing it. Maybe because it is on the Classic Editor they don’t want to bother fixing it. One thing though anyone else seeing this happen to be using TinyMCE Advanced? Could it be anutyhign to do with it. I might test and see.

    Thread Starter irishetcher

    (@irishetcher)

    Hi Ben,

    Good news. Solved!

    In digging around, as per your request to specify the sticky settings, I noticed that the main menu row had a transparent background. setting this to white sorted the flip from portrait to landscape on tablet. What I learned. There are an awful lot of options under the customiser… which is a good thing. Lots of flexibility.

    Tanks for your patience.

    Thread Starter irishetcher

    (@irishetcher)

    Hi Hannah,

    You can grab the quick movie I made on the header issue I am seeing.

    https://www.mediafire.com/file/74zt6erg0xmav0b/sticky-header.mov/file

    I recorded this with ten viewport set to tablet as it the most likely place that people will encounter this issue.

    It start in Landscape with the header working properly. It is a solid header and should be fixed/sticky as per the setting I made for desktop. I then switch the view to portrait and again all is fine. In fact the header is sticky. But, when I switch back to landscape you will see that the white header background is a bit off and when I scroll this background scrolls away as well.

    Thread Starter irishetcher

    (@irishetcher)

    Thanks Hannah,

    Yes, the site is for testing, so I enabled the maintenance page again after not hearing back from Ben. If possible I will see if I can make a short video, if the uploader permits this, if not I will send a set of screenshots.

    Thread Starter irishetcher

    (@irishetcher)

    Hi Ben,

    Here is a link to where you can see what I am talking about:

    https://testing.vaughanprint.com/.

    I stuck a screenshot of the header settings onto the page. I disabled all plugins except for Kadence.

    The best way to see this is to use Chrome tools or other and view as a tablet, in portrait first, then landscape. When you do this and scroll up you will see the page content moving up under the header which is now transparent.

    Lastly, I presume we can make a basic child theme from the parent as per the standard WordPress instructions. I am planning to build a budget site for a client with the Kadence theme. Their hosting isn’t the quickest so this will be a perfect fit for this theme and I want to work exclusively with the block editor to be more familiar with it and any of its quirks. The last time I did a block editor build was over a year ago and I used another theme whose child theme set up for me wasn’t standard. It looks like things have moved on nicely since then.

    Thread Starter irishetcher

    (@irishetcher)

    Just checked out the Block Navigation plugin. Makes moving stuff a far better experience.

    Cheers.

    Thread Starter irishetcher

    (@irishetcher)

    Thanks Ben,

    I will have a look at that plugin you recommend. Though I try to follow best practice and install as few plugins as possible… it never works out that way. You know yourself.

    Good to hear you are working on the previews. Always the nagging feeling though that the Gutenberg team may come along later and suddenly introduce their own implementation which could mess up your solution or Toolset’s. It’s the one crib I have with the whole block editor project. They get so far and then get distracted by some other cool feature such as Full Site editing without covering all use cases that are set up on sites.

    One of these, which if you ever used Toolset to set up a custom post type with a prescribed set of custom fields, is data entry where the main editor is disabled and the user is forced to use what’s provided. All this is then dynamically presented with a template designed elsewhere. As it is with the new editor, the blocks, which are great for free form content creation, are dangerously, available to clients and end users. There should be a way to disable this editor area, even if it has to be done with a function or as a setting on the post type in the likes of Toolset. Like yourself I have resorted to a hack that is a function that activates css on the post type to hide the block editor. Probably not the best solution but it works. And, the curious question, with the classic editor flagged to be retired by the end of the year, where is the fancy new UI for WooCommerce products?

    Thread Starter irishetcher

    (@irishetcher)

    Hi Alex,

    So, first go to edit the page and then open Asset Managers rules for loading and unloading. Scroll down to the WooCommerce section and check to see if you have opted to unload for photo swipe dependencies. Might be wise just to remove any unloads for WooCommerce at this stage. Save and then remove my suggested css to see if the issues is resolved.

Viewing 15 replies - 31 through 45 (of 148 total)