linux4me2

Forum Replies Created

Viewing 15 replies - 76 through 90 (of 1,795 total)
1 2 3 … 5 6 7 … 118 119 120
  • Forum: Themes and Templates
    In reply to: [Twenty Twenty-Three] Poor Largest Content full Paint Google PageSpeed
    linux4me2

    (@linux4me2)

    2 years, 11 months ago

    I checked on a test site, and I’m getting an LCP of 1.6s on mobile with a performance score of 99, and an LCP of 0.4s on desktop with a performance score of 100.

    The test site is on a Litespeed server and I’m using the Litespeed Cache plugin with the “advanced” presets.

    Are you using a caching plugin?

    Forum: Themes and Templates
    In reply to: [Twenty Twenty-Three] Navigation block doesn’t work at all
    linux4me2

    (@linux4me2)

    2 years, 11 months ago

    I don’t think this is specific to Twenty Twenty Three. I believe it’s a bug in the Navigation Block, or perhaps an issue with specific menus.

    I created a new post in a test site using the Twenty Sixteen theme, then added a navigation block and attempted to import the “main menu” for the site, the same one that failed in the Twenty Twenty Three theme.

    The menu displayed just right in the Editor, but on the front end it was a mess, displaying all the pages for the site.

    Forum: Plugins
    In reply to: [WooCommerce] Attributes > New Attribute Panel Loads Automatically On All Variable Products
    Thread Starter linux4me2

    (@linux4me2)

    2 years, 11 months ago

    I just updated to WC 7.8.0, and this issue seems to be fixed, so I’m marking this topic “resolved.”

    Thanks for the help!

    Forum: Themes and Templates
    In reply to: [Twenty Twenty-Three] Navigation block doesn’t work at all
    linux4me2

    (@linux4me2)

    2 years, 12 months ago

    I’ve experienced the same thing with Twenty Twenty Three, so at least you’re not alone.

    I can’t get the import menu to work on the front end, though it works fine in the editor. Creating a new menu works in the editor and the front end.

    I was thinking initially that it was some kind of caching issue, so I disabled my caching plugin (Litespeed) and made sure I cleared the browser cache, but neither made any difference.

    I’m thinking bug, since you deactivated all plugins and still had the same issue.

    Forum: Plugins
    In reply to: [LiteSpeed Cache] Litespeed Cache Breaks Site Logo Block
    Thread Starter linux4me2

    (@linux4me2)

    2 years, 12 months ago

    Thanks @qtwrk. I am very glad you were able to reproduce it.

    Forum: Plugins
    In reply to: [WooCommerce] Attributes > New Attribute Panel Loads Automatically On All Variable Products
    Thread Starter linux4me2

    (@linux4me2)

    3 years ago

    @druesome Very helpful! Thanks for doing that.

    Forum: Plugins
    In reply to: [WooCommerce] Attributes > New Attribute Panel Loads Automatically On All Variable Products
    Thread Starter linux4me2

    (@linux4me2)

    3 years ago

    Hi @babylon1999,

    However, based on my test, I can easily edit the existing local attribute even when the panel is open.

    I can edit existing local attributes too, I just can’t save the changes unless I delete the New Attribute panel because the Save Attributes button stays disabled as long as there is an uncompleted New Attribute panel there.

    I will wait to see what the developers say as you recommend. I doubt that this is a big priority for them since there are easy workarounds (add a global attribute, remove the New Attribute panel to save edits), but I hope they fix it. : )

    Forum: Plugins
    In reply to: [WooCommerce] Attributes > New Attribute Panel Loads Automatically On All Variable Products
    Thread Starter linux4me2

    (@linux4me2)

    3 years ago

    Hi @babylon1999,

    Thank you for submitting the bug report!

    Judging by the code snippet I included above, I believe opening an empty New Attribute panel is a feature intended only for when there are no product-specific (local) attributes. In that case, it’s convenient to have the New Attribute panel open without the need of an extra button-click to add a new attribute.

    However, if there are already local attributes, the panel shouldn’t open, because it requires the user to remove the New Attribute panel to edit existing local attributes. In that situation, I think it’s a bug.

    Forum: Plugins
    In reply to: [WooCommerce] Attributes > New Attribute Panel Loads Automatically On All Variable Products
    Thread Starter linux4me2

    (@linux4me2)

    3 years ago

    I found the difference between affected sites and those that are not!

    The unaffected sites have at least one global attribute. The affected sites have no global attributes, only product-specific attributes.

    @babylon1999 and @xue28, perhaps you could not reproduce the issue because both your test sites have at least one global attribute?

    I can prevent the extraneous New Attribute panel from loading by adding a global attribute. If I remove the global attribute, the extraneous New Attribute panel is back. I tested a few times, and the behavior is consistent.

    I also found this code on line 60 of wp-content/plugins/woocommerce/assets/js/admin/meta-boxes-product.js:

    $( function () {
		if ( ! woocommerce_admin_meta_boxes.has_local_attributes ) {
			$( 'button.add_attribute' ).trigger( 'click' );
		}
} );

    If I comment out the line that triggers the click event for the Add Attribute button in that block of code, and set SCRIPT_DEBUG to true in wp-config.php so that the un-minified version of meta-boxes-product.js is loaded, it also prevents the issue with the extraneous Add Attribute panel from occurring.

    That leads me to suspect that if there are no global attributes, WooCommerce is incorrectly setting the value of the woocommerce_admin_meta_boxes.has_local_attributes object so that the click event for the Add Attribute is triggered when it should not be.

    Forum: Plugins
    In reply to: [WooCommerce] Attributes > New Attribute Panel Loads Automatically On All Variable Products
    Thread Starter linux4me2

    (@linux4me2)

    3 years ago

    Just in case, I downloaded all the /wp-content/plugins/woocommerce files from an unaffected site and an affected site and ran a comparison using diff, but there were not differences between the files of the two sites:

    $ diff -q woocommerce-unaffected/ woocommerce-affected/
