Issues page on github
There is an issues page http://github.com/vti/bootylicious/issues on http://github.com where you can post your feature request or a bug report. I am trying to fix bugs and write new features as soon as possible.
There is an issues page http://github.com/vti/bootylicious/issues on http://github.com where you can post your feature request or a bug report. I am trying to fix bugs and write new features as soon as possible.
Bootylicious was released on CPAN couple of weeks ago. All the plugins are moving there also.
Available plugins so far are:
Bootylicious::Plugin::GoogleAnalytics
And parsers:
Other files are moving to CPAN also, but slowly.
New i18n plugin translates strings,
localizes time and adds template helper for translating your own strings.
Configuration is as easy as usual (e.g.
ru locale):
"plugins" : [
"i18n", {"languages" : "ru_RU.UTF-8", "helper" : "loc"}
]
Use loc helper in templates:
<%= loc('My string to be translated') %>
Helper name is configurable (thanks Sebastian Riedel for a good advice):
<%=l 'My string to be translated' %>
or even
<%=_ 'My string to be translated' %>
To create a new localization use Bootylicious::I18N::ru as an example. Plugin requires MojoX::Locale::Maketext.
Thanks to the latest Mojo Unicode support updates, bootylicious Unicode support is a way better now. You can use any UTF-8 symbol in the article title, tag, search parameter etc.
The next step is going to be a localization plugin. Stay tuned!
Thanks to new ep templates from Mojo bootylicious templates are much cleaner now.
If you've created your own templates and don't want to change anything just set template_handler option in configuration file:
"template_handler" : "epl"
Bootylicous will use your epl templates like it did before.
It is now possible to format the dates as you like while changing only one option in configuration file.
With:
"datefmt" : "%a, %d %b %Y"
you will get all the power that strftime has.
As you might have already noticed I've added http://addtoany.com/ widget to index and article pages.
I've done this by changing http://addtoany.com/ widget a little and have added it to index.html.epl and article.html.epl templates.
Ever wondered how to get rid of debug information while running bootylicious in production?
Now you can control it with a new loglevel option:
"loglevel" : "debug" | "error" | "fatal" | "info"
If you run perl bootylicious.pl inflate you will get the output close to this:
$ perl bootylicious.pl inflate [mkdir] /home/vti/bootylicious/templates [exist] /home/vti/bootylicious/templates [write] /home/vti/bootylicious/templates/index.html.epl [exist] /home/vti/bootylicious/templates [write] /home/vti/bootylicious/templates/archive.html.epl [exist] /home/vti/bootylicious/templates [write] /home/vti/bootylicious/templates/index.rss.epl [exist] /home/vti/bootylicious/templates [write] /home/vti/bootylicious/templates/tags.html.epl [exist] /home/vti/bootylicious/templates [write] /home/vti/bootylicious/templates/tag.html.epl [exist] /home/vti/bootylicious/templates [write] /home/vti/bootylicious/templates/article.html.epl [exist] /home/vti/bootylicious/templates [write] /home/vti/bootylicious/templates/page.html.epl [exist] /home/vti/bootylicious/templates [write] /home/vti/bootylicious/templates/draft.html.epl [mkdir] /home/vti/bootylicious/templates/layouts [write] /home/vti/bootylicious/templates/layouts/wrapper.html.epl
All bootylicious templates will be in the templates/ directory.
Here is a sample Apache + FastCGI configuration. I have it working on my local machine, so all the configs are ArchLinux compatible :)