Navilan

Hello, If you are using this plugin to generate a menu, then you should add the code to the `begin_node` event. If you still have issues after that, please do...

@llonchj, @jonafato - Couple of points: 1) My coverage summary shows 74% overall (instead of the 86% above) 2) How important useful will it be to get to 99%? Lot...

@pradyunsg - Thats true. @llonchj has been trying to increase coverage so that we can be reasonably confident about python 3.x compatibility. Tests do have diminishing returns, so the goal...

@llonchj: @callaa's problem is a specific one in that his path has dots, but they are not file extension related dots and hence they are being missed. So his suggested...

> And this is why hyde server source code has to be modified, creating sort-of-coupling between the plugin and > core functionality, including this current bug. This is the reason...

Hi, All files under the `content` folder are considered content. `.htaccess` might have template structures that get transformed as well. If you do not want the `.htaccess` file to be...

Just reread your comment in the lakshmivyas/hyde repository. If your .htaccess file seems to be wrapped in html - you probably have `auto_extend` enabled. Adding `extends: false` will solve that...

Not right now. But its simple enough to write a plugin to do it after regeneration. You can set the media_url property in 'site.yaml` to an empty string in that...

@jfaust - [setting](https://github.com/hyde/hyde/blob/master/hyde/ext/plugins/css.py#L43-L44) `users_template=False` will keep the imports as is. The reason for using includes is to maintain the dependency links for incremental generation. I agree that it is surprising....

Can you share your source on github?