Category: Interaction (with the outside World)

phpBB is a popular open source forum software.
Sometimes, a forum is not enough.
So, the data must be migrated from phpBB to Tiki forums...

If you want to help:
Please post links to similar scripts.
ex.: phpbb to invision board, etc
If/when we do a script, we should do for all major forums.
---
__From kerrnel22 on 11/20/07:__

I have almost completed an integrated TikiWiki forum migration tool for 1.9.8.x and 1.10. Initial release will be to migrate only Tiki forums from one Tiki install to another. However, hooks are in place, and the intention is there, to work on extending the migration tool to importing of phpBB2 (or any other forum software) into Tiki. If you would like more information, email tiki.kerrnel@kerris.com. I expect a general release of the forum migration tool (for Tiki forums only) into cvs of both branches for beta testing by December 1/07. If all goes well, I'll have something released for phpBB2 migration prior to Dec 31.

Tutos uses this one:
http://php-pdb.sourceforge.net/

http://prdownloads.sourceforge.net/tutos/palm-1.2.20050306.zip?download

The use of an outside mail-list system is not unusual.

I'm using [http://feedblitz.com|FeedBlitz.com] to get newsletters to users.

It would be nice to have the FeedBlitz system integrated with the Tiki registration module.

Here is what their Knowledge base says about integrating this kind of requirement.

I would like to suggest an enhancement to TikiWiki 8 to integrate with MantisBT. Specifically the desired outcome would be:

(1) A single sign-on. If you are logged into to TW, you are logged into Mantis and visa versa;
(2) A unified view of user. If you are a registered user on the TW, then you are a user on Mantis and visa versa. Creating an account on TW also creates an account on Mantis.
(3) Either a center module to deliver Mantis content or a menu link to take you to the linked Mantis website.
(4) Users can create links between forum topics and Mantis bugs. Each forum topic links to zero or one Mantis Issue, and each Mantis Issue links to zero or more TW forum topics.
(5) Develop a TikiWiki syntax enhancement to enable users to easily reference Mantis bugs by Bug ID.

It's easy:
http://translate.google.com/translate_tools?hl=en

((SAML))

http://en.wikipedia.org/wiki/Security_Assertion_Markup_Language
http://simplesamlphp.org/

Please see: ((OpenMicroBlogging))

hcal was added to 1.10!

As this is an ongoing process, we'll use a wiki page to coordinate efforts. Please see: ((microformats)).

Please see: ((WebDAV))

NTLM is an authentication protocol which is widely used in Microsoft based network environments. By using it with HTTP you can use that method for single-sign-on (SSO) authentication within your web browser.
This means that without needing to enter additional username or passwords, you can be authenticated at the website you're visiting. This is quite convenient especially for company intranets. NTLM should work with all major browsers (Internet Explorer, Firefox and Opera).

Tiki has internal ((doc:search)). It is fully integrated, checks permissions, and works on shared server, etc.

However, in some contexts, better support for external search technologies would be useful.


Related:
http://framework.zend.com/manual/en/zend.search.lucene.html
http://www.sphinxsearch.com/
http://www.google.com/sitesearch/
http://lucene.apache.org/solr/
http://ir.dcs.gla.ac.uk/terrier/

