Jonathon Leathers

Thanks for the follow-up. I will stick with recommending other plugins when I teach building WooCommerce sites to developers.

This has nothing to do with anything on Stripe but has to do with the code written by the developers of this specific plugin. I only have one Stripe account that is permanently in test mode, that has never changed, but the code in this plugin has changed. You can see that below because the plugin offers different options depending on the URL.

Screenshot from a localhost site
Clicking that link opens a pop-up modal to allow entering in live or test keys.

Screenshot from a live site
Clicking that link takes you to https://connect.stripe.com/oauth/v2/authorize and forces you to fill out a lot of information that is irrelevant for a test store and there is no way to skip it or specify that you are just testing. Unless there is a way to get around this and use the interface from the screenshot above, this plugin is just unnecessarily more complicated for testing compared to the other WooCommerce Stripe plugins that exist.

Thank you both for the suggestions!

There is already a Trac ticket about this and I’ve referenced the solution offered here.

The code shared above, setting the version parameter to null, was the solution for me.

This is why I love SiteGround!

Yeah, that works great in 5.1. Thanks for the change and update Hristo!

Maybe I didn’t explain it well enough but I’m saying the way you have your responsive images feature built will break layouts.

Currently you’re using information from data-srcset to define the value of the “src” attribute. I assume you’re getting the viewport width via Javascript to figure out which image to use. But if the viewport width changes, the browser has no access to the other images defined in data-srcset because you are never setting the “srcset” attribute.

What happens is you end up with a small image even if the screen width gets larger and there are larger images available.

Basically, the “srcset” attribute needs to be added otherwise this is not actually a responsive image.

For anyone with this issue, you can deactivate Yoast SEO to restore functionality of WooCommerce as a quick fix to be able to make changes to anything WooCommerce related.

That doesn’t sound like it makes any sense but if you ever want to disable a plugin when you can’t access your backend you can do so by renaming the folder through FTP.

Login to the FTP of your hosting and rename the Wordfence folder in your “wp-content/plugins” directory. That will disable Wordfence so if that is the problem, you will be able to access your backend again.

My pleasure. Glad you got it working!

When you say “the content of the pages I write” I assume you are referring to anything you’re adding to the WYSIWYG editor for a page/post. In which case, that is all content stored in the database.

If that’s the case and all you want to do is add HTML to the content, you can do this from the WYSIWYG editor. In the top right corner there are two tabs: Visual and Text. Click on Text and it will show you the HTML of the content (for the most part, it doesn’t include all of the markup). For the Text view you can write HTML of your own.

What you are looking to change is likely in one of two places:
1) The database
2) The theme files

If it’s in the database then you can make whatever changes you want by simply editing the posts/pages in the backend of WordPress.

If it’s in the theme files then you need to access the server through FTP and go to “wp-content/themes/[your-theme]/”. That folder will have all of the theme files which creates the basic structure of pages the content is output into.

If it’s the theme files you need to edit then I would recommend creating a child theme and editing the necessary files there. You can read more about how to do this and why here.

raker3, that code should be placed in the functions.php file of your theme. So:
wp-content/themes/[your-theme]/functions.php

This fixed the issue for me. Thanks Kaspars.

If you have specific questions then I’m happy to help answer them.

You’re very welcome!

In the style.css file of your theme or child theme, find the following:

.main-navigation ul ul li {
    z-index: 99999999;
    position: relative;
    background-color: #000;
    left: 0px;
    width: 200px;
}

Change it to this:

.main-navigation ul ul li {
    z-index: 99999999;
    position: relative;
    background-color: #000;
    left: 0px;
    width: 200px;
    display: block;
}

That will make all sub-navigation items appear on their own line.

Absolutely, I’m always happy to answer any questions if I can.