Hide plugin

Why don’t you use this nifty

“<!– this is a comment –>”

stuff?

M.

Because I don’t want my comments to end up in the source of my website 😉

Hiding comments could be very useful…don’t have time to try it right now but will at some point 😊

It’s also nice to be able to temporarely hide a piece of code.

{exp:hide}
<h2 class="sidetitle">Categories</h2>

{exp:weblog:categories weblog="{master_weblog_name}" style="nested"}
<a href="http://{path=/index}">{category_name}</a>
{/exp:weblog:categories}

{/exp:hide}

If anyone finds it useful I might submit it.

It

If you have ee tags inside of that, does that stop them from being parsed as well as hiding them? Or just hide them?

Maybe Rick or Paul should answer that one. If I’m not mistaken EE tags are parsed inside out, so in the example above the categories will be parsed first and then hidden (thrown away).

That’s all the plugin does at the moment, return nothing.

I really needed to add some comments to my template code today and couldn’t find a way to do this yet so I ‘wrote’ a plugin.

Does your template use PHP? I occasionally use

<? php // Comment line one // two // and three ? >

I like the idea… being able to hide stuff while working on the code, or extracting parts of troublesome code.

IIRC there was a thread somewhere that discussed being able to reverse the order of parsing, then it would also reduce the server time.

Yea, you add parse=”inward”, if you search on parse in the user guide, it’ll come up. I”m not sure if magic doohickeys have to be done within the plugin to make it work, though.

I just uploaded a new version and downgraded it to 0.2 because it needs some more work. Added a ‘style’ parameter to specify what comment style you want to use.

{exp:hide} This is the default style (none) which will just hide the entire code or text and nothing will show up in the source of your browser

{exp:hide style="html"} <!– for HTML style comments –>

{exp:hide style="css"} /* CSS comments */ (using the values “php” or “js” will return the same style for PHP or JavaScript comments)

There are still some things to work out, one of them is nesting. For example, this won’t work:

{exp:hide style="html"}
{exp:hide}
code or text you want processed 
{/exp:hide}
{/exp:hide}

I will be away untill after the weekend, enjoy!

Cool idea.

I’ve been doing a lot of plugin stuff myself recently and I’m pretty sure you are correct about the parsing. Plugins seem to be the last thing to go through the engine. So if an EE tag is in there it will get parsed and then the plugin will hide it afterwards so you can’t use your plugin for a performance gain of any kind.

But I like the idea of having comments hidden from users while still being able to view them in your templates. It would also be interesting to add the ability to have it not hide them in the source when a person logged in as a certain member group is viewing the page. So admins could still open the source and see comments but normal users would not.

Jamie

Of course it just occurred to me a simple conditional could do the user group thing too. But it would be nice to cut down on tags by having the plugin handle that.

Does anyone know if this plugin is still available? I’d like to “hide” some of my EE code for testing purposes. Thanks!