[lang_en]Yesterday I released an update of @stash making it v1.3. It comes with a number of new interresting features and last but not least it has support for RapidWeaver 4.0 so that you can continue using this neat plugin after you have updated your favourite webdesign tool.

So lets start going through the features…[/lang_en]
[lang_sv]I går släppte jag en uppdatering av @stash till v1.3. Den har ett antal nya intressanta funktioner och sist men inte minst den fungerar med RapidWeaver 4.0 så att ni kan fortsätta använda det här finurliga plugin:et även efter att ni har uppdaterat er favorit-webbeditor.

Så låt oss gå igenom dom nya funktionerna… (resten är på engelska)[/lang_sv]

Smart tags
The first feature is ”smart tags”, yes you read right, the @stash tag have become smart. You can now create a code snippet with special tags that you can later replace with values define in the @stash tag that you use to insert the snippet.

You can turn any code snippet into a ”smart tag” by adding one or more user replaceable variables to the snippet. To do so just put {{your_variable_name}} in the position where you want to be able to replace something. Then when you want to use this snippet you just reference this variable by its name in comma separated key/value pairs:

@stash((item name,key1=value1,key2=value2,...))

This feature is not intended for replacing massive amounts of text/code although it might still work for that. Instead this is intended for replacing small parts of often used code snippets so you can use the same snippet in many places even if there are minor changes to it in each place.

Error logging
The second feature is error logging. Sometimes when you use @stash you might spell the name of an item erroneously, or you delete an item and forget to remove the tag. The result has then been a @stash((name)) tag that has not been converted so it has been visible on the published site. With this release this should no longer be possible if you just remember to check the errors after publishing.

This feature is not enabled by default so you have to go to the setup dialogue and the ”Global settings” and check ”Enable error logging”. The errors are reported in a list on a new tab on the main view called ”Errors”. Each error will have a date stamp and a description of the error which most of the times includes both the name of the item and on which page there was an error so it should be relatively easy to locate the tag that is not working.

If you have enabled error logging and you have seen a couple of errors when you were working but you have to shutdown RapidWeaver you can also enable ”Save errorstate”. That will force @stash to save all errors that have not been acknowledged and restore the state of the errorlist when you reopen your project.

If you have cleaned up some of the errors in the list you can tick the checkbox next to the date. That will acknowledge the error and it will be greyed out. If you are saving the errorstate these errors will not be saved.

Growl support
The third feature is Growl support. This is connected to the error logging and relies on the same error handling in @stash. But if you enable this feature in the setup dialogue (”Global settings” and ”Growl support”) each error will be reported through Growl so you will see a Growl notification for each error.

The appearance of these Growl notifications can be changed in Growls preference pane. Open it and under applications you will find ”@stash Growl helper” in the list of applications. There you can change the way these notifications appear.

Free update
Just like most of the times this is a free @stash update for registered users so go grab your copy now.

Tags: @stash | Growl | Plugins | RapidWeaver | Released | Update