Hi Guys,
It has happened several times already that I have found a solution to an issue, but I can't really see them, because the link is hidden.
For example, I googled an issue that really interested me and have discovered that Beda had posted a link to the solution/erratum:
https://toolset.com/forums/topic/toolset-view-load-css-in-div-displaynone-but-google-indexes-css-as-keywords/
Brilliant, but, dang! Hidden link!
Facepalm.
I'd like to remove the "views-extra-css-ie7" div and this from the page source:
//-----------------------------------------
// Content Template: Some example content template.
//-----------------------------------------
I don't enter CSS into templates anymore, I use Generatepress Hooks for that, and it adds them into the head only on URLs where I need it.
Guys, where is the solution? I suppose the link to the thread that I've posted will also get hidden.
Cheers,
Tom
Hi, a while back we implemented hidden links to protect login URLs and other private project links. If you place an "@" symbol before a link in your reply, it will be public. Otherwise, it's private. Lots of older posts were created before the "@" symbol workaround, so those links are private by default. If there's a link you want exposed in another thread, I can do that as long as it's not a link to a client's personal project. Here's the link from Beda's post: https://wp-types.com/errata/remove-unused-style-and-type-attribute-from-the-style-element/
I'll update that post so the link is exposed for others. Sorry for the inconvenience!
Hello Christian,
Thank you for the quick response. Yes, I understand it is for privacy reasons. However, I suppose the toolset.com and wp-types.com domains could be excluded from that.
As for the issue, the erratum reads that it was resolved in Views 2.6, but in Views 2.8.3 I still get this in my page source:
"views-extra-css-ie7" script/div and this:
//-----------------------------------------
// Content Template: Some example content template.
//-----------------------------------------
This was the subject of that thread. It seems to me that Beda's link refers to something else (though related), because the erratum mentions 'head', and I see this stuff in the footer.
Of course, it's not a big deal, but it's kind of irritating seeing that in the page source. I don't enter CSS into templates anymore, I use GeneratePress Hooks for that, and it adds them into the head only on URLs where I need it.
If possible, I'd like to disable custom CSS completely for Content Templates/Views to keep the page source cleaner. Yes, it was very convenient when I started with Toolset and it's great that such an option exists. But now I think that managing it in GeneratePress Hooks is a better way and I deleted all my CSS from Content Templates and Views. I also dequeue jQuery where I don't need it, so it wouldn't work anyway.
Cheers,
Tom
At this time there is no filter or setting to remove those bits of code from the page source or completely disable Content Template or Views CSS, but I encourage you to submit your request over here: https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
This will put your suggestion in front of the people who make decisions about new features to include in upcoming releases.
Hello Christian,
OK, fair enough, thanks a lot.
Cheers,
Tom
