You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(103) |
Jul
(105) |
Aug
(16) |
Sep
(16) |
Oct
(78) |
Nov
(36) |
Dec
(58) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(100) |
Feb
(155) |
Mar
(84) |
Apr
(33) |
May
(22) |
Jun
(77) |
Jul
(36) |
Aug
(37) |
Sep
(183) |
Oct
(74) |
Nov
(235) |
Dec
(165) |
2002 |
Jan
(187) |
Feb
(183) |
Mar
(52) |
Apr
(10) |
May
(15) |
Jun
(19) |
Jul
(43) |
Aug
(90) |
Sep
(144) |
Oct
(144) |
Nov
(171) |
Dec
(78) |
2003 |
Jan
(113) |
Feb
(99) |
Mar
(80) |
Apr
(44) |
May
(35) |
Jun
(32) |
Jul
(34) |
Aug
(34) |
Sep
(30) |
Oct
(57) |
Nov
(97) |
Dec
(139) |
2004 |
Jan
(132) |
Feb
(223) |
Mar
(300) |
Apr
(221) |
May
(171) |
Jun
(286) |
Jul
(188) |
Aug
(107) |
Sep
(97) |
Oct
(106) |
Nov
(139) |
Dec
(125) |
2005 |
Jan
(200) |
Feb
(116) |
Mar
(68) |
Apr
(158) |
May
(70) |
Jun
(80) |
Jul
(55) |
Aug
(52) |
Sep
(92) |
Oct
(141) |
Nov
(86) |
Dec
(41) |
2006 |
Jan
(35) |
Feb
(62) |
Mar
(59) |
Apr
(52) |
May
(51) |
Jun
(61) |
Jul
(30) |
Aug
(36) |
Sep
(12) |
Oct
(4) |
Nov
(22) |
Dec
(34) |
2007 |
Jan
(49) |
Feb
(19) |
Mar
(37) |
Apr
(16) |
May
(9) |
Jun
(38) |
Jul
(17) |
Aug
(31) |
Sep
(16) |
Oct
(34) |
Nov
(4) |
Dec
(8) |
2008 |
Jan
(8) |
Feb
(16) |
Mar
(14) |
Apr
(6) |
May
(4) |
Jun
(5) |
Jul
(9) |
Aug
(36) |
Sep
(6) |
Oct
(3) |
Nov
(3) |
Dec
(3) |
2009 |
Jan
(14) |
Feb
(2) |
Mar
(7) |
Apr
(16) |
May
(2) |
Jun
(10) |
Jul
(1) |
Aug
(10) |
Sep
(11) |
Oct
(4) |
Nov
(2) |
Dec
|
2010 |
Jan
(1) |
Feb
|
Mar
(13) |
Apr
(11) |
May
(18) |
Jun
(44) |
Jul
(7) |
Aug
(2) |
Sep
(14) |
Oct
|
Nov
(6) |
Dec
|
2011 |
Jan
(2) |
Feb
(6) |
Mar
(3) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(11) |
Feb
(3) |
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(8) |
Dec
(1) |
2015 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2016 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
(11) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(3) |
2024 |
Jan
(7) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(3) |
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
From: Steve W. <sw...@pa...> - 2007-07-11 13:55:40
|
Hello Reini, et al: Has anyone approached you yet about the Go PHP 5 project yet? It's a grassroots campaign to get projects to drop support for PHP4. I loosely follow the Gallery project and it looks like they are about to join up (see below). ~swain Begin forwarded message: > From: Larry Garfield <la...@ga...> > Date: July 10, 2007 10:36:40 PM EDT > To: Bharat Mediratta <bh...@me...> > Cc: gal...@li... > Subject: Re: [Gallery-devel] The PHP 5 revolution > > Hi again, Bharat. It's not quite the list you had before, but does 30 > projects and 50+ web hosts count as "critical mass"? > > http://gophp5.org/projects > http://gophp5.org/hosts > > That's also not counting web hosts that offer PHP 5 as an option > but not the > default. > > I'm actually rather surprised myself at how much steam this has > picked up. I > don't know if you follow php-internals at all, but they're actively > discussing dropping PHP 4 support completely within the next year. > > Is this something Gallery could get behind at this point? > > On Sunday 01 July 2007, Bharat Mediratta wrote: >> Larry, >> >> How's this progressing? Andy pointed out that we should focus on the >> high profile php4-only projects like ezPublish. Serious hosts that >> offer php4 only today will offer both versions when the pressure >> is on, >> but it would help if there were less pressure to keep php4 around... >> >> -Bharat >> >> Bharat Mediratta wrote: >>> Larry Garfield wrote: >>>> Thanks, Bharat. I can understand your position, certainly. What >>>> would you consider "critical mass"? Shear number or some number of >>>> "big" projects (for some definition of big) or...? >>> >>> Good question :-) I think that we'd want to see the majority of the >>> best-of-breed applications in various different webapp categories >>> support this. >>> >>> Here are lists of apps that our affiliate web hosts support: >>> http://partners.powweb.com/powweb/autoInstalls.bml >>> http://wiki.dreamhost.com/One_Click_Installs >>> >>> And we'd want the top 3 hosts here to support PHP5 (I think that >>> they >>> already do, but it wouldn't hurt to get them on the list): >>> http://gallery.menalto.com/wiki/Web_Hosting_Referral_Page >>> >>> If you can get 50% of those apps on board, I think that would be >>> more >>> than enough. >>> >>>> As for advertising, I don't believe we're planning any sort of real >>>> advertising. This isn't a money-making venture by any >>>> means. :-) We >>>> plan to have a page/link for web hosts that offer 5.2 out of the >>>> box, >>>> just as we'll list projects that are targeting 5.2, as an added >>>> incentive for hosts to get on board; they get to appear >>>> "future-friendly". That's as close to advertising as we plan to >>>> get, >>>> though. >>> >>> Thanks. That's what I figured, but I wanted to make sure that we >>> were >>> clear :-) >>> >>> -Bharat >>> >>> >>> >>> -------------------------------------------------------------------- >>> ----- >>> This SF.net email is sponsored by DB2 Express >>> Download DB2 Express C - the FREE version of DB2 express and take >>> control of your XML. No limits. Just data. Click to get it now. >>> http://sourceforge.net/powerbar/db2/ >>> __[ g a l l e r y - d e v e l ]_________________________ >>> >>> [ list info/archive --> http://gallery.sf.net/lists.php ] >>> [ gallery info/FAQ/download --> http://gallery.sf.net ] > > > -- > Larry Garfield AIM: LOLG42 > la...@ga... ICQ: 6817012 > > "If nature has made any one thing less susceptible than all others of > exclusive property, it is the action of the thinking power called > an idea, > which an individual may exclusively possess as long as he keeps it to > himself; but the moment it is divulged, it forces itself into the > possession > of every one, and the receiver cannot dispossess himself of it." > -- Thomas > Jefferson > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] > |
From: Reini U. <ru...@x-...> - 2007-07-07 08:12:06
|
Another forward from the wikistandards list: Reini: This idea came from the Montreal 2007 RoCoCoMeeting in persona, where we discussed how to extend the interwiki map, to be able to use other features in other wiki's and wiki-engines, different from linking just to a page (interwiki), or using xmlrpc. We don't even know the xmlrpc interface for the other wiki. So we came up with a idea to publish for every wiki a wikiprofile, with a list of links to be used for some features other might be interested in. I heavily opted for <link rel="wiki.profile" type="application/rdf+xml" href="http://mywiki.com/wiki?action=profile"> and optionally n3 version: <link rel="wiki.profile" type="text/rdf+n3" href="http://mywiki.com/wiki?action=profile&format=n3"> docuwiki and mediawiki I believe export a dublin core metadata list. ============================================== Earle Martin: Thanks to everyone who attended Tuesday's IRC meeting (http://wikiohana.net/cgi-bin/wiki.pl/IrcMeetingJuly2007) - it was productive. For those who weren't there, I was inviting discussion on a project I've been working on called the Wiki Profile Vocabulary, which is essentially an RDF vocabulary for describing wikis and aspects of wikis. (The idea was originally suggested by Ward; thanks.) You can find the latest version at http://wikirdf.org/vocabulary/profile/ . There's also an article I wrote about what a "profile document" is and how to make one, at http://wikirdf.org/docs/creating-wiki-profiles.html . What I'm hoping that wiki authors will do is add support for producing these profile documents to their wiki engines, complete with autodiscovery tags in the <head> sections of their HTML pages, in order for robots and other mechanisms to find the information. In theory, it would be possible to write code to automatically generate sister site links from one wiki to another, just by entering the URI of the other wiki. Two main points were discussed: The current version of the spec has a naive expectation that wiki URIs are roughly of the form http://example.com/scriptname?args=whatever;page=[page name here]. However some wiki engines use URIs of the form http://example.com/scriptname/[page name here]/args. Chris Dent suggested using URI Templates (http://bitworking.org/projects/URI-Templates/) to define the form of URIs, and this was generally agreed to be a good idea. The other point was how to specify an autodiscovery method in page HTML that points to a wiki's profile document. Suggestions were (note, examples only; your engine's URI for producing a profile doesn't matter): A la Dublin Core (suggested by Reini Urban): <meta name="wiki.profile" type="application/rdf+xml" link="/wiki?action=profile"> A la FOAF (http://rdfweb.org/topic/Autodiscovery): <link rel="meta" type="application/rdf+xml" href="/wiki?action=profile"> Hybrid: <link rel="wiki.profile" type="application/rdf+xml" href="/wiki?action=profile"> Hybrid, n3 version: <link rel="wiki.profile" type="text/rdf+n3" href="/wiki?action=profile&format=n3"> Also, the possibility of having a "standard location" like robots.txt (http://www.robotstxt.org/) was mentioned, but was thought to be too inflexible. Out of all of these, I very much prefer the second, FOAF-style option, because the profile is very much an example of metadata, and I'm not too sure about how the "x.y" syntax works. On the other hand, reading through the W3C specs, it is apparently legal to have any QName (XML qualified name - see http://www.w3.org/TR/xmlschema-2/#QName) as the value of a "link rel", and a XML prefix can be used as long as it's been defined in an xmlns attribute (http://www.w3.org/TR/xhtml2/mod-metaAttributes.html#adef_metaAttributes_rel). So I guess it would be possible to do <link rel="rdfs:isDefinedBy" type="application/rdf+xml" href="/wiki?action=profile#Wiki"> ...but that seems a little over the top. <link rel=meta> is a well-known style and shouldn't cause any problems. Cheers, Earle. -- Earle Martin http://downlode.org/ http://purl.org/net/earlemartin/ _______________________________________________ wiki-standards mailing list. wik...@wi... http://www.wikisym.org/cgi-bin/mailman/listinfo/wiki-standards For the wiki-research, wiki-standards, wikisym-announce mailing lists, please see: http://www.wikisym.org/cgi-bin/mailman/listinfo -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://spacemovie.mur.at/ http://helsinki.at/ |
From: Reini U. <ru...@x-...> - 2007-07-07 07:46:49
|
A project we are working on in our monthly #wikiohana meetings, brought some results. See also http://wikiohana.net/cgi-bin/wiki.pl/IrcMeetingJuly2007 Forwarded from Brandon CS Sanders Hello Wiki-Standards Gang, There is a movement afoot to agree on an easily-recognizable universal "Edit This" button. We're using a consensus poll to coalesce consensus around the metaphor and version 0.1 implementation of the icon. So far 52 wiki people are participating. If you are not yet involved, please go to http://www.aboutus.org/ UniversalWikiEditButton and add yourself as a {{NotYet}} If you are participating, please take a look at the current version of the document and update your status accordingly. Big thanks to Ted Ernst, FridemarPache and the other volunteer facilitators. If you'd like to help with active listening and synthesis, we're organizing the facilitation effort at http:// www.aboutus.org/Projects:UniversalWikiEditButton Please invite folks who aren't yet participating to join the process. At the very least it's an interesting exercise in community written standards. See you on the poll! Brandon -- Reini |
From: Sabri L. <sab...@st...> - 2007-06-26 08:53:37
|
Reini Urban wrote: >2007/6/25, Sabri LABBENE <sab...@st...>: >> Hi all, >> It seems that the syntax highlighter plugin is disabled or >not installed. >> The following syntax: >> >> <?plugin SyntaxHighlighter syntax=c style=kr color=emacs #include >> <stdio.h> >> >> int main() { >> printf("Lalala\n"); >> } >> ?> >> >> Gives the following errors: >> >> Plugin SyntaxHighlighter failed. sh: line 1: highlight: command not >> found >> >> Plugin SyntaxHighlighter failed. Couldn't start commandline >'highlight --data-dir /usr/share/highlight --style emacs -c >/work1/codex/sabri/codex-3.0/592_wysiwyg_integration/usr/share/ codex/src/www/phpwiki-1.3.12p3/uploads/highlight-emacs.css -F kr -q >-X -f -S c' >> >> I want to have this plugin working. What do I need to do? > >Install highlight? > >Read lib/plugin/SyntaxHighlighter.php for the available >options, where to find the highlight executable. Ok I've got the plugin working and I was surprised that there is no difference between a preformatted text and the plugin result (no colors for langage key words for example even if I change color and style plugin parameters). Another question: What directory 'HIGHLIGHT_DATA_DIR' parameter should point to ? Thanks, -- Sabri. |
From: Reini U. <ru...@x-...> - 2007-06-25 17:10:04
|
2007/6/25, Sabri LABBENE <sab...@st...>: > Hi all, > It seems that the syntax highlighter plugin is disabled or not installed. > The following syntax: > > <?plugin SyntaxHighlighter syntax=c style=kr color=emacs > #include <stdio.h> > > int main() { > printf("Lalala\n"); > } > ?> > > Gives the following errors: > > Plugin SyntaxHighlighter failed. sh: line 1: highlight: command not found > > Plugin SyntaxHighlighter failed. Couldn't start commandline 'highlight --data-dir /usr/share/highlight --style emacs -c /work1/codex/sabri/codex-3.0/592_wysiwyg_integration/usr/share/codex/src/www/phpwiki-1.3.12p3/uploads/highlight-emacs.css -F kr -q -X -f -S c' > > I want to have this plugin working. What do I need to do? Install highlight? Read lib/plugin/SyntaxHighlighter.php for the available options, where to find the highlight executable. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://spacemovie.mur.at/ http://helsinki.at/ |
From: Sabri L. <sab...@st...> - 2007-06-25 08:47:19
|
Hi all, It seems that the syntax highlighter plugin is disabled or not = installed. The following syntax: <?plugin SyntaxHighlighter syntax=3Dc style=3Dkr color=3Demacs #include <stdio.h> int main() { printf("Lalala\n"); } ?>=20 Gives the following errors: Plugin SyntaxHighlighter failed. sh: line 1: highlight: command not = found Plugin SyntaxHighlighter failed. Couldn't start commandline 'highlight = --data-dir /usr/share/highlight --style emacs -c = /work1/codex/sabri/codex-3.0/592_wysiwyg_integration/usr/share/codex/src/= www/phpwiki-1.3.12p3/uploads/highlight-emacs.css -F kr -q -X -f -S c' I want to have this plugin working. What do I need to do? Thanks, -- Sabri. |
From: Reini U. <ru...@x-...> - 2007-06-24 13:07:39
|
Brian Herman schrieb: > I would like to make the stylesheets of phpwiki editable by the users > how would I do that? I haven't thought about that yet. It must be a special pagetype, and wrote by a new script from the database to the browser. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Brian H. <bri...@gm...> - 2007-06-24 12:40:57
|
I would like to make the stylesheets of phpwiki editable by the users how would I do that? |
From: Reini U. <ru...@x-...> - 2007-06-20 23:28:14
|
isonomia <bu...@ha...> schrieb: > Hi, > > I'm very keen to get a version of 1.3.13 up and going on my own web site. > > At the moment I'm only going to use it to put data into the database - it > won't be going public for a few months. > > Having heard it won't be out to January can I ask a few questions: > > 1. Are the tables in the latest build likely to change? user is deprecated and should not be used anymore. > 2. Have you created an option to allow prefixes to all tables including > pref, user and groups ( At least the three tables that didn't have a prefix > in 1.3.12!) This option existed forever, when we introduced these tables. You can always prefix your pref, user and groups table with the same string as the page tables, but since these tables are user customizable in the external auth settings you have to fix these there also. And the DATABASE_PREFIX is not applied automatically to these tables. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Reini U. <ru...@x-...> - 2007-06-20 00:00:19
|
Chris O'Halloran schrieb: > Replying again > > I can see in the webserver access logs > > ... "GET /phpwiki/images/tex/c0e78585c2add482621c0a58207171029.png > HTTP/1.1" 304 1593 "http://ohalloran.homeip.net/phpwiki/" "Mozilla/5.0 > (Windows; etc etc > > I was wondering if the 304 response was indicating somethings about the setup? 304 is just 304, not modified since. images/tex/c0e78585c2add482621c0a58207171029.png is treated as empty wikipage text/html, and not as image/png in your accesslog there must be "GET /phpwikidata/images/tex/c0e78585c2add482621c0a58207171029.png ..." otherwise you'll see no image Have you already tried the real and working latex plugin? TexToPng This requires PLUGIN_CACHED_CACHE_DIR to be configured, but this plugin should work with your non-simple setup. > On 16/06/07, Reini Urban <ru...@x-...> wrote: >> 2007/6/14, Chris O'Halloran <cm...@gm...>: >>> Hello, >>> >>> I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. >>> >>> I am trying to get the Tex2png plugin working. >>> >>> The first error I got related to the /images/tex directory not being writeable. >>> >>> I created the directory in /usr/share/phpwiki/ so that I now have >>> >>> /usr/share/phpwiki/images/tex >>> >>> I can now see the png files being created in this directory and the >>> error about not being writeable has gone away. >>> >>> However, whenever I use the wiki, the latex code is still displayed. >>> ie the alt description in the <img> tag. I can see the correct >>> reference for src="images/tex/12345abcde.png" but the images isn't >>> displayed. >>> >>> I've set the read write permissions to everyone >>> >>> And I've checked in the config.ini file and made sure png is included >>> in the inline images configuration. >>> >>> Is there something else I need to do to make it go? >> "/usr/share/phpwiki/images/tex" is the file location >> but the webserver must find it under "images/tex" >> so must set an alias for images. >> or better symlink from images to /usr/share/phpwiki/images/tex >> >> -- >> Reini Urban >> http://phpwiki.org/ http://murbreak.at/ >> http://spacemovie.mur.at/ http://helsinki.at/ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Phpwiki-talk mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://helsinki.at/ http://spacemovie.mur.at/ |
From: Reini U. <ru...@x-...> - 2007-06-19 09:27:58
|
No, the session already exists. Try to use DB_SESSION=false or use a current version of phpwiki. 2007/6/19, Chris O'Halloran <cm...@gm...>: > http://homepages.slingshot.co.nz/~cmoman/pics/phpwiki_screenshot.png > > The wiki uses mysql as the backend. > > In general it operates correctly but when I am logged in any creating > a saving changes, it present this error message at the bottom of the > page > > When I log out, there is not mention of the error again. > > I have set permissions to allow anonymous users and bogo users but > this hasn't changed the error message appearing at the bottom. > > Thoughts, comment appreciated. > > BTW using > I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://spacemovie.mur.at/ http://helsinki.at/ |
From: Chris O'H. <cm...@gm...> - 2007-06-19 03:41:09
|
http://homepages.slingshot.co.nz/~cmoman/pics/phpwiki_screenshot.png The wiki uses mysql as the backend. In general it operates correctly but when I am logged in any creating a saving changes, it present this error message at the bottom of the page When I log out, there is not mention of the error again. I have set permissions to allow anonymous users and bogo users but this hasn't changed the error message appearing at the bottom. Thoughts, comment appreciated. BTW using I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. Chris |
From: Chris O'H. <cm...@gm...> - 2007-06-19 03:34:44
|
Thanks for your help. I am not entirely sure what you mean but I will have a think about what you've said. Are you suggesting that I need to change some code in the Tex2png plugin? Chris On 18/06/07, Reini Urban <ru...@x-...> wrote: > 2007/6/18, Chris O'Halloran <cm...@gm...>: > > Replying again > > > > I can see in the webserver access logs > > > > ... "GET /phpwiki/images/tex/c0e78585c2add482621c0a58207171029.png > > HTTP/1.1" 304 1593 "http://ohalloran.homeip.net/phpwiki/" "Mozilla/5.0 > > (Windows; etc etc > > > > I was wondering if the 304 response was indicating somethings about the setup? > > your setup is clear. > /phpwiki/images resolves in your setup to /usr/share/phpwiki/index.php/images. > this will not work. > you have to change the source of the problem: the plugin, which wants > /phpwiki/images and not /phpwikidata/images. > > > > On 16/06/07, Reini Urban <ru...@x-...> wrote: > > > 2007/6/14, Chris O'Halloran <cm...@gm...>: > > > > Hello, > > > > > > > > I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. > > > > > > > > I am trying to get the Tex2png plugin working. > > > > > > > > The first error I got related to the /images/tex directory not being writeable. > > > > > > > > I created the directory in /usr/share/phpwiki/ so that I now have > > > > > > > > /usr/share/phpwiki/images/tex > > > > > > > > I can now see the png files being created in this directory and the > > > > error about not being writeable has gone away. > > > > > > > > However, whenever I use the wiki, the latex code is still displayed. > > > > ie the alt description in the <img> tag. I can see the correct > > > > reference for src="images/tex/12345abcde.png" but the images isn't > > > > displayed. > > > > > > > > I've set the read write permissions to everyone > > > > > > > > And I've checked in the config.ini file and made sure png is included > > > > in the inline images configuration. > > > > > > > > Is there something else I need to do to make it go? > > > > > > "/usr/share/phpwiki/images/tex" is the file location > > > but the webserver must find it under "images/tex" > > > so must set an alias for images. > > > or better symlink from images to /usr/share/phpwiki/images/tex > -- > Reini Urban > http://phpwiki.org/ http://murbreak.at/ > http://spacemovie.mur.at/ http://helsinki.at/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > |
From: Reini U. <ru...@x-...> - 2007-06-18 10:17:01
|
2007/6/18, Chris O'Halloran <cm...@gm...>: > Replying again > > I can see in the webserver access logs > > ... "GET /phpwiki/images/tex/c0e78585c2add482621c0a58207171029.png > HTTP/1.1" 304 1593 "http://ohalloran.homeip.net/phpwiki/" "Mozilla/5.0 > (Windows; etc etc > > I was wondering if the 304 response was indicating somethings about the setup? your setup is clear. /phpwiki/images resolves in your setup to /usr/share/phpwiki/index.php/images. this will not work. you have to change the source of the problem: the plugin, which wants /phpwiki/images and not /phpwikidata/images. > On 16/06/07, Reini Urban <ru...@x-...> wrote: > > 2007/6/14, Chris O'Halloran <cm...@gm...>: > > > Hello, > > > > > > I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. > > > > > > I am trying to get the Tex2png plugin working. > > > > > > The first error I got related to the /images/tex directory not being writeable. > > > > > > I created the directory in /usr/share/phpwiki/ so that I now have > > > > > > /usr/share/phpwiki/images/tex > > > > > > I can now see the png files being created in this directory and the > > > error about not being writeable has gone away. > > > > > > However, whenever I use the wiki, the latex code is still displayed. > > > ie the alt description in the <img> tag. I can see the correct > > > reference for src="images/tex/12345abcde.png" but the images isn't > > > displayed. > > > > > > I've set the read write permissions to everyone > > > > > > And I've checked in the config.ini file and made sure png is included > > > in the inline images configuration. > > > > > > Is there something else I need to do to make it go? > > > > "/usr/share/phpwiki/images/tex" is the file location > > but the webserver must find it under "images/tex" > > so must set an alias for images. > > or better symlink from images to /usr/share/phpwiki/images/tex -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://spacemovie.mur.at/ http://helsinki.at/ |
From: Chris O'H. <cm...@gm...> - 2007-06-18 04:19:56
|
Replying again I can see in the webserver access logs ... "GET /phpwiki/images/tex/c0e78585c2add482621c0a58207171029.png HTTP/1.1" 304 1593 "http://ohalloran.homeip.net/phpwiki/" "Mozilla/5.0 (Windows; etc etc I was wondering if the 304 response was indicating somethings about the setup? Thanks again. On 16/06/07, Reini Urban <ru...@x-...> wrote: > 2007/6/14, Chris O'Halloran <cm...@gm...>: > > Hello, > > > > I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. > > > > I am trying to get the Tex2png plugin working. > > > > The first error I got related to the /images/tex directory not being writeable. > > > > I created the directory in /usr/share/phpwiki/ so that I now have > > > > /usr/share/phpwiki/images/tex > > > > I can now see the png files being created in this directory and the > > error about not being writeable has gone away. > > > > However, whenever I use the wiki, the latex code is still displayed. > > ie the alt description in the <img> tag. I can see the correct > > reference for src="images/tex/12345abcde.png" but the images isn't > > displayed. > > > > I've set the read write permissions to everyone > > > > And I've checked in the config.ini file and made sure png is included > > in the inline images configuration. > > > > Is there something else I need to do to make it go? > > "/usr/share/phpwiki/images/tex" is the file location > but the webserver must find it under "images/tex" > so must set an alias for images. > or better symlink from images to /usr/share/phpwiki/images/tex > > -- > Reini Urban > http://phpwiki.org/ http://murbreak.at/ > http://spacemovie.mur.at/ http://helsinki.at/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > |
From: Chris O'H. <cm...@gm...> - 2007-06-17 21:55:56
|
Thanks for the reply. I might need a more explicit instruction here. In the apache.conf file in /etc/phpwiki there are the alias definitions. Alias /phpwikidata /usr/share/phpwiki/ Alias /phpwiki /usr/share/phpwiki/index.php/ As per your suggestion, I have tried adding the following lines. Alias /phpwiki/images/tex /usr/share/phpwiki/images/tex/ or Alias /images/tex /usr/share/phpwiki/images/tex/ or Alias /phpwiki/images/ /usr/share/phpwiki/images/tex or Alias /phpwiki/images/ /usr/share/phpwiki/ The remainder of the apache.conf file is <Directory /usr/share/phpwiki/> DirectoryIndex index.php Options +FollowSymLinks AllowOverride None etc The images are still not displaying. Any thoughts of comments appreciated. Chris On 16/06/07, Reini Urban <ru...@x-...> wrote: > 2007/6/14, Chris O'Halloran <cm...@gm...>: > > Hello, > > > > I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. > > > > I am trying to get the Tex2png plugin working. > > > > The first error I got related to the /images/tex directory not being writeable. > > > > I created the directory in /usr/share/phpwiki/ so that I now have > > > > /usr/share/phpwiki/images/tex > > > > I can now see the png files being created in this directory and the > > error about not being writeable has gone away. > > > > However, whenever I use the wiki, the latex code is still displayed. > > ie the alt description in the <img> tag. I can see the correct > > reference for src="images/tex/12345abcde.png" but the images isn't > > displayed. > > > > I've set the read write permissions to everyone > > > > And I've checked in the config.ini file and made sure png is included > > in the inline images configuration. > > > > Is there something else I need to do to make it go? > > "/usr/share/phpwiki/images/tex" is the file location > but the webserver must find it under "images/tex" > so must set an alias for images. > or better symlink from images to /usr/share/phpwiki/images/tex > > -- > Reini Urban > http://phpwiki.org/ http://murbreak.at/ > http://spacemovie.mur.at/ http://helsinki.at/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > |
From: Reini U. <ru...@x-...> - 2007-06-15 20:05:00
|
2007/6/14, Chris O'Halloran <cm...@gm...>: > Hello, > > I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. > > I am trying to get the Tex2png plugin working. > > The first error I got related to the /images/tex directory not being writeable. > > I created the directory in /usr/share/phpwiki/ so that I now have > > /usr/share/phpwiki/images/tex > > I can now see the png files being created in this directory and the > error about not being writeable has gone away. > > However, whenever I use the wiki, the latex code is still displayed. > ie the alt description in the <img> tag. I can see the correct > reference for src="images/tex/12345abcde.png" but the images isn't > displayed. > > I've set the read write permissions to everyone > > And I've checked in the config.ini file and made sure png is included > in the inline images configuration. > > Is there something else I need to do to make it go? "/usr/share/phpwiki/images/tex" is the file location but the webserver must find it under "images/tex" so must set an alias for images. or better symlink from images to /usr/share/phpwiki/images/tex -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://spacemovie.mur.at/ http://helsinki.at/ |
From: Manuel V. <man...@gm...> - 2007-06-15 12:34:53
|
On 6/15/07, Reini Urban <ru...@x-...> wrote: > 2007/6/15, Manuel Vacelet <man...@gm...>: > > On 6/14/07, Reini Urban <ru...@x-...> wrote: > > > 2007/6/14, Manuel Vacelet <man...@gm...>: > > > > I would like to know if there is a way to support phpwiki syntax in > > > > all the textarea of a website but without having to manage the > > > > textarea in wikipages. > > > > > > > > I was thinking about 2 ways: > > > > * use a 3rd party lib and hack it to support phpwiki syntax (like > > > > wikirenderer for instance). > > > > * hack phpwiki to only use the syntax parser (w/o plugins, save, > > > > templates, etc). > > > > > > I don't think that I complelety understand. > > > You mean completely dynamic, without any database persistency? > > > As in tiddlywiki edit just updates a <div>? > > > > No, actually we (with Sabri) integrated phpwiki in a bigger intranet > > website and we are currently thinking about offer to our users the > > possibility to include some kind of in all the text input on the > > website (forum, news, bug tracking, etc...). > > > > What I want to do is to allow users to use the phpwiki syntax for this > > purpose (to keep it coherent). > > I hope it's more clear. > > I see. That's very easy. > > require("BlockParser.php") > $html = TransformText ($text); > //(if you know the context for links, provide basepage also) > $xml = $html->asXML(); Unfortunatly it's not as easy due to the cascading of includes I already included prepend.php (rcs_id) config.php (clone) PageType.php (getInterwikiMap) BlockParser.php And I have to include main.php for getDdh too (I feel it becomes to be a bit heavy if I need to have a DB access). -- Manuel |
From: Reini U. <ru...@x-...> - 2007-06-15 10:59:54
|
2007/6/15, Manuel Vacelet <man...@gm...>: > On 6/14/07, Reini Urban <ru...@x-...> wrote: > > 2007/6/14, Manuel Vacelet <man...@gm...>: > > > I would like to know if there is a way to support phpwiki syntax in > > > all the textarea of a website but without having to manage the > > > textarea in wikipages. > > > > > > I was thinking about 2 ways: > > > * use a 3rd party lib and hack it to support phpwiki syntax (like > > > wikirenderer for instance). > > > * hack phpwiki to only use the syntax parser (w/o plugins, save, > > > templates, etc). > > > > I don't think that I complelety understand. > > You mean completely dynamic, without any database persistency? > > As in tiddlywiki edit just updates a <div>? > > No, actually we (with Sabri) integrated phpwiki in a bigger intranet > website and we are currently thinking about offer to our users the > possibility to include some kind of in all the text input on the > website (forum, news, bug tracking, etc...). > > What I want to do is to allow users to use the phpwiki syntax for this > purpose (to keep it coherent). > I hope it's more clear. I see. That's very easy. require("BlockParser.php") $html = TransformText ($text); //(if you know the context for links, provide basepage also) $xml = $html->asXML(); -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://spacemovie.mur.at/ http://helsinki.at/ |
From: Manuel V. <man...@gm...> - 2007-06-15 08:34:12
|
On 6/14/07, Reini Urban <ru...@x-...> wrote: > 2007/6/14, Manuel Vacelet <man...@gm...>: > > I would like to know if there is a way to support phpwiki syntax in > > all the textarea of a website but without having to manage the > > textarea in wikipages. > > > > I was thinking about 2 ways: > > * use a 3rd party lib and hack it to support phpwiki syntax (like > > wikirenderer for instance). > > * hack phpwiki to only use the syntax parser (w/o plugins, save, > > templates, etc). > > I don't think that I complelety understand. > You mean completely dynamic, without any database persistency? > As in tiddlywiki edit just updates a <div>? No, actually we (with Sabri) integrated phpwiki in a bigger intranet website and we are currently thinking about offer to our users the possibility to include some kind of in all the text input on the website (forum, news, bug tracking, etc...). What I want to do is to allow users to use the phpwiki syntax for this purpose (to keep it coherent). I hope it's more clear. -- Manuel |
From: Reini U. <ru...@x-...> - 2007-06-14 21:43:18
|
2007/6/14, Manuel Vacelet <man...@gm...>: > I would like to know if there is a way to support phpwiki syntax in > all the textarea of a website but without having to manage the > textarea in wikipages. > > I was thinking about 2 ways: > * use a 3rd party lib and hack it to support phpwiki syntax (like > wikirenderer for instance). > * hack phpwiki to only use the syntax parser (w/o plugins, save, > templates, etc). I don't think that I complelety understand. You mean completely dynamic, without any database persistency? As in tiddlywiki edit just updates a <div>? -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://spacemovie.mur.at/ http://helsinki.at/ |
From: Manuel V. <man...@gm...> - 2007-06-14 08:01:41
|
Hi all, I would like to know if there is a way to support phpwiki syntax in all the textarea of a website but without having to manage the textarea in wikipages. I was thinking about 2 ways: * use a 3rd party lib and hack it to support phpwiki syntax (like wikirenderer for instance). * hack phpwiki to only use the syntax parser (w/o plugins, save, templates, etc). Any advice ? -- Manuel |
From: Chris O'H. <cm...@gm...> - 2007-06-14 02:52:53
|
Hello, I am running phpwiki 1.3.11p1 on my Kubuntu Dapper machine. I am trying to get the Tex2png plugin working. The first error I got related to the /images/tex directory not being writeable. I created the directory in /usr/share/phpwiki/ so that I now have /usr/share/phpwiki/images/tex I can now see the png files being created in this directory and the error about not being writeable has gone away. However, whenever I use the wiki, the latex code is still displayed. ie the alt description in the <img> tag. I can see the correct reference for src="images/tex/12345abcde.png" but the images isn't displayed. I've set the read write permissions to everyone And I've checked in the config.ini file and made sure png is included in the inline images configuration. Is there something else I need to do to make it go? Thanks for your time and attention. Chris |
From: Don h. <sno...@ho...> - 2007-06-13 19:31:40
|
I am pretty new here. Can someone point me in the right direction to instal= l phpwiki to work with mysql? I have easyphp1.8 installed. When I unzippe= d phpwiki, and open the index.php page, the error says dba_open does not wo= rk. I am on xp. thanks very much if you can point out some documents or d= irections I can use.Don=0A= Send _________________________________________________________________ Hotmail to go? Get your Hotmail, news, sports and much more! Check out the = New MSN Mobile!=20 http://mobile.msn.com= |
From: Davide R. <da...@gm...> - 2007-06-13 11:50:46
|
First of all thank you for PhpWiki and pardon my poor english :D I installed PhpWiki CVS version on my home web server running Gentoo Linux, Apache2 and PostgreSQL 8. It can be visited at http://davide.no-ip.com (when my computer is switched on and connected to the internet, of course ). I have some problems when the text entries exceeds a certain number of characters. In this case the text is not shown or partially, but when i try to modify the entire message is still there. Is it a known problem or someone can help me? thank you :) Davide |