Category: Newsletters

__Update:__ there is http://doc.tiki.org/Newsletter+Admin#Styling_an_HTML_Newsletter so this is invalid bug report (maybe pointing that out in Admin interface could help ?)

In 12.x LTS when we send a Newsletter the email message gets "clipped" for GMail users which is annoying for promotion of the News we want to distribute because the email size is more than 128KB (which is the limit to display the message intact in GMail) even with almost no text content in the message. Many users use GMail nowadays so it is no help that it displays just fine in other email clients. Other newsletters of rival (competition) systems have emails far under 100KB. Tiki seems to include all the stylesheets even when less than 10% of the styles are actually used in the Newsletter.

Example of what it shows in GMail instead of the Newsletter email:
~np~[Message clipped] View entire message~/np~

Expected behavior: use only stylesheets related to Newsletters or make an option to omit inclusion of all the stylesheets via an Admin panel or while editing the Newsletter so the message is not unnecessarily large in KB and does not get clipped in GMail.

importing users & tracker items from .CSV is possible, so why not for newsletters :-)

The goal of having a newsletter system with group & permissions is that many different people may send newsletters.

Until 1.9.2, the "from" email was always the system email. In 1.9.3, the "from" email was corrected to be the user actually sending the newsletter.

We could have general options, overrideable on a newsletter-per-newsletter basis.

A- System default email
B- Email of person sending the email (so this person gets the replies)
C- Use a specific email (part of newsletter settings)

Newsletters (in Firefox and Chrome) do not show the list of emails being sent to, that page where the list got updated as emails where being sent.

In Chrome they are shown as usual (as in 12.x)

Using Firefox 46 on GNU/Linux 64 bit (Ubuntu 16.04).

Got it while testing this issue:
"Newsletter fails to be sent properly if article clipping is involved"
https://dev.tiki.org/item6040

Throtlling was in use, in case this matters.
Reproduced in tiki.org
https://tiki.org/tiki-send_newsletters.php?nlId=7
---
Update: using 16.x in t.o sites, and Chromium: I can't see the list of emails being sent either. (and unclear if all people receive the newsletter, but that is another story - even if that makes uncertain whether we are communicating properly security releases to all t.o-news-and-releases-newsletters subscribers ) {sign user="xavidp" datetime="2016-12-27T18:44:32+00:00"}

To send a newsletter you could use a previously "Sent Edition" and edit it. (it used to work in Tiki9 and T10 for sure).

Actually you still can, the newsletter preview will show you the edited newsletter with changes properly. BUT it is still the previous newsletter that will be sent has none of you changes was saved.

The feature may be not THAT important but the consequences are (imagine some of us have thousands of newsletter subscribers) so i categorise it as very important.

To reproduce on the instance:
Enter as admin (12345)
Go to Newsletter -> Subscriptions -> Add your email
Go to -> Send Newsletter
Click on tab "Sent Editions"
Click on the Subject on the last one
Edit anything you want -> send the modified edition of the newsletter.
Check your mailbox, you will see a the previous newsletter edition, not the new one with your editing.

{syntax type="tiki" editor="plain"}
In Tiki newsletters, it is possible to subscribe a group (excellent)
It is also possible for individuals to unsubscribe from a newsletter without leaving the group (excellent)

However, newsletter admins do not have access to this list. They should know who left the list and should be able to administer this "exception" list.

Usability bugs - not showstoppers but could use some polishing.

* no handling or warning if you subscribe a user without an email.
* No way to skip the confirm your subscription?
* Download the log file displays a blank page in the browser - temp/public/newsletter-log-2.txt
* adding a subscriber, selecting a user but checking "Add Email" crashes Tiki. (unhandled null)
* no way to filter or recognize anonymous spam bots

{syntax type="tiki" editor="plain"}
On the Admin Newsletter page, I create a new Newsletter.

Then from the page tiki-admin_newsletters.php#contentadmin_newsletters1-1 I click the action wrench for the newsletter: "Subscriptions".

