ive just completed fixing a wordpress site, its hosted with godaddy and uses cloudflare.
I have a valid ssl certificatie managed by godaddy autossl
when you visit the site and its pages firefox browser shows that the site is secure, its shows the padlock icon in the address bar.
But when you visit other pages on the same domain and use the https prefix, it says the connection is not secure. I checked the source code of these pages and they do not contain any https:// unsecure links. Note that these pages are not in the WordPress site, but seperate html pages in the same domains location (on the server)
https://www.oilstainsremedy.com/landingpage.php
https://www.oilstainsremedy.com/adtest.html
So why is this?
]]>I just generated my first google merchant center feed with ctx plugin. I uploaded this feed onto my merchant center and it says the ssl certificate has expired. My site already has SSL and it isn’t expired. Is there something wrong with my feed setup?
]]>I have recently migrated my website to staging folder in the server. After moving I found out that the pages , posts , images are not showing at all. I checked the database the data is there and the files are there in the server as well.
Then I found data from the database is not at all syncing properly.
How can I update the data as well in the website.
]]>It came to our attention that the previous email had links that were not easily accessible. We apologize for any confusion. Here are the correct links to the support articles with detailed instructions below:
? <u>Entrust to DigiCert SSL Certificate Migration (KA-05545)</u>
? <u>Latest Version of Authorize.net Server-Level SSL Certificates (000003009)</u>
Who is being affected: Merchants who utilize Authorize.net APIs and endpoint URLs in their websites or applications will need to make updates. They will need to integrate and use the newly-issued Root and Intermediate (CA) SSL certificates from DigiCert. This should be done before the scheduled revocation dates to avoid disruptions.
What you need to do: You must integrate and use the newly-issued Root and Intermediate (CA) SSL certificates from DigiCert by October 24 to avoid any disruptions. To help you fight fraud, AFDS is automatically enabled on your account, which gives you access to many powerful fraud filters, including:
Sincerely,
The Authorize.net team
]]>Authorize.net?is updating the SSL/TLS certificates used for secure communication with our systems. This change affects both browser-based and server-to-server interactions.?
Who is being affected: Merchants who utilize Authorize.net APIs and endpoint URLs in their websites or applications will need to make updates. They will need to integrate and use the newly-issued Root and Intermediate (CA) SSL certificates from DigiCert. This should be done before the scheduled revocation dates to avoid disruptions.
What you need to do:?You must integrate and use the newly-issued Root and Intermediate (CA) SSL certificates from DigiCert by October 24 to avoid any disruptions. To help you fight fraud, AFDS is automatically enabled on your account, which gives you access to many powerful fraud filters.
Is this something you need to do at the plugin level or something we need to address at the server level?
]]>