Common subdirectories: woocommerce-unaffected/assets and woocommerce-affected/assets
Common subdirectories: woocommerce-unaffected/client and woocommerce-affected/client
Common subdirectories: woocommerce-unaffected/i18n and woocommerce-affected/i18n
Common subdirectories: woocommerce-unaffected/includes and woocommerce-affected/includes
Common subdirectories: woocommerce-unaffected/lib and woocommerce-affected/lib
Common subdirectories: woocommerce-unaffected/packages and woocommerce-affected/packages
Common subdirectories: woocommerce-unaffected/sample-data and woocommerce-affected/sample-data
Common subdirectories: woocommerce-unaffected/src and woocommerce-affected/src
Common subdirectories: woocommerce-unaffected/templates and woocommerce-affected/templates
Common subdirectories: woocommerce-unaffected/vendor and woocommerce-affected/vendor

    I guess that means the issue is coming from something in the database?

    Forum: Plugins
    In reply to: [WooCommerce] Attributes > New Attribute Panel Loads Automatically On All Variable Products
    Thread Starter linux4me2

    (@linux4me2)

    3 years ago

    Hi @babylon1999

    Thank you for trying.

    Clearing my browser’s cache was one of the first things I did, though I didn’t mention it in my first post, as browser-caching can so often cause issues. I also tried two different browsers (Firefox and Chromium), but none of that resolves the issue.

    Of note is that there is no server-caching, either.

    Forum: Plugins
    In reply to: [Menu In Post] JS reference on each page regardless whether Menu-in-Post contained or not
    Plugin Author linux4me2

    (@linux4me2)

    3 years ago

    You’re welcome!

    Thank you for the suggestion.

    Forum: Plugins
    In reply to: [Menu In Post] JS reference on each page regardless whether Menu-in-Post contained or not
    Plugin Author linux4me2

    (@linux4me2)

    3 years ago

    Hi @abitofmind

    I haven’t heard back from you in about about two weeks, so I’m going to go ahead and mark this as resolved.

    Forum: Plugins
    In reply to: [WooCommerce] Attributes > New Attribute Panel Loads Automatically On All Variable Products
    Thread Starter linux4me2

    (@linux4me2)

    3 years ago

    Hi @xue28,

    WordPress lost my entire reply, so I’ll post it again and hope it isn’t duplicated.

    This is a strange behavior, because it doesn’t happen on all the sites I have access to.

    Here’s what I see with a new variable product:

    Here is what I get when editing an existing product:

    Here is the system report with all plugins but WooCommerce disabled and the Storefront theme active:

    `
### WordPress Environment ###

WordPress address (URL): https://test.thedomain.com
Site address (URL): https://test.thedomain.com
WC Version: 7.7.0
REST API Version: ✔ 7.7.0
WC Blocks Version: ✔ 10.0.4
Action Scheduler Version: ✔ 3.5.4
Log Directory Writable: ✔
WP Version: 6.2.2
WP Multisite: –
WP Memory Limit: 256 MB
WP Debug Mode: –
WP Cron: ✔
Language: en_US
External object cache: –

### Server Environment ###

Server Info: LiteSpeed
PHP Version: 8.0.28
PHP Post Max Size: 128 MB
PHP Time Limit: 30
PHP Max Input Vars: 3000
cURL Version: 7.61.1
OpenSSL/1.1.1k

SUHOSIN Installed: –
MySQL Version: 10.5.19-MariaDB-cll-lve
Max Upload Size: 128 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

### Database ###

WC Database Version: 7.7.0
WC Database Prefix: wp_
Total Database Size: 45.66MB
Database Data Size: 26.94MB
Database Index Size: 18.72MB
wp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_order_itemmeta: Data: 0.13MB + Index: 0.09MB + Engine InnoDB
wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_actions: Data: 0.11MB + Index: 0.16MB + Engine InnoDB
wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_logs: Data: 0.08MB + Index: 0.06MB + Engine InnoDB
wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_comments: Data: 0.13MB + Index: 0.09MB + Engine InnoDB
wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_litespeed_img_optming: Data: 0.61MB + Index: 0.83MB + Engine MyISAM
wp_options: Data: 2.47MB + Index: 0.23MB + Engine InnoDB
wp_postmeta: Data: 11.52MB + Index: 7.03MB + Engine InnoDB
wp_posts: Data: 3.52MB + Index: 0.70MB + Engine InnoDB
wp_relevanssi: Data: 6.52MB + Index: 7.55MB + Engine InnoDB
wp_relevanssi_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_relevanssi_stopwords: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_termmeta: Data: 0.14MB + Index: 0.16MB + Engine InnoDB
wp_terms: Data: 0.11MB + Index: 0.13MB + Engine InnoDB
wp_term_relationships: Data: 0.22MB + Index: 0.13MB + Engine InnoDB
wp_term_taxonomy: Data: 0.11MB + Index: 0.13MB + Engine InnoDB
wp_tinvwl_analytics: Data: 0.08MB + Index: 0.05MB + Engine InnoDB
wp_tinvwl_items: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_tinvwl_lists: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_usermeta: Data: 0.05MB + Index: 0.03MB + Engine InnoDB
wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wcpdf_invoice_number: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wcpdf_packing_slip_number: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wc_admin_notes: Data: 0.05MB + Index: 0.00MB + Engine InnoDB
wp_wc_admin_note_actions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_category_lookup: Data: 0.05MB + Index: 0.00MB + Engine InnoDB
wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_product_attributes_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_product_meta_lookup: Data: 0.28MB + Index: 0.44MB + Engine InnoDB
wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wfls_2fa_secrets: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wfls_role_counts: Data: 0.00MB + Index: 0.00MB + Engine MEMORY
wp_wfls_settings: Data: 0.02MB + Index: 0.00MB + Engine InnoDB

### Post Type Counts ###

attachment: 1555
cfredux_contact_form: 4
mc4wp-form: 1
nav_menu_item: 151
page: 121
post: 9
product: 618
product_variation: 2140
revision: 221
shop_coupon: 23
shop_order: 6
shop_order_refund: 180
soliloquy: 1
wp_global_styles: 1
wp_navigation: 1

### Security ###

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

### Active Plugins (1) ###

WooCommerce: by Automattic – 7.7.0

### Inactive Plugins (10) ###

Contact Form Redux: by linux4me2 – 1.3.4
MainWP Child: by MainWP – 4.4.1.1
Payment Plugins for Stripe WooCommerce: by Payment Plugins
[email protected] – 3.3.41

PDF Invoices & Packing Slips for WooCommerce: by WP Overnight – 3.5.4
Relevanssi: by Mikko Saari – 4.20.0
Responsive WordPress Slider - Soliloquy Lite: by Soliloquy Team – 2.7.2
Simple Lightbox: by Archetyped – 2.9.3
TI WooCommerce Wishlist: by TemplateInvaders – 2.5.1
User Role Editor: by Vladimir Garagulya – 4.63.3
Wordfence Login Security: by Wordfence – 1.1.2

### 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)
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: –
HPOS feature screen enabled: –
HPOS feature enabled: –
Order datastore: WC_Order_Data_Store_CPT
HPOS data sync enabled: –

### WC Pages ###

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

### Theme ###

Name: Storefront
Version: 4.3.0
Author URL: https://woocommerce.com/
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: –

### Admin ###

Enabled Features: activity-panels
analytics
coupons
customer-effort-score-tracks
import-products-task
experimental-fashion-sample-products
shipping-smart-defaults
shipping-setting-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
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-page

Disabled Features: product-block-editor
minified-js
new-product-management-experience
product-variation-management
settings

Daily Cron: ✔ Next scheduled: 2023-05-25 16:53:14 -07:00
Options: ✔
Notes: 41
Onboarding: completed

### Action Scheduler ###

Complete: 260
Oldest: 2023-04-24 11:23:12 -0700
Newest: 2023-05-25 09:47:07 -0700

Failed: 2
Oldest: 2023-04-26 07:30:38 -0700
Newest: 2023-05-25 09:49:58 -0700

Pending: 2
Oldest: 2023-05-26 07:07:45 -0700
Newest: 2023-05-26 07:07:45 -0700


### Status report information ###

Generated at: 2023-05-25 09:51:34 -07:00
`

    There are no error logs.

    Forum: Fixing WordPress
    In reply to: PHP Warning: Constant WP_MEMORY_LIMIT Already Defined In wp-config.php
    Thread Starter linux4me2

    (@linux4me2)

    3 years ago

    I believe the problem is that I was led down a rabbit hole when I really just need to remove the WP_MEMORY_LIMIT declaration from my wp-config.php to resolve the warnings in my error log.

    Without the WP_MEMORY_LIMIT declaration, one of the plugins I was using was giving me a warning that WP_MEMORY_LIMIT was only 40 MB. I interpreted that to mean that I didn’t have enough memory allocated to WordPress, even though my server’s PHP memory limit is set to 256 MB.

    However, when I looked at the code in /wp-includes/default-constants.php that handles WordPress’ memory allocation, it’s clear that WordPress only tries to set the PHP memory limit when WP_MEMORY_LIMIT is greater than the PHP memory limit. If it’s the same, as in my case, there is no need to set WP_MEMORY_LIMIT in wp-config.php.

    According to WordPress’ wp-config.php documentation:

    if PHP has been allocated 64MB, there is no need to set this value to 64M as WordPress will automatically use all 64MB if need be.

    Substitute “256” for “64”, and that’s exactly my situation.

    I’m going to remove the wp-config.php WP_MEMORY_LIMIT declaration, which should fix the “problem.”

Viewing 15 replies - 76 through 90 (of 1,795 total)
1 2 3 … 5 6 7 … 118 119 120