[http://freshmeat.net/browse/1099/|bibliography management system] like www.bibwiki.com

http://refbase.sourceforge.net/

Could probably be done by a smart combination of ((doc:wiki)) & ((doc:trackers)) in a [http://profiles.tikiwiki.org|profile].

[http://en.wikipedia.org/wiki/Wikipedia:CITE|This guideline uses the terms "source", "reference", "citing", and "citation" interchangeably.]


Related:
[wish1825|Generate footnotes at the bottom of a wiki page] (a simpler version of the current wish)

Setting feature_tell_a_friend=n doesn't affect the "Email This Post" functionality for the blog, so visitors is always offered to mail the link for a post. Imho the admin should be able to choose if this is allowed or not.

Let's follow the progress on this:
http://intranetblog.blogware.com/blog/_archives/2008/9/25/3900479.html

See also: ((CMIS))

Let's follow the progress on this:
http://intranetblog.blogware.com/blog/_archives/2008/9/25/3900479.html

See also: ((CMIS))

We have: ((tw:PO convertor for TikiWiki))

Should we change the way we handle language.php?: ((Research about different i18n systems))

We'll coordinate at ((diso))

Please see:
http://www.google.com/webmasters/gadgets/

Please see:
http://developers.facebook.com/connect.php
http://www.sociable.es/en/facebook-connect/

http://en.wikipedia.org/wiki/Gravatar
http://en.gravatar.com/site/implement/images/smarty/


https://www.libravatar.org/

Tiki can read and display RSS feeds: good
Tiki can read, combine and display RSS feeds : great


The next step is to import the data into Tiki and treat it like a native article / event / whatever.

If the remote article / event / whatever is modified, the item should be re-imported (but not duplicated). Using the URL to identify the uniqueness. (Some systems many use titles in the URL and if the title changes, we'll end up with a duplicate)

Related:
*[tiki-view_tracker_item.php?itemId=496|RSS feeds on tiki calendar + calendar data sharing via RSS (remote calendars)]
* http://profiles.tikiwiki.org/Collaborative_Watch

No indent
: One indent
:: Two indents

Please see:
http://www.mediawiki.org/wiki/Help:Formatting

MediaWiki/Wikipedia has an interesting way of dealing with meta-data concerning a wiki page. [http://en.wikipedia.org/wiki/Help:Infobox|Infobox] is very flexible and is very suitable to an encyclopedia. It's easy to create new ones and they are very flexible to adapt to the topic. As soon as a bunch of pages have something in common, you can create one and it gives visitors and quick overview of what characteristics this entry has.

There are over a hundred of these templates:
http://en.wikipedia.org/wiki/Category:Infobox_templates

Here is a simple one:
http://en.wikipedia.org/wiki/Template:Infobox_Animal

Here is a more advanced one where special language codes, when parsed, are shown with a nice presentation:
http://en.wikipedia.org/wiki/Wikipedia:Babel

This is a great way to have ad-hoc, organically growing meta-data around wiki pages which share some sort of structured/comparative data.

In TikiWiki, we use ((doc:trackers)) for tabular data. We need to have an even tighter integration.

Goal: that the metadata be stored both in the wiki page and the trackers
That you can update in one or the other. This would permit us to make lists/tables with all the data from all the infoboxes, without duplicating the data. (not sure if/how to do this with MediaWiki)

We'd need a Wiki Page field-type in trackers. Say I have an "Animals" tracker with all the Meta-Data. One of the fields should be the name of the associated wiki page. And that wiki pages "knows" to get latest data from tracker (like we do now for ((doc:PluginTrackerList)) and ((doc:PluginTrackerItemField)).



{img src=images/code.png}%%% {CODE(caption="2008-06-22 on #mediawiki on freenode.net", wrap=1)}
[09:48] marclaporte: Say I have lots of data in various infoboxes, is it possible to make a report/list/table of all these infoboxes and have them link to the various wiki pages?
[09:48] Splarka: you can use Special:Whatlinkshere on each infobox
[09:48] Splarka: (sorta)
[09:49] marclaporte: tks, would you know of an example?
[09:51] Dantman|FS: SMW
[09:51] Dantman|FS: Doing that with data is basically the purpose of SMW
[09:52] Splarka: http://en.wikipedia.org/wiki/Special:Whatlinkshere/Template:Infobox_Aircraft
[09:52] marclaporte: There are some lists here: http://en.wikipedia.org/wiki/Comparison_of_wiki_software -> how to reuse that info in infoboxes on each page
[09:52] marclaporte: tks
[09:53] marclaporte: Splarka: : yes, that's what I am looking for
[10:05] marclaporte: Splarka: : So now I know where the template is used. What if I want to make a mega chart for all the planes from all the infoboxes?
[10:06] Splarka: well, that might be something more for the category system
[10:06] Splarka: (or ask Dan about SMW, unless he means Super Mario World)
[10:08] Dantman|FS: heh
[10:10] marclaporte: Dantman|FS: : What is SMW?
[10:10] Dantman|FS: Semantic MediaWiki
[10:10] Dantman|FS: http://semantic-mediawiki.com/
[10:11] Dantman|FS: It's an extension for MediaWiki
{CODE}

!!Other things to think about:
*When watching a wiki page, how to watch tracker(s) which are associated with that wiki page?
*In page editing of tracker data, have a quick & nice interface like the ((doc:dynamic variable)) feature

Related:
*[wish2102|Support some of the MediaWiki syntax that doesn't conflict with TikiWiki syntax]
*[wish1191|Wiki editing: Preview with diff, like Mediawiki]
*[wish1781|Support for the Wiki creole markup (syntax)]
*[wish1220|MediaWiki import script]

I found the other day a chat that looks like is no more on develpment and is used to chat over irc (nice way to chat) is named Eteria IRC and u can find it at sourceforge (http://eirc.sourceforge.net/)

Might this be usefull to change the chat (that in my opinion) that does not work right.

I post this cuz the few times i used the tiki's chat module gave me a few problems with cpu usage and db's saturation

Hope u find this usefull for new vers for the tiki's chat module.

When I first met Tikiwiki, I was looking for only a wiki program. The translating for page (multilingual) feature of Tikiwiki made me to choose it.

But I always wonder: does Tikiwiki really need to have so many features ?

We all know that multi-features software is more complicated for developers as well as users than single-feature software. For example, Tikiwiki has a forum built-in, do you think this forum is better than phpBB3 ? Tikiwiki also has an article feature, do you think this feature is better than Joomla! CMS ?

At present, I have a website built with Joomla, I want to add a new wiki section, but Joomla has no wiki component. In fact, I think we should combine these best softwares together, not re-create the wheel. Joomla doesn't need to build a new wiki component if we can integrate Tikiwiki with it. In fact, this integration only needs at least one function: synchronize the users so they can login in to Tikiwiki without register twice.

I should inform you that Joomla! will be the most popular CMS soon, so I hope the Tikiwiki team take some time to consider this integration suggestion.

Thanks.

http://fotonotes.net/
http://wikifarm.koumbit.net/wikigraphe
http://kryogenix.org/code/browser/annimg/annimg.html



A nice usage example:
http://flickr.com/photos/36381329@N00/2190723280/

There's a Gedcom viewer (for Genealogy researchers) that's called PhpGedView (www.phpgedview.net) that looks like a completely awesome online family tree viewer/updater. Looks really well done. There is already a module written for it for PhpNuke, and I think it would be pretty cool if a module was written to interface it with TikiWiki.

If we had this, we'd use it on http://dev.tikiwiki.org

The Trac Repository Browser:
http://trac.edgewall.org/wiki/TracBrowser

Let's coordinate here: ((Repository Browser)) and ((Code Review))

((doc:InterTiki)) permits to share login, preferences and groups between various Tiki sites.

We need the Sister Wiki too!
http://www.wikimatrix.org/wiki/feature:SisterWiki
Continue discussion here: ((Sister Wiki))

((doc:backlinks)) are very cool. But what about backlinks from other sites?

We could use list from:
http://doc.tiki.org/External+Wikis


Related:
[wish2086|Backlinks between trackers and wiki pages (and maybe forums)]
[wish1768|Tracker plugin to get title and make link to tracker item]

Button does not accept any separtators other than '_' in _text variable.

There are many reasons to create button with two or more words on it.

The plugin Exercise is a nice way to for students to get feedback on their learning. For an instructor or an admin it would be very useful to have a way of checking student's success. That way, the instructor could evaluate how easy the material is, or if certain students need extra help with something.

As far as I understand, right now exercise input data is not stored in the database so there is no way to track the exercise outcome. It would be great if a table could be added to the database where the this data could be stored and accessed.

Please see: ((tw:Viral Tiki))

XML files are cool for data interchange.

For example, you can create an xml file to feed a Flash animation. However, you still need to update that XML file via FTP. What if you could edit a wiki page (with permissions, history, etc) and have the Flash animation get the data from it as if it was xml?

Or maybe a button on a wiki page "save to .xml", which would save on the filesystem WikiPageName.xml? (where the Flash would know to look for it)

Related idea:
* {wish id=467}
* {wish id=3103}


Louis-Philippe Huberdeau --will look into-- used [http://www.yaml.org/|YAML] --to see if this could be useful-- and it is very useful for the ((Profile Manager))

I tried the mod blogroll with an example opml file from wikipedia, and the rss icons doesn't link to the expected mp3 but to the same url as the url of the browser in tiki (tiki-list_file_gallery.php?galleryId=1, tiki-admin_modules.php, ...)

This happened with this blogroll:
[http://static.userland.com/gems/radiodiscuss/playlist.opml]

The one I used for documentation. After fixing the problem, if so, please, check documentation page to see if it's correct (I didn't understand that much about the whole thing myself ...):
[http://doc.tikiwiki.org/Mod+blogroll]


Moreover, with this other opml file:
[http://www.scripting.com/feeds/top100.opml]

The rss icons point to xml files, but no text is shown between the number of the item and the rss icon. (error). See attached image to this tracker item.

That's what the mod descritpion says:
{CODE()}
author: mcfarland
last modification: 2006/12/22 01:49:26
by: mcfarland
features/phpcas/COPYRIGHT -> lib/phpcas/COPYRIGHT
features/phpcas/README -> lib/phpcas/README
features/phpcas/source/CAS/CAS.php -> lib/phpcas/source/CAS/CAS.php
features/phpcas/source/CAS/PGTStorage -> lib/phpcas/source/CAS/PGTStorage
features/phpcas/source/CAS/PGTStorage/pgt-db.php -> lib/phpcas/source/CAS/PGTStorage/pgt-db.php
features/phpcas/source/CAS/PGTStorage/pgt-file.php -> lib/phpcas/source/CAS/PGTStorage/pgt-file.php
features/phpcas/source/CAS/PGTStorage/pgt-main.php -> lib/phpcas/source/CAS/PGTStorage/pgt-main.php
features/phpcas/source/CAS/client.php -> lib/phpcas/source/CAS/client.php
features/phpcas/source/CAS/domxml-php4-php5.php -> lib/phpcas/source/CAS/domxml-php4-php5.php
features/phpcas/source/CAS/languages/english.php -> lib/phpcas/source/CAS/languages/english.php
features/phpcas/source/CAS/languages/french.php -> lib/phpcas/source/CAS/languages/french.php
features/phpcas/source/CAS/languages/greek.php -> lib/phpcas/source/CAS/languages/greek.php
features/phpcas/source/CAS/languages/languages.php -> lib/phpcas/source/CAS/languages/languages.php
{CODE}

And that's what it says to me when attempting to install it:
{CODE()}
Warning: mkdir(lib/phpcas/source/CAS/PGTStorage): File exists in c:\archivos de programa\easyphp1-8\www\branch-1-9\lib\mods\modslib.php on line 68

Warning: copy(mods/features/phpcas/source/CAS/PGTStorage/pgt-db.php): failed to open stream: No such file or directory in c:\archivos de programa\easyphp1-8\www\branch-1-9\lib\mods\modslib.php on line 375
features/phpcas/source/CAS/PGTStorage/pgt-db.php to lib/phpcas/source/CAS/PGTStorage/pgt-db.php impossible to copy
{CODE}

This should be discussed. Not decided if we want it.

This would be useful for the import from MediaWiki people because this is a setting in MediaWiki. Now, after import, users must go in each page and add maketoc.


This would be a site-wide setting (overrideable per workspace). Would need to have a way to turn off for a page (ex.: with a wiki syntax)

Please see:
http://www.wikimatrix.org/wiki/feature:nofollow
http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html

The Export feature is nice, but it would be nice to export/save wiki pages with html formatting intact. A way to edit offline then sync changes would be even better, but for now, I'd settle for a way to just view pages offline.

ML: You can ((doc:mail-in)) and ((doc:watch)) (mail-out), but no true sync

XML-RPC? IMAP?

http://www.socialtext.net/help-en/index.cgi?working_offline_with_unplugged

See: ((Offline))

Would be really nice to combine with an encrypted password manager for offline storage -> ((User Encryption))

Investigate:
http://openmicroblogging.org/

http://sourceforge.net/projects/orgapp/

See details here:
http://tikiwiki.org/OrgChartDev

Johan is working on an outlook connector for MyTiki <-> Outlook

Has anyone written a module to integrate PayPal's ecommerce capabilities into TikiWIki?

Should be done through a module and several plugins (ADD_TO_CART, SHOWCARTCONTENTS, CHECKOUT etc)...

Oh, on that one, I would love to have a plugin that invalidates the cache to make sure that inside a cached website there are pages that are always rendered fresh...


Related:
*[wish1808|Shopping Cart / ecommerce / online orders]
*((shopping cart))

The login settings page should be refactored to eliminate the presentation of unneeded configuration options.

We already are able to show articles, wiki page changes, etc on our calendar. So, how about showing RSS feeds on tiki-calendar.php? That would be a nice way to aggregate all the RSS feeds :-)

RSS feeds could be filtered much the same way as Group Calendars and Tools Calendars. A third column would be added with all available RSS feeds. Users could select via checkbox which RSS feeds they want. (By default none are selected)

Therefore, thanks to RSS in & out for calendars, several Tiki sites could federate calendar data via RSS.
http://tikiwiki.org/tiki-calendars_rss.php?ver=2

Later, we can add ical and hcalendar (http://www.microformats.org/wiki/hcalendar). But in the mean time, it's an easy & efficient solution for calendar sharing :-)

WebCalendar has a Remote Calendars feature to support hCalendar (for example)
http://webcalendar.cvs.sourceforge.net/webcalendar/webcalendar/edit_remotes_handler.php?revision=1.7&view=markup

Related:
[tiki-view_tracker_item.php?itemId=1607|Import/sync from RSS/ical and not just show]

Tiki has a basic feature to generate slides from wiki page data. This permits to prepare slides collaboratively and makes them highly available/searchable/accessible.
http://doc.tikiwiki.org/Slideshow+User

However, the feature is not very exciting.

1- I do not want to rely on an external service to distribute my
slides. I want to put on my TikiWiki-powered sites. And I want them to
be searchable & accessible. An export to Flash is not ideal.

2- I want something standards-based to make sure I can use when I am
not using my computer (like at FOSDEM). Sure, Regis did an amazing
presentation at the last TikiFest, made with Keynote. But now, how to
share, mix and re-use?

3- I want a way to collaborate (when preparing) & share slide
information in an easier fashion.
a) I have done dozens of presentations. The collaborative process
using desktop tools is very inefficient. I remember a long night in a
hotel room in Tunis where we where collaborating over Skype to
fine-tune a presentation.

4- As Dogfood, I think these slides could help to
A) Make nicer tutorials/documentation
B) Promotional material on info.tikiwiki.org

5- Finally, I want something much nicer than what we have now. The
quality/design/features of S5 reloaded has nothing to be shy about
compared to Desktop apps:
http://www.netzgesta.de/S5/reloaded/advantages.php?id=sunny_gfx

Some goodies I look forward to using:
A- A second browser window which shows me a timer and some notes.
B- A special syntax to handle handouts.

6- Some of the concepts (ex.: image resizing depending on current
browser size) could be useful for Tiki in general.


Here is a proof of concept of
Wiki page:
http://trim.rclaporte.com/svn/slides/tiki-index.php?page=tests5reloaded
Slides:
http://trim.rclaporte.com/svn/slides/tiki-slides.php?page=tests5reloaded



Investigate:
http://meyerweb.com/eric/tools/s5/
http://www.netzgesta.de/S5/
http://en.wikipedia.org/wiki/S5_%28file_format%29
http://icant.co.uk/domslides/

Ideal:
Long-term collaboration/integration of one of these, or a similar open source project

Perhaps with ((jQuery))?

Please see:
https://wiki.mozilla.org/Support/ScreencastsPRD

Also:
[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=screencast&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=|SUMO bugs with word screencast]


Related: ((WebDAV)) to ease management of files.

This would be very useful as we move documentation from tikiwiki.org to doc.tikiwiki.org, for example.

For data interchange with other systems too.

Like Ricks99's great work:
http://tikiwiki.org/tiki-view_blog_post.php?blogId=26&postId=302

current plugin (from mods)
http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/mods/trunk/wiki-plugins/submit/wiki-plugins/wikiplugin_submit.php?view=markup

Ex:
http://www.stumbleupon.com/tag/tikiwiki/

Please see:
http://www.addthis.com/

Here are some options
http://framework.zend.com/manual/en/zend.service.akismet.html
http://bad-behavior.ioerror.us/
http://antispam.typepad.com/
http://www.defensio.com/
http://mollom.com/

See: ((Spam Protection))

Please see:
http://www.wikimatrix.org/wiki/feature:CREOLE%20support
http://www.wikicreole.org/wiki/TikiWikiCMSGroupware

Related:
http://dev.tiki.org/Why+Wiki+Syntax+is+Important
http://dev.tiki.org/tiki-index.php?page=2007-07-18+IRC+MediaWiki+discussion&highlight=creole
http://tiki.org/RFCWiki


Related:
*[wish1531|Wiki markup for icons]
*[wish1805|Universal Wiki Edit Button]
*[wish2102|Support some of the MediaWiki syntax that doesn't conflict with TikiWiki syntax]
*[wish1843|Infoboxes like MediaWiki/Wikipedia, but making use of trackers to be future-proof]
*[wish1220|MediaWiki import script]

Please go to "Syntax Examples" here:
http://www.wikimatrix.org/compare/TikiWiki-CMS-Groupware+MediaWiki

Please also see:
http://meta.wikimedia.org/wiki/Help:Wikitext_examples

Some syntax could be supported as it doesn't really conflict with the existing.

__Basic formatting markup__
{img src=images/code.png}%%% {CODE()}
You can ''italicize text'' by putting 2 apostrophes on each side.

3 apostrophes will '''embolden the text'''.

5 apostrophes will '''embolden''' and ''italicize''
'''''the text'''''.
{CODE}


__Signature/timestamp__
{img src=images/code.png}%%% {CODE()} You should "sign" your comments
on talk pages:
- Three tildes gives your
signature: ~~~
- Four tildes give your
signature plus date/time: ~~~~
- Five tildes gives the
date/time alone: ~~~~~ {CODE}

__Section headings__
{img src=images/code.png}%%% {CODE()} == Section headings ==

''Headings'' organize your writing into
sections.
The ''Wiki'' <u>ab</u>
##software can automatically
generate a [[table of contents]] from them.

=== Subsection ===
Using more "equals" (=) signs creates a subsection.

==== A smaller subsection ====

Don't skip levels,
like from two to four equals signs.

Start with 2 equals signs not 1
because 1 creates H1 tags
which should be reserved for page title. {CODE}


However, links & images could be more problematic.

Related:
*[wish1531|Wiki markup for icons]
*[wish1191|Wiki editing: Preview with diff, like Mediawiki]
*[wish1843|Infoboxes like MediaWiki/Wikipedia, but making use of trackers to be future-proof]
*[wish1781|Support for the Wiki creole markup (syntax)]
*[wish1220|MediaWiki import script]

Maybe some of you will think of this as a "marketinhg" thing, but let's face it : for most users on the Web "wiki" is synonym with "MediaWiki-powered sites that look like wikipedia".

What I propose is to create the theme and tools to facilitate migration of mediawiki powered sites to tikiwiki the (very) easy way : fill a form during install that points to the Mediawiki database, and extract all the info to automagically populate the Tiki. I'm willing to participate, but I do not feel I have the required knowledge at this moment to be able to do something useful in the coding part : I know little to no PHP or MySQL stuff, I even wasn't able to install Tiki properly here (shame on me).

Currently, the remove_all_versions function, defined in tikilib.php, accepts page as a parameter. It would be ideal if the function could be modified, or a new function created, that accepts username as a parameter. This would be ideal in instances where, for instance, several hundred pages have been created by a given user. The pages could be removed en masse, rather than having to specify each page specifically.

When I am in Firefox, I should be able to add an RSS feed directly (one click instead of login, and copy & paste)

Goal: to add a way to represent relevant data in a timeline.

This will most probably be done by re-using an existing library and/or service.

Let's coordinate here: ((TimeLine))

It is impossible to activate various Functions...

In the Administration Menu under "Editing and Plugins" it is impossible to activate functions like "google analytics" and lots more... everytime I want to save I get a "permission denied"
{CODE()}Forbidden

You don't have permission to access /content/tiki-admin.php on this server.{CODE}

The Module is unusable right at the moment...

I did:
- disable the searchengine friendly urls
- did a complete reinstall
- applied chmod 755 over everything

Nothing did work...

Please see:
http://universaleditbutton.org/

Related:
*[wish1781|Support for the Wiki creole markup (syntax)]


In testing now on:
http://wiki-translation.com

Commit:
http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=rev&revision=13295

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

Our friends at [http://www.horde.org/imp/|IMP] offer a feature to view various file formats without having the viewer installed on your desktop.

Beyond viewing, we could want a way to import to a wiki page. Since this is a broad topic, we'll coordinate on ((Binary File Handling)).

Contributors