Clever use of inline styles and !important by the plugin developer, but try this:
.kjo-link {
clip: rect(1px, 1px, 1px, 1px);
position: absolute !important;
}
Just out of curiosity, what instructions did the plugin developer give you?
The developers instructions are below:
“Calendar is released under the GPL which permits you to copy, modify and redistribute the plugin as you see fit after you have downloaded it. So long as credit to me, Kieran O’Shea, is maintained within the source then you can remove the link and make any other changes you want.”
I wasn’t sure how to go about doing that though!
Sadly I popped your suggestion in the CSS but it didn’t seem to work … any other thoughts most appreciated!
I noticed you forgot the period; it should be .kjo-link.
As for maintaining credit, that’s a bit trickier because the developer wrote the styles directly to the page and doesn’t use a separate stylesheet. You could write a note on your “About Us” page saying that the calendar was developed by Keiran O’Shea and provide a link to the developer’s website.
Amazing – of course I did! Your code did work thank you, and great idea about the about page too.
Thank you again!
Hi Stephen…
Just wondering if you can give a newby a hand. I too wish to eliminate the developers name at the bottom of the calendar (but do intent to give proper credit in another location on website). Your code recommendation seems to have worked well for the person who previously asked — can you assist by explaining where exactly in the developers code I am to paste your code to make the change?
Thanks very much!
crys56 – Don’t edit the theme files directly, otherwise your changes will be overwritten whenever the theme is updated.
An easy way to add custom CSS is to install the Jetpack plugin and activate the Custom CSS module. You’ll then add your custom CSS in the new stylesheet editor that’ll appear in your dashboard, under Appearance > Edit CSS.
As alternatives, you could either install a standalone custom CSS plugin, or create a child theme.
In future please start a new thread as it’s unlikely anyone will spot this reply on a year-old thread that’s already marked as resolved. 🙂
