Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter atlinstructional

    (@atlinstructional)

    File generation is off and all caches have been cleared. Problem still exists. I have been able to better isolate but not resolve with Spectra.

    After further testing I have found that the Spectra css is not fully loading for templates that do not contain a <Div class=> but instead use only a predefined pattern. The same behavior occurs when creating any new blank pages that do not yet contain any blocks. Given that you were able to properly hide header blocks, but I am experiencing difficulty on three different sites, it must be some kind of permalinks or database issue related to the way I am modifying the theme. I was able to find another plugin that is hiding header blocks on these pages and have resorted to using that for now.

    Thread Starter atlinstructional

    (@atlinstructional)

    Thank you for the reply and for taking the time to make the video. I did a very simple test header. The following is showing in the page source for all pages:

    <p class="uag-hide-desktop uag-hide-tab">This block should be shown on mobile only.</p>?
    
    <p class="uag-hide-mob">This block should be shown on desktop and tablet only.</p></header>

    However, the following is not included in the page source for the theme-generated pages such as 404 and Search Results, apparently causing hidden blocks to be shown:

    link rel=’stylesheet’ id=’uagb-block-positioning-css-css’ ?
    style id=”uagb-style-conditional-extension” (containing the @media instructions and other css)

    Both of the missing style sections are included in the page source for user generated pages, and the headers display correctly.

    Something must be causing part of the Spectra css to not load with these theme-generated pages, but I haven’t been able to identify the cause as of yet. There is no caching or no other plugins so I don’t really know where to look next.

    Thanks again.

    Thread Starter atlinstructional

    (@atlinstructional)

    This latest update resolved the issue. Thanks for the great support.

    Thread Starter atlinstructional

    (@atlinstructional)

    Here is a test page with 5 products. The first two (without thumbnails ) are newer and work OK. The other three are older and do not work in this version 2.3.9. If I roll back to 2.3.7 they will work.

    https://www.sociopolitical.net/shop-products/

    Thank you.

    Thread Starter atlinstructional

    (@atlinstructional)

    Thanks for the reply. There is no cache with WordPress or the server, and there are no other plugins in use. Example of shortcode is [wp_express_checkout product_id=”1484″]. The error also occurs without shortcode when a product is chosen directly through the Shop page that the plugin created.

    Based on the errors on the WordPress debug log (see my earlier post) the new plugin version appears not able to properly locate the old products in the database. When rolling back to the older version they are located and the transactions are successful.

    Thread Starter atlinstructional

    (@atlinstructional)

    Some additional info: The WordPress debug log indicates the error is related to the following

    …/wp-express-checkout/includes/class-order-summary-table.php on line 48 – Attempt to read property “public” on null

    ?…/wp-express-checkout/admin/includes/class-admin-order-summary-table.php on line 45 – Attempt to read property “public” on null?

    …/wp-express-checkout/includes/class-paypal-button-ajax-handler.php on line 325 – Undefined array key “applied”

    Thread Starter atlinstructional

    (@atlinstructional)

    That was helpful. The download issues were resolved after adding the following:

    header(“X-LiteSpeed-Location: /wp-content/uploads/files/$file_name”);

    Thank you for your assistance with this.

    Thread Starter atlinstructional

    (@atlinstructional)

    That had no effect, but after some more checking I was able to determine that the problem is not specific to the LiteSpeed Cache plugin. The same issues exist with any cache plugin on the LiteSpeed server. There are no issues when caching is disabled on this server, and no issues with caching on non-LiteSpeed servers.

    For purposes of saving time, I think I’ll look around for another forced download script known to work on this server.

    Thanks for your replies.

    Thread Starter atlinstructional

    (@atlinstructional)

    Yes, download URLs are excluded.

    After some further testing I have learned that the reason PDF and JPEG files are being inflated in size and assigned an HTML extension is because the page source from the actual site is being added to the downloaded file. For example, if I open one of the inflated JPEGs with the HTML extension in a browser, then view the page source, I see garbled characters representing the image, followed by the fully legible page source.

    This issue is only occurring when LiteSpeed Cache is enabled. The fopen forced download script is being initiated by a PayPal plugin called WP Express Checkout. I think there must be a serious conflict between this plugin and Litespeed cache. I have made them aware of the issue as well.

Viewing 9 replies - 1 through 9 (of 9 total)