-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Button Text for Paid Posts #901
Comments
Hey @danielherndon, I couldn't reproduce this. Would you be able to give me an URL to the post that has this issue? |
Thanks for checking. This link is one where I am seeing this: https://www.danielkherndon.com/cereal-and-ivy-league/ You have to be a logged-in user who is not a paid user. One thing I have not checked is to see if this was something caused by cache on my browser, although I would be surprised. |
I confirm that it's reproducible and it's not related with your browser cache. We're aware of this issue and let you know when it's fixed. In the meantime, could you add this CSS workaround as a code injection until it gets fixed? <style>
.gh-post-upgrade-cta a.gh-btn {
color: var(--ghost-accent-color);
}
</style> |
Thank You! I appreciate the help. |
refs TryGhost/Casper#901 - the site accent color property on default cta for upgrade link had a typo and was using wrong accent color property
refs TryGhost/Casper#901 - the site accent color property on default cta for upgrade link had a typo and was using wrong property
Closed with TryGhost/Ghost@e05889c, will be out in next Ghost release. |
refs TryGhost/Casper#901 - the site accent color property on default cta for upgrade link had a typo and was using wrong property
Hey folks,
Just discovered (Casper) that when a post is for paying subscribers, and a logged-in free subscriber views it, the text on the button is white and doesn't appear.
In an effort to ensure I'm seeing the issue clearly, I removed all my code injections to see if my CSS additions were the source of the problem, but that didn't change anything.
Excited to finally see what that button says!
The text was updated successfully, but these errors were encountered: