SaladGoat

Hi @bizanimesh thanks for having a look. I use NoScript extension on my browser and didn’t realize I had not given permission to the http version of the site. ???♂?

Once I did that, the link did re-direct to the secure page.

But it still begs the question, why is the link sending to the http address instead of the https address?

Report sent. Thank you!

I have posted to the other forum. Thank you for your guidance.

Thanks for a quick response.

I have WooCommerce, WooCommerce Payments, and WooCommerce PayPal Payments plugins installed and activated.

The checkout gives credit card option or PayPal option, which is what I want.

But I need the payment to go into the PayPal account, not a personal bank account, and that’s where I’m stuck. Since all the plugins are integrated with each other, I don’t even know which one I am looking at when I look in the settings, so I thought posting to the “parent” plugin would get me the support I need.

Thanks!

My question to you, in regard to your video: are you using a chrome-based browser?

This only happens in Google Chrome and Microsoft Edge. It does not happen in Firefox. (I have not tested it in any other browsers.)

I disabled all plugins and it still happened. I am already using TwentyTwenty theme (well, a child theme of that). I tried it on other sites using different child themes of different themes. I tried it on a site using an original theme. This happens in all cases on chrome-based browsers but not on Firefox.

I installed and activated the Health Check plugin and did the Troubleshooting mode. Disabled all plugins except Classic Editor. Switched to TT3 theme. Same result.

You say you only have Gutenberg active. But this is the Classic Editor plugin I’m talking about. I don’t have the Gutenberg plugin. Maybe that is “helping” put things right for you? Or maybe you’re not using a chrome-based browser?

You have copied the link and then pasted it. Yes, that works just fine. I’m talking about dragging and dropping it. I guess I’m just not great at explaining with words, so here are some images.

On a mostly unrelated note not worthy of response, I find it awfully ironic that I’m being forced to use the wholly confusing block editor to discuss the superior Classic Editor.

Not at all. You keep switching to Visual, and using Lorum text. Neither is needed for this bug.

Just insert an image in the Text (not Visual) tab. It will produce the img src html. In that html, highlight the FULL url (from https to jpg), not including the quotes. Now click it and drag to a new area of the post – right after the final > if you like. Everything from https to the image name is stripped away, leaving only the image name and extension.

No screencast, sorry, but here are the exact steps:

1. Start a new Post.
2. Click Add Media button.
3. Drag image to browser and drop it.
4. Wait while it uploads.
5. Click Insert into post button.
6. Looks something like this (angle brackets removed):
   img src=”https://www.foo.com/FUP/wp-content/uploads/2023/02/image-800×600.jpg” alt=”” width=”800″ height=”600″ class=”alignnone size-large wp-image-29368″
7. Highlight the absolute url (underlined for demonstration):
   img src=”<span style=”text-decoration: underline;”>https://www.foo.com/FUP/wp-content/uploads/2023/02/image-800×600.jpg</span>&#8221; alt=”” width=”800″ height=”600″ class=”alignnone size-large wp-image-29368″
8. Drag that url to another part of the Post.
9. Drop it there.
10. Blam! Relative url:
    img src=”” alt=”” width=”800″ height=”600″ class=”alignnone size-large wp-image-29368″
    image-800×600.jpg

Did that help?

Thanks!

They changed the IP address of my site and now the images are loading fine. Thanks!

Thank you for your quick response. I have tried without the security plugin but it was the same result. Not surprising, since I have been using that plugin for a few years and your CDN has worked fine up until recently. I have forwarded your screenshot to my hosting provider to find the problem.

As I was the OP and I did respond, it seems to me it should not have been marked Resolved. Not my forum though, so not my rules…. ???♂?

So I did this:

1. Deactivate Jetpack
2. Delete Jetpack
3. Upgrade to PHP 7.4
4. Update WordPress from 6.0.3 to 6.1.1
5. Install Jetpack
6. Click to Setup Jetpack
7. Receive error: The Jetpack server was unable to communicate with your site [HTTP 500]. Ask your web host if they allow connections from WordPress.com. If you need further assistance, contact Jetpack Support: https://jetpack.com/support/

So I talked to my web host and they could find nothing wrong, and then I was able to connect. Huh?

Result: First try uninstall and reinstall Jetpack did not work; second try did work.

Thanks!

Why was this marked as Resolved when it absolutely is not?

I have changed back to Unresolved. Please fix this.

• This reply was modified 1 year, 11 months ago by SaladGoat.

I followed Steps 1 & 2, then upgraded PHP to 7.4 then re-installed Jetpack. On Activate, I got the message:
The registration secrets sent by your site do not match the ones the Jetpack server has on record.
When clicking Setup Jetpack I get the error:
An error occurred. Please try again.
Trying again got the same error message.
I downgraded to PHP 7.3 and tried activating Jetpack and all was fine!
(All stats were retained, but it didn’t remember what Modules were activated.)

My point is that the forum is called Requests and Feedback. If the Team isn’t reading it, then it’s a bit of a pointless forum, isn’t it? If every request someone posts is met with “you should post that in core.trac” why not just remove the forum and redirect to that in the first place?

Thanks for the links. Very involved (for my non-programmer brain) but I will read it a few dozen times and see if it sinks in. lol

@threadi This forum is called Requests and Feedback … I guess I don’t know what is the point of a forum for Requests if nobody from the Core team actually reads them….

@chiragpatel I wouldn’t know the first thing about writing custom code for that. If you can point me in the right direction, I’d appreciate it.

Thanks!