wimorrison

I have WPO setup to

1. served cached version to mobile users
2. not to serve cached versions to logged in users

According to the form developers (Ninja Forms) the Ninja CSS file is missing in the cached version (though they do not say this is causing the issue). What I know is that the version I see as a logged in user i.e. admin, or plain user, is correctly displayed however the pages is displayed incorrectly when served to a member of the public i.e. a user who is not logged in. This is the basis for my assumption that there is something being done by the caching which is causing the issue.

I have not disabled WPO caching, can I achieve this by simply deactivating the plugin, testing then reactivating it?

Many Thanks

Iain Morrison

Thank you. This was also my suspicion (though it was only a guess by me!) and I have posted a question on the Bright Plugins forum asking them to take a look.

These are the line in the files that this link recommends to amened when seeing an out of memory limitation Increasing the WordPress memory limit: documentation – WooCommerce

.htaccess

php_value memory_limit 256M

wp-config.php

define (‘WP_MEMORY_LIMIT’, ‘256M’);

However I cannot find the line /* That's all, stop editing! Happy publishing. */ in my wp-config.php file which might suggest that it was changed by the person who wrote the site?

I have not been able to find a PHP.ini file

• This reply was modified 1 year, 3 months ago by wimorrison.

Hi,

Been away for a few days hence the delay in replying 🙁

I get this error shown on my screen when trying to open the Home Page

Error: Loading CSS chunk 9001 failed. (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/chunks/9001.style.css?ver=64ff0eaf842e0f4c83f1)

and the details are:

at Lazy at Suspense at W (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:537853) at div at div at Ao (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:619023) at div at Sw (https://009society.com/news/wp-includes/js/dist/components.min.js:26:215774) at kw (https://009society.com/news/wp-includes/js/dist/components.min.js:26:216451) at Pw (https://009society.com/news/wp-includes/js/dist/components.min.js:26:216796) at w (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/admin-layout/index.js:1:1989) at Po (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:619617) at Oo (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:619411) at https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:622513 at https://009society.com/news/wp-includes/js/dist/data.min.js:9:3292 at WithSelect(Component) (https://009society.com/news/wp-includes/js/dist/compose.min.js:9:18949) at https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/data/index.js:2:140267 at O (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:515229) at A (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:514670) at a (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:509181) at https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:622766 at https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/data/index.js:2:141344 at https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/data/index.js:2:138219 at https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/data/index.js:2:138219 at https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/data/index.js:2:139441 at pi (https://009society.com/news/wp-content/plugins/woocommerce/assets/client/admin/app/index.js:2:657505)

WooCommerce appears to be working correctly in all other respects, just this one issue

I thought that the too, i used was the same thing – why are there 2 tools doing the same thing – and showing different CSS in each one?

Matters not, placing it using the tool you suggest has worked!

THANK YOU very much for your patience 🙂

• This reply was modified 1 year, 5 months ago by wimorrison.

Fi, thanks for the suggestion. Unfortunately it doesn’t seem to work 🙁

This the existing Custom CSS that is ‘active’ in the site Appearance, which is where I assume I should be placing the text you supplied? I inserted at the end, and also at the top but it doesn’t seem to affect the AWS search box at all.

.wrap {
font-size: 16px;
font-weight: normal;
}

.woocommerce-breadcrumb {
font-size: 1.2em;
font-weight: bold;
}

.woocommerce-loop-category__title {
font-size: 1.2em;
font-weight: bold;
white-space: normal;
text-align: center;
}

.woocommerce-loop-product__title {
font-size: 1em;
font-weight: bold;
white-space: normal;
text-align: center;
}

p {
font-size: 1em;
}

.main-navigation a:hover {
padding: 10px;
}

.main-navigation ul#top-menu {
margin-top: 0px;
}

.select2-container--default .select2-results__option--highlighted[data-selected] {
color: #ffffff;
}

.woocommerce-account form select,
.woocommerce-account form textarea,
.woocommerce-account form input[type="tel"],
.woocommerce-account form input[type="text"],
.woocommerce-account form input[type="email"],
.woocommerce-account form input[type="password"],
.woocommerce-checkout form select,
.woocommerce-checkout form textarea,
.woocommerce-checkout form input[type="tel"],
.woocommerce-checkout form input[type="text"],
.woocommerce-checkout form input[type="email"],
.woocommerce-checkout form input[type="password"] {
background-color: #fff;
color: #000;
}

.colors-dark input {
color: #121010;
}

The issue was being caused by another plugin