There tiki-admin_newsletter_subscriptions.php?nlId=6 (this newsletter is id6) I go to the option; Import emails from tracker. I select the tracker where I want to grab emails. Click "Add".

It goes to a 500 and this is what I see in my php_error.log
It seems a bit inconsistent as it mention a tracker field from a different tracker I selected...

{CODE()}
thrown in /home/opensourcesolutions/public_html/lib/trackers/trackerlib.php on line 558
#2 {main}
#1 /home/opensourcesolutions/public_html/tiki-admin_newsletter_subscriptions.php(242): NlLib->get_emails_from_tracker()
#0 /home/opensourcesolutions/public_html/lib/newsletters/nllib.php(1365): TrackerLib->list_tracker_items()
Stack trace:
[01-Jan-2026 14:01:42 UTC] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/opensourcesolutions/public_html/lib/trackers/trackerlib.php:558
thrown in /home/opensourcesolutions/public_html/lib/trackers/trackerlib.php on line 558
#2 {main}
#1 /home/opensourcesolutions/public_html/tiki-admin_newsletter_subscriptions.php(242): NlLib->get_emails_from_tracker()
#0 /home/opensourcesolutions/public_html/lib/newsletters/nllib.php(1365): TrackerLib->list_tracker_items()
Stack trace:
[01-Jan-2026 14:01:29 UTC] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/opensourcesolutions/public_html/lib/trackers/trackerlib.php:558
[01-Jan-2026 13:53:23 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:53:23 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:53:23 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:53:23 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:53:23 UTC] PHP Warning: Undefined array key "key" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 26
[01-Jan-2026 13:53:23 UTC] PHP Warning: Undefined array key "itemkey" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 25
[01-Jan-2026 13:51:50 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:51:50 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:51:50 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:51:50 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:51:49 UTC] PHP Warning: Undefined array key "key" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 26
[01-Jan-2026 13:51:49 UTC] PHP Warning: Undefined array key "itemkey" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 25
[01-Jan-2026 13:50:48 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:50:48 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:50:48 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:50:48 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:50:48 UTC] PHP Warning: Undefined array key "key" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 26
[01-Jan-2026 13:50:48 UTC] PHP Warning: Undefined array key "itemkey" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 25
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:41:16 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:35:37 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:35:37 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:35:37 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:35:37 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:35:36 UTC] PHP Warning: Undefined array key "key" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 26
[01-Jan-2026 13:35:36 UTC] PHP Warning: Undefined array key "itemkey" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 25
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:20:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:05:39 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:05:26 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:05:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:05:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 13:05:26 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 13:05:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 13:05:26 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 12:46:50 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 12:46:43 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 12:46:43 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 12:46:43 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 12:40:48 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
[01-Jan-2026 12:40:48 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[01-Jan-2026 12:40:48 UTC] PHP Warning: Undefined array key "values" in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[01-Jan-2026 12:40:48 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 12:40:48 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 12:40:48 UTC] PHP Warning: Undefined array key "tracker_field_ossfaqTypeDeQuestion" in /home/opensourcesolutions/public_html/temp/templates_c/en_social^b1e897cce212dabee32b6e47fb255350ebd05a8a_0.file_homepage_testimonials_en.tpl.php on line 81
[01-Jan-2026 12:40:48 UTC] PHP Warning: Undefined array key 1 in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 52
{CODE}

When sending newsletters, Tiki sends as HTML. However, if the recipient does not accept HTML, the newsletter may become malformed for the recipient. For example, the EXTERNAL LINK text becomes merge with URL links.

I would like an option to send the newsletter as "plain text", thereby stripping out all HTML from the newsletter.

See here:

https://dev.tiki.org/Newsletter

__Personalised Newsletter__
* There are various options to fetch the eMail addresses as list of receipients of newsletters in Tiki, although one important is missing:
* There is no standard option to create personalised newsletters, either from a Tracker or from a CSV file.
* A very common and important feature for newsletters (despite Tiki doesn’t cover that) is the opportunity to send personalised newsletters with personal salutations like “Dear Mr. Doe”, “Dear Ms Smith”, “Dear Prof. Dr. Nevertheless”.
* If a newsletter could fetch a limited number of field from a Tracker by using permanent field names - optionally but not necessarily a user tracker - it would be quite easy to create a personalised newsletter.
* Additionally it could be considered to either implement an option to self-subscribe to the newsletter via the Tracker - with the problem to handle self-unsibscribe by an unsubscribe link in the sent newsletter or to add oneself to the tracker by the subscription link.

__This feature request was accidently submitted twice.__
__Please use only [item6469]__

See here:

https://dev.tiki.org/Newsletter#Roadmap

__Per user/group newsletter administration__ based on category permission or on object permission.
* It should (shall) be possible for specified groups to provide an own group-newsletter created by a superuser, which then could (shall) be administrated by one or more specified group members / group admins whilst the newsletter admin of one group cannot (shall not) administrate or alter the newsletter(s) of another group.
* This could be accomplished by adding to the code the opportunity to categorise newsletters and to add certain admin-permissions like tiki_p_batch_subscribe_email, tiki_p_send_newsletters, tiki_p_subscribe_email, tiki_p_subscribe_newsletters, tiki_p_view_newsletter, tiki_p_list_newsletters to the category permissions (not tiki_p_admin_newsletters)
* There should be a distinction between tiki_p_admin_newsletters which includes the permission to create a new newsletter and the now not (yet) existing tiki_p_admin_newsletter which would limit admin permissions to the specific newsletter.

See here:

https://dev.tiki.org/Newsletter#Roadmap

__Per user/group newsletter administration__ based on category permission or on object permission.
* It should (shall) be possible for specified groups to provide an own group-newsletter created by a superuser, which then could (shall) be administrated by one or more specified group members / group admins whilst the newsletter admin of one group cannot (shall not) administrate or alter the newsletter(s) of another group.
* This could be accomplished by adding to the code the opportunity to categorise newsletters and to add certain admin-permissions like tiki_p_batch_subscribe_email, tiki_p_send_newsletters, tiki_p_subscribe_email, tiki_p_subscribe_newsletters, tiki_p_view_newsletter, tiki_p_list_newsletters to the category permissions (not tiki_p_admin_newsletters)
* There should be a distinction between tiki_p_admin_newsletters which includes the permission to create a new newsletter and the now not (yet) existing tiki_p_admin_newsletter which would limit admin permissions to the specific newsletter.

Hi there everyone, newbie calling.

I work in a technical operations area. Currently developing the wiki as a wiki for operational staff across various areas but thought I would use some more of the functions that are available.

As an operations area there is a requirement for logs to be written daily by operation staff across different departments and to be e-mailed to management staff.

My idea is to give each department (5 in total) a separate blog. Only members of each department can write to their blog but any member of each department can read the other blogs. So far so good. By tagging each entry searches across blogs can identify faults across departments. This works perfectly and therefore preferable to a forum based solution as I need it to be as simple as possible for the operational staff.

However there is a requirement to print each log on a daily basis and ideally e-mail it to non-members (managers) possibily dependent upon tags. Obviously it is simple to print each separate entry but what I am looking for is a way of printing a 24 hour period of blog entries, or exporting them to a text file (word or e-mail body for example) to be distributed and printed. This is because there can be as many as 100 blog entries per day and it would be time consuming (and forest destroying) to print each one out individually.

Apologies if this is covered in a document that I have missed but I am still trying to absorb all the variables. I have also posted it in the forums to see if someone has any ideas with existing features or indeed using it in this way.

Any help would be greatly appreciated

Copied some suggestion I just throwed on irc..., after fighting each time on some of my production sites to manually send messages to many users which are kind of lost some times at the beggining of their participation in a tiki-site-powered community.

{QUOTE()}
(11:37:39) xavi: I was just wondering about a new and easy improvement of the registration process of new users to a community sit eusing tiki
(11:38:07) xavi: just through allowing an admin to add acustomized welcome message to new users successfully registered to the site...
(11:38:29) xavi: ... with the text and links he might need to tell to new users....
(11:38:52) xavi: ...in a similar way to what mailman does for the welcome message to new users...
(11:39:48) xavi: ...I imagine a simple text area, like site identity does, where the admin can write any simple text (with or without wiki markup? like the newsletter feature does/allows)...
(11:40:45) xavi: ...so that the admin can set that message easily (without manualy searching for the appropiate template to hack through ftp)...
(11:42:48) xavi: ..and the the new user, can review the infos and tips that he/she needs to know on that site: "now you can: # watch that forum where that important thing is discussed.... #join that newsletter/blog/articlefeature to be up to date about news from that community, #review and/or subscribe to that tracker..., ...
(11:45:22) xavi: oh well, I can't code php+mysql myself (yet, at least ;-) ), but I guess that this shouldn't be that difficult nor time consuming to an experienced coder, provided that that person agrees on that this feature is "low hanging fruit" to improve the experience of newcomers to a community, through improving the communication while the first steps of that person in the community site...
{QUOTE}

This could also be important for ((Workspaces)), and ((Organic Groups)). So that, not just to register (join the registered group), but as a customized message per group, so that, when joining a new group (at registration time, or later on through the subscribe groups plugin), you get the specific message with hints, links and remindings of things adapted for that group.

Feature working in 12.6

Case: Newsletter with 222 subscribers
Throttle: 6 every 120 seconds (=180/hour) to meet web host max of 200/hour

Sending shows this result:
---
__Sending Newsletter ...__
__... throttled sending to 222 addresses

Total emails sent: 1 after sending to 'wyncoghlan@bigpond.com':__
---
Admin Newsletter shows the Newsletter is still a draft i.e. not sent.

The subscriber email to myself does not receive a copy.

A second attempt to send produces exactly the same result.

For some reason, some subscribers to a newsletter got deleted when one of them validated the link to his subscription.
This happened twice to me ina production site.

I'll see if I can reproduce it in a show instance. more details will come once the issue is reproduced in the show.t.o instance.

---

Oh well, unable to reproduce in the show.t.o instance. Maybr language-specific, maybe conflict of prefs? Who knows, looks like too-edge case, so closing.

Please see:

"Put simply, I have a text box, and people commonly cut + paste
information into this text box from Microsoft word. The problem is that
word has all types of funky characters (smart quotes, em-dashes), that
the system (php-based) doesn't understand. Does anyone know of a way to
filter out these Microsoft-specific characters? Does PHP have a special
function for this? Thanks a lot!"
http://www.thescripts.com/forum/thread159156.html

I have problems with oe, and OE too. (used in French)

In Tiki, when the page is saved, it is OK for viewing & printing.
However, newsletters & email notifications (of articles & wiki pages)
are sent with a question mark instead of these characters.

Has anyone figured this out for Tiki? We'd need some sort of cleaning
code in the email class?

Currently, Tiki allows you to add users to a newsletter by name, email, or an entire group.

I would like to add users based on last login. For example, I want to send a newsletter to all users who have not logged in for 6+ months.

You can only see one page's worth of newsletters.

Workaround: tiki-admin.php?page=general

increase: "Maximum number of records in listings"

The following text in a newsletter results on "send newsletter" in:

501 Method Not Implemented
to /index.html not supported.
Invalid method in request

Oddly, when the message is split into part, each part will go through.

> > > Rick Labs wrote:
> > >> 2. I would like to get you introduced to
> Christian Schuhegger
> > over at the
> > >> OJTS. He is running a pure Java Project. While
> the guy is
> > brilliant I'm
> > >> not
> > >> positive he has much real world experience with
> investment system
> > >> backtesting and all the ways you can "torture"
> historical
> > investment data
> > >> to
> > >> "make it tell you what you want to hear".
> However, Christian is a VERY
> > >> quick
> > >> learner! I'll bet you would both benefit by the
> association.
> > >
> > > I am the founder of the OpenJavaTradingSystem
> project on sourceforge:
> > > http://ojts.sourceforge.net/
> > >
> > > As stated on the website of the project:
> > > "The project's aim is to provide a self
> contained pure Java (platform
> > > independent) common infrastructure for
> developers of trading systems."
> > > Which means that the aim is not to produce a
> finished end user
> > application
> > > but to factor out all the common and boring
> subparts that you need to
> > > write a trading system and to define "standard"
> interfaces for the
> > > subparts.
> > >
> > >>>robotrader or any part of it in those pages,
> please feel free to do so.
> > >
> > > I've just had a quick look at your robotrader
> project and I see for
> > > example that you have implemented fetching data
> over yahoo. The
> > gathering
> > > of data from "data providers" I would consider
> such a common and boring
> > > subpart of every trading system project.
> Therefore I would like
> > to see it
> > > implemented in a library (e.g. OJTS) with well
> defined
> > interfaces so that
> > > you can plug in other "data providers" easily.
> > >
> > > I would also like to point you to the
> humaitrader project:
> > > https://humaitrader.dev.java.net/
> > > which in my opinion looks very promising. I've
> contacted the author
> > > already but I habe the feeling he is not very
> interested in
> > sharing parts
> > > of his implementation.
> > >
> > > The sad thing in humaitrader aswell is that
> common functionality is
> > > implemented again and again!
> > >
> > > I would like OJTS to be in the trading system
> community something like
> > > OSKit is for the operating system researchers:
> > > http://www.cs.utah.edu/flux/oskit/
> > > "... the OSKit lets them concentrate on the real
> issues ... instead of
> > > spending six months or years groveling inside
> ugly code ..."
> > >
> > > For the beginning I would like to create common
> interfaces and
> > > implementations for the following parts:
> > > # the gathering of raw data over the internet
> > > # the recognition of trading signals /
> algorithms in general
> > > - here for example ta-lib could be plugged in
> > > # a visualisation module
> > > - why does everybody have to reinvent the
> visualisation? is
> > writing this
> > > part of the code so intellectually inspiring :)
> > > # plugging in scripting languages
> > > - beanshell
> > > - abcl lisp
> > > - sisc scheme
> > >
> > > Up to now I've worked alone on OJTS, but with
> Rick's talent to bring
> > > people together perhaps some of us could start
> OJTS (or at
> > least its idea)
> > > from scratch again. It would be nice to throw
> our collected experience
> > > into a bin and come up with a really good
> foundation library
> > for trading
> > > system.
> > >
> > > Have a nice week-end,
> > > --
> > > Christian Schuhegger
> > > http://www.el-chef.de/
> >
> >
> >

