dabeed

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
1 2
  • Forum: Plugins
    In reply to: [BetterDocs – Knowledge Base Docs & FAQ Solution for Elementor & Block Editor] How to stop theme overrides?
    Thread Starter dabeed

    (@dabeed)

    8 months ago

    Hi Amit!

    I just updated on two sites and notice that font-family for the <h1> now uses theme CSS (that’s great!). However, font-size, font-weight, line-height, and text-transform are still being overridden by BetterDocs CSS. For <p> BetterDocs is also still overriding font-size and line-height. And those are just the rules I’m noticing off-hand, there may be other overrides occurring.

    I also can’t seem to find any setting similar to the one I shared provided by The Events Calendar. Something like that would be the optimal solution.

    Also, I noticed when I updated to 4.0.0 it automatically changed the layout option from the Essence layout (which was what it was set to prior to the update) to the Classic layout. Is there a reason the layout selection is changed when updating the plugin?

    Forum: Plugins
    In reply to: [BetterDocs – Knowledge Base Docs & FAQ Solution for Elementor & Block Editor] How to stop theme overrides?
    Thread Starter dabeed

    (@dabeed)

    8 months, 2 weeks ago

    As an update and for more clarification, BetterDocs is adding the typography I am referring to via Customize > BetterDocs – and in most (if not all) the sections (Docs Page, Single Doc, Sidebar… etc.).

    Here’s just one example from Single Doc for the Post Title:

    View post on imgur.com

    If a user want’s to maintain theme consistency even on the BetterDocs pages, they “might” be able to use the settings in the image above to duplicate their theme. But they shouldn’t have to do that – they shouldn’t have to ‘re-apply theme settings in multiple places’. There should be an option to turn this off and let the theme work.

    font-size: BetterDocs resets the font-size for h1. While I can go in and try to match font-size for desktop/tablet/mobile via settings in BetterDocs, I can’t change the breakpoints, or add more breakpoints, nor can I use clamp() for font-size for a perfect responsive font. If I want to do any of that, I have to write additional CSS to override the forced BetterDocs CSS.

    color: BetterDocs resets the color for h1. While there is a color picker provided, this means I have to go find the hex for my theme’s h1 and paste that in. It would be better to use color-palette here as at least then you could directly pick the theme color (https://developer.wordpress.org/block-editor/reference-guides/components/color-palette/). However, this still means that you have to ‘reset’ this in Customize > BetterDocs rather than just let the theme do it’s job.

    font-weight: This is set by BetterDocs CSS files but there is no ability to change this in Customize > BetterDocs that I can see. So the only way to override BetterDocs’ forced CSS is to write more CSS to override BetterDocs.

    margin: Same thing here. The user has to find the margins used by the theme and copy those over, for each breakpoint. And if fluid margins are used via clamp(), custom CSS overrides are needed just to match what is already done by the theme.

    font-family: This is like font-weight in that the BetterDocs CSS files (the 16 noted earlier) set the font-family to ‘Lora’. But there is no option that I have found that allows me to reset font-family back to the theme’s font-family for h1. The only way (that I can find) to override this h1 font-family is to write additional CSS with enough specificity to win over BetterDocs’ 0,7,0 specificity.

    This is just one area of many where BetterDocs hijacks the theme by forcing a pre-made ‘layout’ in a way that makes it more difficult to maintain theme styles within BetterDocs pages.

    This makes site set up more difficult and time consuming. It also means there is no longer a single source of truth for theme styling. Any change to the overall theme for this CSS means you also have to come into Customize > BetterDocs and make the same changes, or, you may have to write additional CSS to override. If a user decides to change the BetterDocs pre-made layout to another pre-made layout, that will break their theme styling as the overrides would have to be made on a BetterDocs layout by layout basis.

    Providing pre-made layout options is great! I love that! But forcing all the typography that comes with these layouts is too heavy handed in my opinion. Yes, someone with 30 years of front-end dev experience like myself can easily write the necessary overrides. But that still means there is no single source of truth for theme typography. For the novice, if they want to maintain theme typography even on the BetterDocs pages, they may be unable to do so without quite a bit of help.

    BetterDocs should provide a way to only use the basic, absolutely required styles for BetterDocs while relying on the theme for everything else. You can still provide the option for the full typography take-over within the layout options. But the full typography take-over layouts should not be the only option (without further customizations required). A great example of this is done by The Events Calendar:

    https://theeventscalendar.com/knowledgebase/basic-template-settings/

    View post on imgur.com

    Hopefully this and my most recent prior post explain things better. Looking forward to your reply!

    Forum: Plugins
    In reply to: [BetterDocs – Knowledge Base Docs & FAQ Solution for Elementor & Block Editor] How to stop theme overrides?
    Thread Starter dabeed

    (@dabeed)

    8 months, 2 weeks ago

    BetterDocs CSS sets font-family in 16 different CSS files:

    View post on imgur.com

    Those files are in /plugins/betterdocs/assets/public/css.

    Here’s an example from toc.css:

    .betterdocs-wrapper.betterdocs-single-layout-8 .betterdocs-content-wrapper .docs-content-full-main .betterdocs-content-inner-area .betterdocs-entry-header .betterdocs-entry-title {
        color: #1d2939;
        font-family: Lora;
        font-size: 42px;
        font-weight: 700;
        line-height: 1.2em;
        margin: 0;
        padding-bottom: 24px;
        text-transform: unset;
    }

    The CSS above is applied to the page heading <h1> where you add the class .betterdocs-entry-title to the <h1> for a BetterDocs page (with a specificity of 0,7,0).

    That should be all that is needed to see that BetterDocs adds typography CSS with a specificity that will override just about any theme (probably all themes).

    Even so, I’ve spun up a new site, installed the GeneratePress theme and BetterDocs (and no other plugins) I set the theme’s h1 to font-family: Arial, font-weight: 100, and font-size: 100px via the Customizer. You can see this on this page:

    https://betterdocs.flywheelsites.com/sample-page/

    The page heading based on theme settings looks like this:

    View post on imgur.com

    Then I created a single BetterDocs page here:

    https://betterdocs.flywheelsites.com/docs/betterdocs-page-heading/

    The page heading looks like this:

    View post on imgur.com

    Clearly BetterDocs is changing the h1 to something different than what is defined by the theme. It is also doing this for the content area font-size as noted on those pages.

    • This reply was modified 8 months, 2 weeks ago by dabeed.
    Forum: Plugins
    In reply to: [BetterDocs – Knowledge Base Docs & FAQ Solution for Elementor & Block Editor] How to stop theme overrides?
    Thread Starter dabeed

    (@dabeed)

    8 months, 3 weeks ago

    You are using Elementor to override the BetterDocs typography CSS. I am using straight CSS to do the same thing. So it seems that you recognize that BetterDocs does have typography CSS that hijacks the theme, and that to fix this you must have additional CSS to override BetterDocs. You do that with Elementor, I did it with straight CSS.

    The point being that the BetterDocs plugin loads typography CSS that will override the theme (unless you add more code to override BetterDocs).

    https://imgur.com/a/jTDQcZ4

    Again, I have already written the additional CSS needed to override the typography CSS from BetterDocs – just like you did with Elementor.

    I’m not seeking help to code CSS to override the BetterDocs typography CSS (again, I have already done this).

    My question was whether there was a toggle to turn off the BetterDocs CSS rather than writing more CSS just to override BetterDocs from hijacking the theme. (You never answered that question – though I can infer that there is no toggle.)

    The only thing I am doing now is pointing out that typography is the domain of the theme. What BetterDocs is doing with typography is not best practices for plugin development, and the typography CSS should be removed from the plugin. Not only does it hijack the theme, it provides no benefit at all. And there are many benefits from removing that CSS (see the list I provided in an earlier post).

    Forum: Plugins
    In reply to: [BetterDocs – Knowledge Base Docs & FAQ Solution for Elementor & Block Editor] How to stop theme overrides?
    Thread Starter dabeed

    (@dabeed)

    8 months, 3 weeks ago

    It’s all local for now.

    But you should be able to look at the plugin files I mentioned and see the code where BetterDocs is setting styles for font-family, font-size and things on the h1.

    Or you could look on your demo, for example on this page: https://demo.betterdocs.co/docs/community-support-for-sleek-layout-expert-guidance/

    The theme you use (Flexia) sets the h1 to font-size: 2em; and font-family: Merriweather,sans-serif;. BetterDocs then overrides these and sets the h1 font-size: 22px; and font-family: “Lora”, Sans-serif;. So you should be able to see everything I have mentioned occurring on your site.

    The only ways to ‘fix’ this is for either the site dev to write all the overrides just to allow the theme to work, or, BetterDocs removes CSS that overrides basic theme code (like typography). In my option this CSS should be removed from BetterDocs – or at least a toggle provided to turn it off.

    Forum: Plugins
    In reply to: [BetterDocs – Knowledge Base Docs & FAQ Solution for Elementor & Block Editor] How to stop theme overrides?
    Thread Starter dabeed

    (@dabeed)

    8 months, 4 weeks ago

    Hi Amit

    Thanks for the super fast reply – very much appreciated!

    Unfortunately, that isn’t how CSS works. This suggestion made no impact for two reasons.

    First, there is no .betterdocs-container class. I even opened the plugin files in VSCode and did a search, and that class doesn’t exist anywhere. Perhaps you meant betterdocs-wrapper? But even that wouldn’t work due to the second reason.

    Second, inherit works on the element to which it is applied and instructs that element to inherit the property’s value from its parent HTML element in the DOM. It does not mean “find another CSS rule that would have applied to this element and use that value instead.” Inherit is tied to the hierarchical structure of the DOM, not the CSS Cascade. Therefore, even using h1.betterdocs-entry-title { font-family: inherit !important; } will not apply the theme’s h1 styles — because that style will now be inherited from whatever the parent element is for h1.betterdocs-entry-title, not from the CSS Cascade (or some sort of reverse specificity).

    The code you provided would tell the browser to use the styles set on whatever the parent element of .betterdocs-container is (but only if .betterdocs-container existed). If .betterdocs-wrapper was intended, this code would inherit those properties from div.site-content on the site I’m working on – but it would likely be different depending on the theme. So the code provided would likely only have some very odd results (if any), and would certainly be inconsistent from site to site.

    To the best of my knowledge there are only 2 ways to resolve this issue.

    Option 1: The site dev re-writes any and all necessary code to override BetterDocs CSS that changes theme styles.

    Pro: It (usually) works.

    Cons: More work (initially and for theme changes) as it requires duplication of code, resulting in greater potential for error and inconsistencies. This will also break if the classes and/or class structure used by BetterDocs change at some point in the future. It’s not a good long-term solution.

    Option 2: BetterDocs provides a means (such as a single toggle) to turn off any BetterDocs CSS that alters any standard elements – for example heading and body content area typography.

    Pros: It works out of the box, easier for non-devs, no need for code duplication – there’s a single source of truth for styles reducing possible errors and inconsistencies. Site owners that want the BetterDocs CSS overrides can still have them. Site owners that prefer theme style consistency can have that too. Potential changes to classes/structure within BetterDocs would no longer be a concern (for the site owner).

    Cons: I can’t think of any – other than more work for BetterDocs to provide this ability.

    My original question was if there was a way to get the plugin to honor theme settings, which would be Option 2. At this point my assumption is that this is not currently available (but please correct me if I’m wrong). So I’ve already written all the overrides with the proper specificity for my needs.

    I understand it may be a bit of work to implement Option 2 (I’ve been in dev for 30 years and have developed plugins as well), but I think it would be a great addition to the plugin – especially for those who aren’t devs yet still want theme consistency even on the BetterDocs pages.

    I also understand it is ‘par for the course’ to have to override plugin CSS now and then. And I understand that as a ‘system’ plugin with its own Post Type(s) and layout requirements, these factors increase the potential need for some theme overrides. But I’d also argue that typography for headings and the content area ‘reading font’ do not require styling from BetterDocs, and that these styles should either be avoided by BetterDocs, or provided only as an option via a toggle.

    To summarize, here are the benefits I see should BetterDocs implement Option 2:

    • It would actually be true to say “it works with all themes”.
    • Less confusion for non-devs and easier on devs (including maintenance).
    • Greater optimization (less code to load since no overrides are needed).
    • Single source of truth that would need to be maintained for CSS (rather than 2 that must be kept in sync).
    • Provides the easiest way for site owners to maintain theme consistency throughout the site.
    • Much less likely that class/structure changes to the plugin would break theme styles.

    That said, I am very impressed with this plugin. I only recently came across BetterDocs (I am using it for documentation on a site for a new plugin we are developing) and I am loving it! I will certainly be thinking about several client sites that may also benefit from this plugin.

    Adding something like Option 2 would make BetterDocs even better – would that be BetterBetterDocs, or BestDocs? 😉

    Forum: Plugins
    In reply to: [BetterDocs – Knowledge Base Docs & FAQ Solution for Elementor & Block Editor] How to stop theme overrides?
    Thread Starter dabeed

    (@dabeed)

    9 months ago

    Hi Amit! I’m doing great and hope the same is true for you!

    I’m using GeneratePress without a child theme. I’m setting fonts in the Customizer – fonts are being set globally. These are the only fonts loading as seen in payload:

    Roboto:100,100italic,300,300italic,regular,italic,500,500italic,700,700italic,900,900italic|Inter:100,200,300,regular,500,600,700,800,900

    BetterDocs is overriding font-family for h1’s in these 5 css files.

    • /wp-content/plugins/betterdocs/assets/public/css/toc.css
    • /wp-content/plugins/betterdocs/assets/public/css/social-share.css
    • /wp-content/plugins/betterdocs/assets/public/css/reactions.cs
    • /wp-content/plugins/betterdocs/assets/public/css/category-grid.cs
    • /wp-content/plugins/betterdocs/assets/public/css/single.cs

    Sample from toc.css (specificity 0,7,0) where .betterdocs-entry-title is added to the page h1:

    .betterdocs-wrapper.betterdocs-single-layout-8 .betterdocs-content-wrapper .docs-content-full-main .betterdocs-content-inner-area .betterdocs-entry-header .betterdocs-entry-title {
        color: #1d2939;
        font-family: Lora;
        font-size: 42px;
        font-weight: 700;
        line-height: 1.2em;
        margin: 0;
        padding-bottom: 24px;
        text-transform: unset
    }

    This is overriding the theme code (specificity 0,0,1):

    h1 {
        font-family: Inter, sans-serif;
        font-weight: 300;
        font-size: 2.98rem;
    }

    The result in this case is that a system font is loaded for all h1’s on all BetterDocs generated pages (since Lora isn’t loading).

    Unless I’m missing something, it does seem BetterDocs CSS is doing much more than color and weight.

    There’s also a content area font-size being injected that overrides the theme:

    .betterdocs-wrapper.betterdocs-single-wrapper.betterdocs-single-layout-8 .betterdocs-content-wrapper .docs-content-full-main .betterdocs-content, .betterdocs-wrapper.betterdocs-single-wrapper.betterdocs-single-layout-9 .betterdocs-content-wrapper .docs-content-full-main .betterdocs-content {
        font-size: 18px;
    }

    The issue is compounded if trying to use fluid typography (which I am, again through the Customizer for GeneratePress).

    There is even some BetterDocs CSS where one area is trying to change the font-size in a media query but other BetterDocs CSS overrides that and cancels out the responsiveness:

    From toc.css

    @media only screen and (max-width: 1280px) {
        .betterdocs-wrapper.betterdocs-single-layout-8 .betterdocs-content-wrapper .docs-content-full-main .betterdocs-content-inner-area .betterdocs-entry-header .betterdocs-entry-title {
            font-size: 30px;
            padding-bottom: 18px;
        }
    }

    But then injected CSS…

    .betterdocs-wrapper.betterdocs-single-wrapper.betterdocs-single-layout-8 .betterdocs-content-wrapper .docs-content-full-main .betterdocs-content-inner-area .betterdocs-entry-header .betterdocs-entry-title, .betterdocs-wrapper.betterdocs-single-wrapper.betterdocs-single-layout-9 .betterdocs-content-wrapper .docs-content-full-main .betterdocs-content-inner-area .betterdocs-entry-header .betterdocs-entry-title {
        font-size: 42px;
    }

    … font-size: 42px; wins on specificity (and order).

    I may be wrong, but it sure seems like there is a great deal one has to fight in order to maintain theme styles for standard elements like headings and body content.

    Forum: Plugins
    In reply to: [Independent Analytics - Google Analytics Alternative for WordPress] HIPAA Compliance
    Thread Starter dabeed

    (@dabeed)

    1 year, 9 months ago

    Thanks!

    Just to confirm, IPs are anonymized with this plugin, correct?

    Forum: Plugins
    In reply to: [TI WooCommerce Wishlist] Wishlist as My Account endpoint
    Thread Starter dabeed

    (@dabeed)

    3 years, 5 months ago

    Great! Looking forward to it!

    Forum: Plugins
    In reply to: [TI WooCommerce Wishlist] Wishlist as My Account endpoint
    Thread Starter dabeed

    (@dabeed)

    3 years, 5 months ago

    Yes:
    https://snipboard.io/e3O2Hk.jpg

    If you then go to My Account (renamed My Garage here) you see the menu on the left:
    https://snipboard.io/SP9UhO.jpg

    On that page there is a woocommerce-account body class:
    https://snipboard.io/h6NnJA.jpg

    And the structure includes a wrapping “woocommerce” div, nav.woocommerce-MyAccount-navigation, and div.woocommerce-MyAccount-content:
    https://snipboard.io/VKIbur.jpg

    But when you go to the Wish List (renamed Parts List here), while the URL is /my-account/wishlist-manage/ – the menu is gone:
    https://snipboard.io/MHQo3g.jpg

    There is no woocommerce-account body class:
    https://snipboard.io/wkFZnf.jpg

    And while there is a wrapping “woocommerce” div, the rest of the structure is different:
    https://snipboard.io/mRvNjc.jpg

    What we want is for the entire user experience of the wish list to be IN My Account such that the user can then navigate to any other part of My Account while they are working on their wish list.

    Is this possible?

    • This reply was modified 3 years, 5 months ago by dabeed.
    Forum: Plugins
    In reply to: [TI WooCommerce Wishlist] Wishlist as My Account endpoint
    Thread Starter dabeed

    (@dabeed)

    3 years, 5 months ago

    That doesn’t appear to work. While the URL remains under /my-account/, the structure is not that of the WooCommerce Account page. For example, there is no woocommerce-account body class, the My Account menu, <nav class=”woocommerce-MyAccount-navigation”>, is gone.

    How do we make it so that it actually IS an endpoint inside My Account (not just the URL) and not simply added to the initial menu, which then disappears as soon as you click on Wish List?

    Forum: Plugins
    In reply to: [Braintree for WooCommerce Payment Gateway] Apply Pay btn set to display:none;
    Thread Starter dabeed

    (@dabeed)

    3 years, 6 months ago

    Regarding step 1 and creating an Apple Pay Merchant ID, the client receive the following from Braintree Technical Support on 8/3/22 1:09PM PST, case 11090508:

    “Upon taking a look into the … account, I can confirm from Braintree’s side of things you are correctly setup to process with Apple Pay. The Apple Pay certificate only applies if you integrate with Apple Pay using our iOS client SDK, if you only have a domain then it would not concern you.”

    We’ll go ahead and submit a support request with WooCommerce, but I wanted to confirm whether or not they actually do need to create an Apple Pay Merchant ID.

    Thanks!

    Forum: Plugins
    In reply to: [Braintree for WooCommerce Payment Gateway] Apply Pay btn set to display:none;
    Thread Starter dabeed

    (@dabeed)

    3 years, 6 months ago

    Hi

    I’ve turned off basic auth so you should be able to access at that URL.

    Here’s the WC Status Report:

    
### WordPress Environment ###

WordPress address (URL): https://stagingfutv.wpengine.com
Site address (URL): https://stagingfutv.wpengine.com
WC Version: 6.7.0
REST API Version: ✔ 6.7.0
WC Blocks Version: ✔ 7.8.3
Action Scheduler Version: ✔ 3.4.0
Log Directory Writable: ✔
WP Version: ❌ 5.9.3 - There is a newer version of WordPress available (6.0.1)
WP Multisite: –
WP Memory Limit: 1 GB
WP Debug Mode: –
WP Cron: ✔
Language: en_US
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 7.4.30
PHP Post Max Size: 100 MB
PHP Time Limit: 3600
PHP Max Input Vars: 10000
cURL Version: 7.58.0
OpenSSL/1.1.1

SUHOSIN Installed: –
MySQL Version: 5.7.38-41-log
Max Upload Size: 50 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

### Database ###

WC Database Version: 6.7.0
WC Database Prefix: wp_aq3gpsazgf_
Total Database Size: 1767.78MB
Database Data Size: 1258.10MB
Database Index Size: 509.68MB
wp_aq3gpsazgf_woocommerce_sessions: Data: 0.05MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_order_items: Data: 9.52MB + Index: 2.52MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_order_itemmeta: Data: 314.58MB + Index: 35.09MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_tax_rates: Data: 0.16MB + Index: 0.20MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_tax_rate_locations: Data: 0.20MB + Index: 0.22MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_actionscheduler_actions: Data: 51.58MB + Index: 36.16MB + Engine InnoDB
wp_aq3gpsazgf_actionscheduler_claims: Data: 1.52MB + Index: 0.44MB + Engine InnoDB
wp_aq3gpsazgf_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_actionscheduler_logs: Data: 36.56MB + Index: 19.03MB + Engine InnoDB
wp_aq3gpsazgf_commentmeta: Data: 1.52MB + Index: 0.72MB + Engine InnoDB
wp_aq3gpsazgf_comments: Data: 50.58MB + Index: 31.09MB + Engine InnoDB
wp_aq3gpsazgf_dgwt_wcas_index: Data: 5.52MB + Index: 0.16MB + Engine InnoDB
wp_aq3gpsazgf_dgwt_wcas_invindex_cache: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_dgwt_wcas_invindex_doclist: Data: 36.56MB + Index: 42.09MB + Engine InnoDB
wp_aq3gpsazgf_dgwt_wcas_invindex_wordlist: Data: 4.52MB + Index: 4.52MB + Engine InnoDB
wp_aq3gpsazgf_dgwt_wcas_tax_index: Data: 0.11MB + Index: 0.05MB + Engine InnoDB
wp_aq3gpsazgf_dgwt_wcas_var_index: Data: 9.52MB + Index: 2.63MB + Engine InnoDB
wp_aq3gpsazgf_gf_draft_submissions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_gf_entry: Data: 1.52MB + Index: 0.11MB + Engine InnoDB
wp_aq3gpsazgf_gf_entry_meta: Data: 2.52MB + Index: 1.91MB + Engine InnoDB
wp_aq3gpsazgf_gf_entry_notes: Data: 0.47MB + Index: 0.14MB + Engine InnoDB
wp_aq3gpsazgf_gf_form: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_gf_form_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_gf_form_revisions: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_gf_form_view: Data: 0.08MB + Index: 0.09MB + Engine InnoDB
wp_aq3gpsazgf_gf_rest_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_hurrytimer_evergreen: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_i13_woo_slider: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_mailchimp_carts: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_mailchimp_jobs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_ms_snippets: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_nextend2_image_storage: Data: 0.06MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_nextend2_section_storage: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_aq3gpsazgf_nextend2_smartslider3_generators: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_nextend2_smartslider3_sliders: Data: 0.28MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_nextend2_smartslider3_sliders_xref: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_nextend2_smartslider3_slides: Data: 2.52MB + Index: 0.11MB + Engine InnoDB
wp_aq3gpsazgf_options: Data: 10.47MB + Index: 1.69MB + Engine InnoDB
wp_aq3gpsazgf_postmeta: Data: 416.97MB + Index: 190.41MB + Engine InnoDB
wp_aq3gpsazgf_posts: Data: 53.58MB + Index: 15.09MB + Engine InnoDB
wp_aq3gpsazgf_redirection_404: Data: 3.02MB + Index: 0.48MB + Engine InnoDB
wp_aq3gpsazgf_redirection_groups: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_redirection_items: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
wp_aq3gpsazgf_redirection_logs: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_aq3gpsazgf_rg_form: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_rg_form_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_rg_form_view: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_rg_incomplete_submissions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_rg_lead: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_rg_lead_detail: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_aq3gpsazgf_rg_lead_detail_long: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_rg_lead_meta: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_aq3gpsazgf_rg_lead_notes: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_shortpixel_folders: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_shortpixel_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_shortpixel_postmeta: Data: 117.64MB + Index: 42.61MB + Engine InnoDB
wp_aq3gpsazgf_shortpixel_queue: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
wp_aq3gpsazgf_snippets: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_swp_cf: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_aq3gpsazgf_swp_index: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_swp_log: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_aq3gpsazgf_swp_tax: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_aq3gpsazgf_swp_terms: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_aq3gpsazgf_taxjar_record_queue: Data: 2.52MB + Index: 0.41MB + Engine InnoDB
wp_aq3gpsazgf_termmeta: Data: 1.52MB + Index: 0.36MB + Engine InnoDB
wp_aq3gpsazgf_terms: Data: 0.06MB + Index: 0.09MB + Engine InnoDB
wp_aq3gpsazgf_term_relationships: Data: 4.52MB + Index: 2.52MB + Engine InnoDB
wp_aq3gpsazgf_term_taxonomy: Data: 0.06MB + Index: 0.09MB + Engine InnoDB
wp_aq3gpsazgf_tinvwl_analytics: Data: 0.36MB + Index: 0.17MB + Engine InnoDB
wp_aq3gpsazgf_tinvwl_items: Data: 0.38MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_tinvwl_lists: Data: 0.16MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_tm_taskmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_tm_tasks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_usermeta: Data: 45.58MB + Index: 30.11MB + Engine InnoDB
wp_aq3gpsazgf_users: Data: 2.52MB + Index: 1.28MB + Engine InnoDB
wp_aq3gpsazgf_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_wc_admin_note_actions: Data: 0.05MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_wc_customer_lookup: Data: 2.52MB + Index: 1.91MB + Engine InnoDB
wp_aq3gpsazgf_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_wc_order_coupon_lookup: Data: 0.38MB + Index: 0.38MB + Engine InnoDB
wp_aq3gpsazgf_wc_order_product_lookup: Data: 6.52MB + Index: 6.06MB + Engine InnoDB
wp_aq3gpsazgf_wc_order_stats: Data: 3.52MB + Index: 3.53MB + Engine InnoDB
wp_aq3gpsazgf_wc_order_tax_lookup: Data: 0.39MB + Index: 0.31MB + Engine InnoDB
wp_aq3gpsazgf_wc_points_rewards_user_points: Data: 1.52MB + Index: 0.89MB + Engine InnoDB
wp_aq3gpsazgf_wc_points_rewards_user_points_log: Data: 2.52MB + Index: 1.27MB + Engine InnoDB
wp_aq3gpsazgf_wc_product_attributes_lookup: Data: 0.05MB + Index: 0.05MB + Engine InnoDB
wp_aq3gpsazgf_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_wc_product_meta_lookup: Data: 3.52MB + Index: 5.77MB + Engine InnoDB
wp_aq3gpsazgf_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_gc_activity: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_gc_cards: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_aq3gpsazgf_woocommerce_gc_cardsmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_aq3gpsazgf_woof_query_cache: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_wpmailsmtp_debug_events: Data: 0.27MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_wpmailsmtp_tasks_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_ycd_subscribers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_aq3gpsazgf_yoast_indexable: Data: 41.56MB + Index: 18.09MB + Engine InnoDB
wp_aq3gpsazgf_yoast_indexable_hierarchy: Data: 2.52MB + Index: 4.55MB + Engine InnoDB
wp_aq3gpsazgf_yoast_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_aq3gpsazgf_yoast_primary_term: Data: 1.52MB + Index: 1.97MB + Engine InnoDB
wp_aq3gpsazgf_yoast_seo_links: Data: 0.36MB + Index: 0.19MB + Engine InnoDB
wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_comments: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_options: Data: 0.05MB + Index: 0.03MB + Engine InnoDB
wp_postmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_posts: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_usermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

### Post Type Counts ###

acf-field: 46
acf-field-group: 10
attachment: 35130
condition_group: 3
custom_css: 1
hurrytimer_countdown: 1
nav_menu_item: 340
oembed_cache: 328
page: 38
post: 7
product: 6777
product_variation: 15281
responsive_accordion: 1
seedprod: 1
shop_bogof_rule: 2
shop_coupon: 39
shop_order: 25327
shop_order_refund: 1785
sidebar: 1
was: 3
wp_global_styles: 1
wpcode: 2
ycdcountdown: 1

### Security ###

Secure connection (HTTPS): ✔
Hide errors from visitors: ✔

### Active Plugins (2) ###

Braintree for WooCommerce Payment Gateway: by WooCommerce – 2.6.5
WooCommerce: by Automattic – 6.7.0

### Inactive Plugins (70) ###

Advanced Custom Fields PRO: by Delicious Brains – 5.12.3
Advanced Order Export For WooCommerce: by AlgolPlus – 3.3.1
Authorize.Net CIM for WooCommerce: by Cardpay Solutions
Inc. – 2.0.22

Better Search Replace: by Delicious Brains – 1.4.1
Black Studio TinyMCE Widget: by Black Studio – 2.7.2
CartPops Pro: by CartPops.com – 1.4.22
Category Order and Taxonomy Terms Order: by Nsp-Code – 1.6.1
CheckoutWC: by Objectiv – 7.6.0
Code Snippets: by Code Snippets Pro – 3.2.0
Content Aware Sidebars: by Joachim Jensen - DEV Institute – 3.18
Countdown builder: by Adam Skaat – 2.3.9.13
Customer Reviews for WooCommerce: by CusRev – 5.1.2
Custom Post Type UI: by WebDevStudios – 1.12.1
Duplicate Menu: by Jonathan Christopher – 0.2.2
Enable Media Replace: by ShortPixel – 3.6.3
Export media with selected content: by Joost de Keijzer – 2.1.4
Facebook Chat Plugin - Live Chat Plugin for WordPress: by Meta – 2.5
Facebook for WooCommerce: by Facebook – 2.6.19
FiboSearch - AJAX Search for WooCommerce (Pro): by FiboSearch Team – 1.19.0
Genesis Connect for WooCommerce: by StudioPress – 1.1.1
Genesis Simple Sidebars: by StudioPress – 2.2.2
Gravity Forms: by Gravity Forms – 2.6.4
Gravity Forms Gutenberg Add-On: by rocketgenius – 1.0-rc-1.4
GTM4WP: by Thomas Geiger – 1.16.1
HurryTimer: by Nabil Lemsieh – 2.7.2
Klaviyo: by Klaviyo
Inc. – 3.0.3

LP Woocommerce Bing Conversion Tracking: by LP – 1.1
Max Mega Menu: by megamenu.com – 2.9.7
Max Mega Menu - Pro Addon: by megamenu.com – 2.2.6
Nav Menu Roles: by Kathy Darling – 2.1.0
Points and rewards data to CSV export for WooCommerce: by Rynaldo Stoltz – 1.3
Product Filter for WooCommerce: by XforWooCommerce – 8.2.1
Product Per Page for Woocommerce: by FME Addons – 1.0.0
Redirection: by John Godley – 5.3.1
Regenerate Thumbnails Advanced: by ShortPixel – 2.4.0
Responsive Accordion And Collapse: by wpshopmart – 2.3.5
Safe SVG: by 10up – 2.0.2
ShortPixel Image Optimizer: by ShortPixel – 5.0.7
Simple Social Icons: by StudioPress – 3.1.1
Smart Image Resize PRO: by Nabil Lemsieh – 1.7.6.4
Smart Slider 3 Pro: by Nextend – 3.5.1.7
Springbot WooCommerce Integration: by Springbot – 0.0.15
TaxJar - Sales Tax Automation for WooCommerce: by TaxJar – 4.1.3
TI WooCommerce Wishlist: by TemplateInvaders – 1.47.0
Ultimate Addons for Gutenberg: by Brainstorm Force – 1.25.6
Veeqo for WooCommerce: by Veeqo – 1.2.7
Woo All In One Product Slider Carousel: by I Thirteen Web Solution – 1.0.23
WooCommerce - ShipStation Integration: by WooCommerce – 4.1.48
WooCommerce Affirm Gateway: by WooCommerce – 1.3.4 (update to version 1.3.5 is available)
WooCommerce Blocks: by Automattic – 7.6.0
WooCommerce Buy One Get One Free: by Oscar Gare – 3.3.1 (update to version 3.4.0 is available)
WooCommerce Conditional Shipping and Payments: by WooCommerce – 1.14.0 (update to version 1.14.1 is available)
WooCommerce Gift Cards: by WooCommerce – 1.12.1 (update to version 1.12.2 is available)
WooCommerce Name Your Price: by Kathy Darling – 3.3.9
WooCommerce PayPal Payments: by WooCommerce – 1.9.1
WooCommerce PayPal Pro (Classic and PayFlow Editions) Gateway: by WooCommerce – 4.5.1
WooCommerce Points and Rewards: by WooCommerce – 1.7.10 (update to version 1.7.11 is available)
WooCommerce Product Add-ons: by WooCommerce – 5.0.0
WooCommerce Product CSV Import Suite: by WooCommerce – 1.10.49
WooCommerce Signifyd Integration: by Absolute Web – 1.3.062321
WooCommerce Tabs to Accordion: by Jasper Frumau – 1.0.1
WP-Optimize - Clean, Compress, Cache: by David Anderson
Ruhani Rabin
Team Updraft – 3.2.6

WP101 Video Tutorial Plugin: by WP101® – 5.3
WPCode - Insert Headers, Footers, and Code Snippets: by WPCode – 2.0.1
WPFront Notification Bar: by Syam Mohan – 3.2.0
WP Mail SMTP: by WPForms – 3.5.1
WPS Hide Login: by WPServeur
NicolasKulka
wpformation – 1.9.6

YITH WooCommerce Brands Add-On Premium: by YITH – 2.2.0
Yoast SEO: by Team Yoast – 19.4
Yotpo Social Reviews for Woocommerce: by Yotpo – 1.1.8

### Dropin Plugins (2) ###

advanced-cache.php: advanced-cache.php
db-error.php: db-error.php

### Must Use Plugins (6) ###

Force Strong Passwords - WPE Edition: by Jason Cosper – 1.8.0
WPE ElasticPress Autosuggest Logger: by WP Engine – 1.0.0
WP Engine Cache Plugin: by WP Engine – 1.0.10
WP Engine Seamless Login Plugin: by WP Engine – 1.6.0
WP Engine Security Auditor: by wpengine – 1.0.10
WP Engine System: by WP Engine – 5.0.1

### Settings ###

API Enabled: ✔
Force SSL: –
Currency: USD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
pw gift card (pw-gift-card)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: ✔
Enforce Approved Product Download Directories: –

### WC Pages ###

Shop base: #15 - /shop/
Cart: #16 - /cart/
Checkout: #17 - /checkout/
My account: #18 - /my-account/
Terms and conditions: ❌ Page not set

### Theme ###

Name: Twenty Twenty-One
Version: 1.6
Author URL: https://wordpress.org/
Child Theme: ❌ – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme
WooCommerce Support: ✔

### Templates ###

Overrides: –

### Braintree (Credit Card) ###

Environment: Production
Tokenization Enabled: –
Debug Mode: Off

### Braintree (PayPal) ###

Environment: Production
Tokenization Enabled: –
Debug Mode: Off

### Admin ###

Enabled Features: activity-panels
analytics
coupons
customer-effort-score-tracks
experimental-products-task
experimental-import-products-task
experimental-fashion-sample-products
experimental-product-tour
homescreen
marketing
mobile-app-banner
navigation
onboarding
onboarding-tasks
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
wc-pay-promotion
wc-pay-welcome-page
wc-pay-subscriptions-page

Disabled Features: minified-js
settings

Daily Cron: ✔ Next scheduled: 2022-08-05 15:06:15 -07:00
Options: ✔
Notes: 90
Onboarding: completed

### Action Scheduler ###

Canceled: 19
Oldest: 2022-07-18 14:34:35 -0700
Newest: 2022-07-20 13:10:56 -0700

Complete: 97,523
Oldest: 2022-07-04 19:27:19 -0700
Newest: 2022-08-04 11:54:23 -0700

Failed: 37,560
Oldest: 2022-02-08 10:28:17 -0800
Newest: 2022-07-31 20:20:17 -0700

Pending: 1
Oldest: 2022-08-04 23:20:40 -0700
Newest: 2022-08-04 23:20:40 -0700

### Status report information ###

Generated at: 2022-08-04 15:05:40 -07:00
    Forum: Plugins
    In reply to: [Perfect Brands for WooCommerce] All Brands shortcode order_by=”name”
    Thread Starter dabeed

    (@dabeed)

    3 years, 6 months ago

    Note the URL has changed. You can now see the page here: https://www.american-utv.com/brands/

    Still not sure what you want a screenshot of, so here’s everything I could think of:

    Various settings pages:
    https://snipboard.io/SM7xPI.jpg
    https://snipboard.io/xe8Jsc.jpg
    https://snipboard.io/TnQ2zA.jpg
    https://snipboard.io/fInyjw.jpg

    This one is of the page itself where I’ve disabled the display:none; on the text, so that you can see the text is not in alpha order:
    https://snipboard.io/6uevFl.jpg

    Without that display:none; being disabled you’d see this:
    https://snipboard.io/mA9h2S.jpg

    The shortcode used:
    https://snipboard.io/KG3Dws.jpg

    Let me know if there are any specific screenshots you’d like to see that I haven’t included.

    Forum: Plugins
    In reply to: [Perfect Brands for WooCommerce] All Brands shortcode order_by=”name”
    Thread Starter dabeed

    (@dabeed)

    3 years, 6 months ago

    The page using the shortcode is here: https://amutv.3rdstudio.com/brands/

    Note we’re overriding with flex and also have display:none; on the <p> with the name. But if you disable the display:none; you’ll see the brand names are not in alphabetical order.

    What would you like a screenshot of? And how do I share a screenshot here?

Viewing 15 replies - 1 through 15 (of 20 total)
1 2