MikeCooter

Thanks for the links @anastas10s. Some conflicting observations – I will take note when fault finding.

Thanks @tajperf. I had seen some posts about problems with WooCommerce 8.5.1, I’ll give that a try too.

@rokmeglic – these were GET requests shown in the (backend) live server log. I’m not sure if they translate to front-end CSS. All I know is that it slows things down dramatically.

@sh67 – not quite. After days of testing different combinations, I think it’s a problem between LiteSpeed cache and WooCommerce. Some combinations kick off the stream of GET requests and others don’t. Unfortunately, the existing hosting arrangement became problematic. I’m in the middle of a server migration, once complete I’ll be able to continue testing/diagnosing without the added complication of server errors.

@doublezed2 – currently migrating to a new server, will send logs once complete – thankyou.

@shameemreza – thanks for your suggestions. I found a few of those pages before, but once migrated I’ll take a closer look and see how to move forward.

Hi Sol,

I followed your doc (NB: Meks Quick Plugin Disabler is no good in this situation since it disables WooCommerce & the Payments plugin!) – but none of my plugins were causing the issue.

Finally got down to the bare bones – and switched the active theme to ‘Twenty Twenty One’- and the Buy Now button did indeed display correctly.

Huge shame since I’m using Avada, and they are usually very well integrated with all WooCommerce features.

Perhaps something has been overlooked, maybe the <iframe> containing the call for “https://js.stripe.com/v3/elements-inner-payment-request-xxxxx&#8221; on Product pages isn’t allowed by Avada?

I did notice that on Cart & Checkout pages the ‘Buy Now’ button was placed using <script> rather than <iframe> – that seems to be the only major difference?

Any insights welcome, for the time being I’ll just have to remove the button from my product pages.

Thanks.

Thanks for the feedback Sol, I’ll look into and let you know. ??

Hi Xihad,

Looks like the majority of their styling originates from the ‘Open-Shop’ theme they have used, take a look at this page:

https://themehunk.com/wp-themes/open-shop/

Maybe that gets you what you want?

Hi xihad1,

It’s never as easy as it looks!

Not sure what this has to do with this plugin, but since you’re here, I’ll say this: a good way to figure out how to duplicate a feature one someone else’s site is to first understand where the feature comes from.

If you inspect that page’s code, there is a lot of information in the header.

For instance you can see that they use the following:

THEME:
open-shop
elementor

PLUGINS:
woocommerce
menu-icons
yith-woocommerce-wishlist
contact-form-7
widget-post-slider
annasta-woocommerce-product-filters
jetsticky-for-elementor
wp-popup-builder
yith-woocommerce-compare
ajax-search-for-woocommerce
hunk-companion
sassy-social-share
woo-mini-cart-drawer
smart-slider-3
team-showcase-supreme
dropdown-menu-widget

If I were you, I’d look up each of those items one by one, work out what they do and which ones you need.

Good luck!

Hi @va-cape,

I’ve been battling with the same issue as you, but have managed to get it working.

First of all, I thought that entering the values for [Audience | GroupName] entered in ‘WP Membership > Membership Levels > MailChimp List Name’ would automatically create the MailChimp group for me. It didn’t, and I failed to register with MailChimp.

Secondly, I deleted the [Groupname] suffix from above – and this time was able to successfully create an entry in the MailChimp Audience. I then deleted that entry and tried again with groups.

I followed THIS GUIDE and used the RADIO BUTTON option to create a Group with 2 SubGroups. I then re-entered the [Audience | SubGroupName] against ‘MailChimp List Name’ and registered for a third time.

This time, I failed to create an entry in MailChimp – but the WP Membership DEBUG log informed that because I had PERMANENTLY DELETED my previous MailChimp entry, I couldn’t re-register with that email.

Finally – I re-registered with a different email address, and this time an entry was successfully added to the MailChimp Audience, with the SubGroup status correctly assigned.

In summary:
– groups must exist in MailChimp first for the suffix method to work, and only use SubGroupName
– once a MailChimp entry is deleted, that email is barred

Hope this helps.

• This reply was modified 3 years, 11 months ago by MikeCooter.

Thanks, Mr Clayton.

Still receiving critical errors – just received FTP credentials so will use your advice.

Thank you.

• This reply was modified 4 years, 4 months ago by MikeCooter. Reason: Got FTP login

Is this likely to cause a critical error? Since updating Stripe from 4.5.3 > 4.5.4, every attempt to edit a page gives a critical error.

I’ve just applied the 4.5.5 update, but no change. Currently launching debugging to find the problem.

Thanks.

• This reply was modified 4 years, 4 months ago by MikeCooter. Reason: Wanted to enable notifications

Best of luck with your project ??

Hi Michele,

‘Href’ is the HMTL for ‘hyperlink reference’.

If you are only using a front-end editor, then it is the code that is written when you add a ‘link’. Href identifies the post/page that should be loaded when the link is clicked.

I’d suggest proceeding one step at a time:

• Make a homepage and a target post
• Add an image on home page
• Select the image, and add a link to the post
• Test that it works

Only start experimenting with styles and backgrounds after you get the basics working.

I may be wrong, but from what I can see the thumbnails for each post use a normal ‘href’ and do actually load new pages, rather than ‘expand’ into the homepage itself.

Each page shares a common header, and all use this same animated Gif stretched across the whole screen as a background:
https://payload266.cargocollective.com/1/15/487979/7622927/giphy_o.gif

It appears as if loading a new page does not automatically re-start the animated Gif sequence, giving the appearance of the page being constant.

• This reply was modified 4 years, 4 months ago by MikeCooter.

I think it’s pretty much an essential companion plugin, and very easy to use.

You’ll only need help if you want to do something unusual – and Myles will certainly assist.

Hi Vione,

Not sure I completely understand the error, but I use Myle’s Field Editor plugin as well, and it works perfectly.

One thing I can see there is a very odd file path:

plugins/WP Job Manager Field Editor /wp-job-manager-field-editor.php

The part in the middle does not look like an online file path, it looks like a folder label that has been uploaded manually – I would expect the file path to be:

plugins/wp-job-manager-field-editor/wp-job-manager-field-editor.php

I’m not sure how you have installed the plugin, but if it were me I’d delete it and start again, using:

Dashboard > Plugins > Add New > Upload Plugin

…then navigate to the Zip file on your computer, activating once installed.

If for some reason you have to do it via FTP, then rename the containing folder in /plugins/ to remove spaces and uppercase characters, then upload the unzipped contents of the zip file.

Good luck, Mike

• This reply was modified 4 years, 5 months ago by MikeCooter.
• This reply was modified 4 years, 5 months ago by MikeCooter.
• This reply was modified 4 years, 5 months ago by MikeCooter.
• This reply was modified 4 years, 5 months ago by MikeCooter.