demoneye, right, I made a mistake there, should be SharedAccount\Data\mbookmark* rather than just SharedAccount\mbookmark*. Will be fixed in the next beta version.

From Templates.ini:
#
# SeaMonkey
#

[Template_SeaMonkey_Force]
Tmpl.Title=#4323,SeaMonkey
Tmpl.Class=WebBrowser
ForceProcess=firefox.exe

demoneye, your most recent comment has moved here:

http://www.sandboxie.com/phpbb/viewtopic.php?t=5169

Guest10 -- thanks, fixed!

hehe , start thinking where my post gone

10x tzuk u are the best!

and the3.35.19 fix that

10x tzuk

This application template works:


while this one does not, the files end up in the sandbox:


Same result on XP and Vista.

EDIT: above does NOT work on XP (tested again), same behavior on both OS's.

Right. Expandable variables (template variables or any other kind) are not expanded in the program name part (i.e. before the comma). Earlier today I suggested that this might work -- you may have seen it in the topic for application configuration ideas -- so it turns out that I was wrong.

Yes I did see that topic, which was why I tried it. Any plans to allow variables for the program name?

One more question...I noticed now that there is a [TemplateSettings] section in both Sandboxie.ini and Templates.ini (previously only in Sandboxie.ini). Is this on purpose? Does one take precedence over the other if identical template variables are found? The current beta has Tmpl.Firefox and Tmpl.RoboForm in both INI's with the same settings.

Although there have only been a few releases of Sandboxie with application configurations, the "old" way was putting template variables in Sandboxie.ini, and the "new" way has the default values in Templates.ini (like Tmpl.Firefox) and only the overrides/alternates (like Tmpl.Firefox.user) in Sandboxie.ini.

In other words, you can safely discard any duplicates you have in Sandboxie.ini.



I think it might be easily possible, but I have to check.

Can you briefly explain how the alternate folder locations work? I see the entry created in Sandboxie.ini, but I'm not sure how it's used. Thanks!

For a template variable %Tmpl.Whatever%, Sandboxie checks if your [TemplateSettings] section contains

Tmpl.Whatever.YourUserName=value

If that is not found, it checks for

Tmpl.Whatever=value

And if that is not found, it complains about missing variables and aborts the new process.

With the recent change that I described earlier, Sandboxie Control now only manages the Tmpl.Whatever.UserName variables in [TemplateSettings] in Sandboxie.ini. While the [TemplateSettings] in Templates.ini specifies the default/standard locations.

In regard to the above description of alternate folder location, if I understand correctly:
If templates.ini defines
[TemplateSettings]
Tmpl.Firefox=%AppData%\Mozilla\Firefox\Profiles\*

and sandboxie.ini defines
[TemplateSettings]
Tmpl.Firefox.user1=C:\Profiles\Firefox\Profile1

then if user1 is the one logged in: the %Tmpl.Firefox% variable will take on the value that's been assigned to Tmpl.Firefox.user1 in sandboxie.ini - but only for those places where %Tmpl.Firefox% is used in sandboxie.ini (and not in those templates that are defined in templates.ini).Doesn't this mean that if the user wants to use templates that are pre-defined in templates.ini, and yet use the alternate folder location that is specified in sandboxie.ini, that he would have to create "Local" templates in sandboxie.ini that duplicate those that are already defined in templates.ini?
In which case, the values of the variables used in the local templates would have the value that's defined by the alternate folder location setting in sandboxie.ini - instead of the default value, as defined in templates.ini.

Then instead of going to Applications/Web Browser, where the default templates with their default values will be listed, the user will have to go to Applications/Local in order to 'Add' these Local templates to his configuration file.

No, the [TemplateSettings] sections from both configuration files are merged into a single [TemplateSettings] section in memory, so it doesn't matter where the Tmpl.Whatever variable is defined.

For my "official" templates, I am now putting the default folder locations in Templates.ini, rather than have Sandboxie Control write them into Sandboxie.ini, which is what I initially did. This change in behavior is going to make it easier for me to create new templates without having to update Sandboxie Control with new template variables. So it has nothing to do with the mechanism of templates, it's just a convenience for me.

As for alternate locations (i.e. per-user template variables), those are still written in Sandboxie.ini, because Template.ini should not be modified.

For your own templates, you should put all your template variables in Sandboxie.ini, whether they are global or per user.

I hope that clarifies everything now.



Yes, that will be available in the next beta version.

And in response to a point raised by soccerfan . . .



That's also going to be in the next beta version.