Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloning, Copying and Pushing Sites Sometimes Leave The SSL Toggle In The Incorrect State #27

Open
elindydotcom opened this issue Mar 7, 2022 · 1 comment
Labels
bug Something isn't working Priority: Low Low priority item

Comments

@elindydotcom
Copy link
Contributor

When a site is pushed, cloned or copied to a new site / server, we sometimes make an attempt to get an SSL certificate. But we never flip the SSL toggle on the front end if that attempt to get an SSL certificate is successful.

The site continues to work and be served over ssl so there's no harm to the site or issue with how the site functions. It's just the display that is incorrect.

The workaround is to just flip the toggle on the front-end in the SSL tab.

@elindydotcom elindydotcom added bug Something isn't working Priority: Low Low priority item labels Mar 7, 2022
@SuperHondo
Copy link

Hi

Sometimes is sounding unsure statement, it always does attempts to get SSL. That toggle switch on SSL when flipped Red to Green actually goes to reissue another SSL from LE, instead why not programmically make that toggle go green when SSL is installed successfully OTHERWISE & alternatively when ever a new site is cloned or copied or pushed to new server WPCD shouldn't 'sometimes' attempt to get the SSL instead let the user go and always manually toggle the SSL switch to install one.

What are your plans for users wanting to add theur own purchased SSL & Wildcard SSL instead of LE, would be nice.

Hope it makes sense.
Thankyou.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Priority: Low Low priority item
Projects
None yet
Development

No branches or pull requests

2 participants