Trying to subscribe to a Newsletter, seeing the following error:
Warning: Smarty error: unable to read resource: "bitpackage:newsletters/newsletters.tpl" in /path/to/web/directory/bitweaver_r2/util/smarty/libs/Smarty.class.php on line 1095

There is no newsletters.tpl in either /newsletters nor /newsletters/templates

Any help?

Is there anybody out here? (quoting 'Pink Floyd: The Wall')

This is a serious problem for the site as it's a bar with concerts and stuff - so if there's no newsletter it's a problem

Try IRC or mailing lists if forum does not work.

Errrm... the reason of Support Forums are? To tell users to use IRC or mailing lists or to support them? You may remove the support forums then....

So I think this must be a bug - I can't get Newsletters to work properly in 2.0.2 or 2.10...

Any news on this subject. Sending of Newsletter-Editions still doesn't work in bitweaver 2.5 because of missing template.

Failure message:

string(17) "Missing template:"

array

force 	/..../themes/force/newsletters/newsletters.tpl

force_simple 	/..../themes/force/newsletters.tpl

override 	/..../themes/styles/cascader/newsletters/newsletters.tpl

override_simple 	/..../themes/styles/cascader/newsletters.tpl

package_template 	/..../newsletters/templates/newsletters.tpl

Warning: Smarty error: unable to read resource: "bitpackage:newsletters/newsletters.tpl" in /..../util/smarty/libs/Smarty.class.php on line 1092

.... - stands for the web path to bitweaver

Sorry to be the bearer of bad news but in the 12 months that I have been playing with BW, the said template hasn't materialised.

The newsletter package as I understand it, is Spiderr's baby.

I'm at the place again where I wish it would work too.

At present when I go to the tend mail queue /newsletters/admin/mail_queue.php I get this error too:



Sigh

This was fixed last week in CVS and will be part of the 2.6 release.

You should keep up with what is going on (watch CVS commits) and quit wasting your time writing stupid poems.

edit: PS You can thank /habile for getting this going. He registered a bug and kindly kept working with Devs to get the issue resolved.