When using a tracker to collect emails, it's very important that there be no typo.

sorry - not actually a problem

Tiki newsletter works well for small volumes.

But for large volumes, as with any web app, sending emails from a server can be a challenge. Risk of being flagged as spammer, high server load/difficult to throttle, limits from your web hosts (ex.: max x emails per hour), etc

A helpful alternative would be something like this:
https://addons.mozilla.org/en-US/thunderbird/addon/4883

So my Thunderbird client or desktop newsletter application (ex.: [http://gammadyne.com/mmail.htm|Gammadybe Mailer]) should be able to access the TikiWiki database to generate recipient list.



---

Another approach is to make the Tiki contacts (address book) accessible via the LDAP protocol and thus, email clients can access.

Related:
http://www.egroupware.org/egroupware/index.php?menuaction=wiki.uiwiki.view&page=AddresbookAccountsConcept

This problem occurs if :
* the subscriptions to the newsletters are made with tiki groups (with tiki users)
* some groups are subscribed to more than one newsletters
* the users can unsubscribe with the links added at the bottom of each mail

==> if a user clics on the link added in a mail, he will be unsubscribed from all the newsletters

The Subscribe newsletter plugin output white area instead of a form.
Check the instance.

Newsletter, Wikiplugin Subscribe; form to subscribe is displayed ONLY if the user is anonymous