George Appiah

This is just a standard checkout page ??

This will not be a page you create manually, but something to be provided by whatever solution you choose to sell your stuff.

You need to give more thought to what you’re trying to accomplish/sell overall, and not just the look of this single checkout page, as this single page may likely be a tiny (though important) part of the overall solution.

Are you selling a ton of products (physical or digital) that need a catalogue to manage inventory, shipping options, and all the stuff that goes with a typical e-commerce store? You probably want to use WooCommerce, the de-facto e-commerce plugin for WordPress.

Are you selling a handful of products and don’t need to manage inventory and whatnot?

Are you selling downloadable only (no shipping required)?

Are you selling recurring membership subscriptions?

Are you selling access to online courses (e-learning)?

I could go on and on, but I hope you see the point.

While WooCommerce can power all these (and more), it may not be the optimal solution for every situation where you sell something on your website.

So what exactly are you trying to accomplish with this checkout page? Can you provide more context to your question?

OK, found this in the documentation:

If you are using non-pretty permalinks, you should pass the REST API route as a query string parameter. The route https://oursite.com/wp-json/ in the example above would hence be https://oursite.com/?rest_route=/.

So /?rest_route=/wp/v2/search is for non-pretty permalink.

Since we have a query parameter in there already, to add a second query parameter, we need to use & rather than ?, so these two queries are identical and both work:

With Pretty Permalink:
https://swelteringaunt.s2-tastewp.com/wp-json/wp/v2/search?per_page=5

Without Pretty Permalink:
https://swelteringaunt.s2-tastewp.com/wp-json/?rest_route=/wp/v2/search&per_page=5

I’m not sure if I understand your question correctly, but the following URL works on my test site:

https://swelteringaunt.s2-tastewp.com/wp-json/wp/v2/search?per_page=5

Home page is set to latest posts but Sample Page appears

Nope, it’s not the “Sample Page”.

What you’re seeing on your homepage is the latest post or “Blog Home” template from the Twenty Twenty-Four theme. You can find the latest posts at the bottom of this pages as a simple list (under “Watch, Read, Listen”).

If you want to use this theme but prefer a traditional “Latesst Post” blog listing, either customize the default “Blog Home” template… or create a custom “Front Page” template. With a full-site editing theme like Twenty Twenty-Four, you can do either of these options easily in a few clicks without writing a single line of code.

Good luck!

I am using in the bottom footer the WP Facebook jetpack live widget to show our daily Facebook posting on ten of our websites.

I recommend asking in the JetPack plugin’s own support forum… so the plugin’s developers and support community can assist you: https://www.ads-software.com/support/plugin/jetpack/

Good luck!

it seems to redirect them to an already existing post (/wp-login)

Can you tell us exactly what your users are seeing and not what “seems” to be? What’s the FULL URL they start from? And what’s the FULL URL they ultimately land on? Is there any error message? Can you share a screenshot of this?

Note that going to example.com/wp-admin/ will redirect you to the actual login page at example.com/wp-login.php. That’s how WordPress works, and that, in itself, is not a problem.

Sorry I forgot to mention that the other writers (and myself) have no issues I don’t know if that’s because we use wp-admin/ ?

What URL are these users going to to log in? That’s where the problem might be: they might just be using the wrong login URL.

I had a few minutes to spare before retiring to bed, and I was able to quickly whip together this demonstration which — according to you — should be impossible ??

Demo WordPress Multisite site: https://cftest.fun

The domain has a wildcard SSL certificate from Let’s Encrypt, which can be verified here: https://www.ssllabs.com/ssltest/analyze.html?d=cftest.fun

Here’s a multisite (virtual) subdomain demo, with a valid certificate:
https://multisite-dubdomain-demo.cftest.fun/

And to really test this, pull up any random subdomain you can think of: you should be taken to the Multisite signup page to register this non-existing subdomain site. But you’ll not see any certificate error/warning — because this Multisite installation has a valid Let’s Encrypt wildcard certificate covering any virtual subdomain you can think of. Here’s a random latest: https://hfdgashgfaayuegyudfuydgfhgfgewfsyur.cftest.fun

The advice goes against anything I have experienced with LE.

That’s hardly a valid reason to throw away other people’s experiences though ??

See my last response to your other post on the same subject here: https://www.ads-software.com/support/topic/network-multisite-ssl-not-covering-virtual-sites/#post-18056667

Good luck!

https://workplace.lifetoolscorporationltd.co.uk/

The SSL error on this page has nothing to do with Let’s Encrypt or even WordPress Multisite virtual subdomains.

You already have a Lets Encrypt wildcard subdomain certificate for lifetoolscorporationltd.co.uk. Please see: https://www.ssllabs.com/ssltest/analyze.html?d=lifetoolscorporationltd.co.uk

But on the subdomain workplace.lifetoolscorporationltd.co.uk, you’re loading a certificate issued for vps4.lifetools.com. So there’s a certificate/hostname mismatch, hence the ERR_CERT_COMMON_NAME_INVALID privacy warning.

This is a server/vhost misconfiguration.

LE simply does not support wildcards to cover virtuals.

Did you even bother glancing over the official documentation I linked to?

DNS-01 challenge

This challenge asks you to prove that you control the DNS for your domain name by putting a specific value in a TXT record under that domain name. It is harder to configure than HTTP-01, but can work in scenarios that HTTP-01 can’t. It also allows you to issue wildcard certificates. After Let’s Encrypt gives your ACME client a token, your client will create a TXT record derived from that token and your account key, and put that record at _acme-challenge.<YOUR_DOMAIN>. Then Let’s Encrypt will query the DNS system for that record. If it finds a match, you can proceed to issue a certificate!

Emphasis mine.

Of course, you’re free to believe what you want.

Good luck!

My understanding is Let’s Encrypt does not cover virtual domains via a wildcard; it can only cover main domains or actual subdomains.

That “understanding” is totally wrong.

Let’s Encrypt supports two validation methods (or challenge types): HTTP (HTTP-01 challenge) and DNS (DNS-01 challenge). See the official documentation here: https://letsencrypt.org/docs/challenge-types/

For virtual (sub)domains, you cannot use the HTTP validation method… because there’s no place to put the acme-challenge token. So you MUST use the DNS validation method by adding the challenge token to a _acme-challenge.<YOUR_DOMAIN> TXT record.

If you’re using some hosting control panel or provider that does not permit DNS validation, then that’s where the limitation is… and not Let’s Encrypt.

I recommend using the dedicated support channel for Astra, so the team that is most familiar with this theme can assist you.

If you’re using the free version, post your issue here: https://www.ads-software.com/support/theme/astra/

If you’re using the PRO (paid) version of the theme, go to the vendor’s site to post your issue there, as commercial products are not supported here at www.ads-software.com: https://wpastra.com/contact/

Good luck!

• This reply was modified 2 weeks, 2 days ago by George Appiah.

Disallow the path https://sekhoforex.com/lp-profile/ in your robots.txt file to tell Google to NOT index these URLs.

It’s not EVERY page on a site that should (or even can) be indexed: login pages, password-protected pages, etc. There’s no point indexing these sort of pages.

While the site uses Cloudflare, it’s not configured for full-page HTML caching at all (cf-cache-status: DYNAMIC [1]). So this is not likely Cloudflare-related.

From my end, I see the same Astra-theme site (shown below) on both desktop and mobile.

[1] – https://developers.cloudflare.com/cache/concepts/cache-responses/

Try:

.navbar-nav li {
    margin-bottom: 10px;
}

Adjust the margin value as desired.