[Trac] Re: discussion plugin
Am 05.06.2008 um 15:28 schrieb Radek Bartoň: Did it work with 0.12dev? I didn't test it with this version yet. I just had the time to look into it again and since I have another environment which is working with 0.12 and genshi 0.55 and discussion plugin, I simply needed to look for the difference, which was wrong value for the Kollation in mysql. I had it set to utf8_general_ci and changing it to utf8_unicode_ci, like it is in the other environment seems to have solved the problem. so yes the answer is: it does work with 0.12 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] discussion plugin
Hi list,
I can't get the dicussion plugin to work with my trac install (0.12)
it seems to have problems with the latest genshi, which was installed
by the latest pygments release.
I get the following error:
Traceback (most recent call last):
File /usr/lib/python2.5/site-packages/Trac-0.12dev_r7181-py2.5.egg/
trac/web/api.py, line 344, in send_error
data, 'text/html')
File /usr/lib/python2.5/site-packages/Trac-0.12dev_r7181-py2.5.egg/
trac/web/chrome.py, line 741, in render_template
stream.render(method, doctype=doctype, out=buffer)
File build/bdist.linux-i686/egg/genshi/core.py, line 179, in render
return encode(generator, method=method, encoding=encoding, out=out)
File build/bdist.linux-i686/egg/genshi/output.py, line 61, in
encode
for chunk in iterator:
File build/bdist.linux-i686/egg/genshi/output.py, line 311, in
__call__
for kind, data, pos in stream:
File build/bdist.linux-i686/egg/genshi/output.py, line 748, in
__call__
for kind, data, pos in stream:
File build/bdist.linux-i686/egg/genshi/output.py, line 587, in
__call__
for kind, data, pos in stream:
File build/bdist.linux-i686/egg/genshi/output.py, line 702, in
__call__
text = mjoin(textbuf, escape_quotes=False)
File build/bdist.linux-i686/egg/genshi/core.py, line 462, in join
for item in seq]))
File build/bdist.linux-i686/egg/genshi/core.py, line 488, in escape
text = unicode(text).replace('', 'amp;') \
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position
904: ordinal not in range(128)
I am using mysql as database on a debian linux with python2.5. trac is
run via fcgid.
The discussion plugin used to work, before I messed up everything by
updating the debian system...
:-(
is that a genshi thingie?
my guess is that it is related to pygments having updated genshi.
wrong?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] trac authentication problem again...
Hi list, I recently dist-upgraded my debian and since then I can't log into trac anymore as registered user. I used to have it set up, so that my apache config has the trac location protected with basic authentication. but every time I log in, trac sees me as anonymous and not as the user, which logged in. I have cleared the passwords of the browser and I can confirm, that the location is password protected and I need to enter name and password, but still I can see in the trac log file, that the requests come from anonymous and I can only reach whatever I have set to be accessible for anonymous. Unfortunately I am not exactly sure, whether it is something, caused by trac update or the dist-upgrade of the debian system. The update of debian changed lots including the mysql version, but not the apache config, as I did skip that step. I needed to upgrade the trac environment as I got a database too new and in that go I also updated trac to the latest trunk (it already was 0.12 before, when it worked) does that sound familiar to anyone? it must be a very simple stupid thing which is wrong (hopefully) but I can't figure it out at the moment. been striggling with it the last two days... pls help ;-) TIA alex --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: trac authentication problem again...
Am 02.06.2008 um 11:25 schrieb Emmanuel Blot: does that sound familiar to anyone? Which authentication scheme do you use in your Apache config? If your Apache release has been upgraded from 2.0.x to 2.2.x you may have to edit your configuration file to match the new Apache authentication settings - I'm thinking about directives such as AuthBasicProvider for example. many thanks for taking the time, Manu. I use basic http authentication (or at least I am trying to do so, maybe my trac isn't properly recognizing that ?) in my apache site config I have: Location /trac AuthType Basic AuthName Trac AuthUserFile /var/tracpw/trac.htpasswd Require valid-user Options FollowSymLinks Order allow,deny Allow from all /Location it seems to work from the webserver side of things, as I can clear all my cached logins in the browser and it asks me for the username and password and allows me to proceed. However trac then only displays the content as if I was anonymous without the option to login btw, how can I display that login link at the top. It doesn't show up. on other trac environmets (on another server) it does and I can't figure out what is different, regarding login. I am not exactly sure from which apache version to which I updated, but it can very well be, that it was not 2.2 before. what do I need to change in that case. what do I need for AuthBasicProvider ? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: trac authentication problem again...
Am 02.06.2008 um 12:18 schrieb Emmanuel Blot: This is consistent with the expected behaviour: applying the authentication rules to the whole project (that is /trac instead of /trac/login, see above) forces authentication whatever the Trac page you're trying to browse. which is exactly what I want for this project and which used to work like a charme until the upgrade :-( If you do want to click on login first, use the documented path: Location /trac/login Ok, I am trying that now. thanks for the suggestion. what do I need to change in that case. what do I need for AuthBasicProvider ? I think that AuthBasicProvider can be omitted (default config) with htpasswd file authentication. Read the Apache 2.2 documentation for further details, from http://httpd.apache.org/... yes, the default is file and that is exactly what I am using. so it should work. it used to work until now. :-( thanks for the help --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] account manager plugin
Hi list, Does anybody happen to know, what would cause the following error? Traceback (most recent call last): File /usr/lib/python2.5/site-packages/Trac-0.11dev_r6853-py2.5.egg/ trac/web/api.py, line 339, in send_error 'text/html') File /usr/lib/python2.5/site-packages/Trac-0.11dev_r6853-py2.5.egg/ trac/web/chrome.py, line 684, in render_template data = self.populate_data(req, data) File /usr/lib/python2.5/site-packages/Trac-0.11dev_r6853-py2.5.egg/ trac/web/chrome.py, line 592, in populate_data d['chrome'].update(req.chrome) File /usr/lib/python2.5/site-packages/Trac-0.11dev_r6853-py2.5.egg/ trac/web/api.py, line 168, in __getattr__ value = self.callbacks[name] (self) File /usr/lib/python2.5/site-packages/Trac-0.11dev_r6853-py2.5.egg/ trac/web/chrome.py, line 460, in prepare_request for category, name, text in contributor.get_navigation_items(req): File build/bdist.linux-i686/egg/acct_mgr/web_ui.py, line 302, in get_navigation_items (req.href.register())) LookupError: unknown encoding: /trac/ILTable/register It only happens, once I install the account manager plugin. (with easy install) I have installed the latest trunk release of trac and python 2.5 running on a debian etch system. the latest trac + python 2.4, which I have on another, older, debian system works so far with the account manager plugin from trunk. what shall I try next? could it be easyinstall? any pointers? TIA --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: account manager plugin
Thanks a lot, Christian! I'll give it a try once I get back to my desk. and sorry for being so lame at finding these things on my own. :-( Am 22.04.2008 um 17:59 schrieb Christian Boos: http://trac-hacks.org/ticket/2907 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: account manager plugin
Am 22.04.2008 um 18:19 schrieb Christian Boos: It's a bit easier when you're the one who triggered the change ;-) as you might have guessed: it works like a champ! thanks again. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: MediaWikiPluginMacro
Am 04.03.2008 um 02:41 schrieb Michael Morrissey:
If it is, and I can then assume that it has been installed
correctly, why is that that the following MediaWiki syntax does not
get processed as I would expect:
[[mywikipage|pagename]]
You need to enclose the area you want to be processed by the mediawiki
macro with {{{ }}} so that the plugin knows which part to process.
{{{
#!mediawiki
[[mywikipage|pagename]]
}}}
you may want to use a pagetemplate with this directive already filled
in for pages you want to be processed in mediawiki style.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Re: highlight vs. pygments
Am 15.01.2008 um 12:25 schrieb Emmanuel Blot: I was asking for a starting point or get a hint, whether someone already did something like that. I have a few very long scripts, which take rather long to render. Ok. Have a look at trac/mimeview/enscript.py and trac/mimeview/ silvercity.py It should give you the entry points you're looking for to add highlight support for Trac. thanks, that helps. Doesn't look too complicated at the first glance. Too bad I haven't enough time on hands to start right away. :-( Anyway many thanks for taking the time to answer. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: 0.11dev: API change on trunk
Am 09.11.2007 um 16:17 schrieb Dana V. Baldwin: *cheers* Not much to add but kudos to everyone for the work that we all benefit from. A heart felt thank you from my dev team. Add my voice to the above statement! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: http://trac-hacks dead?
let's hope, the holidays are shorter this time ;-) Am 06.11.2007 um 14:31 schrieb Lars Stavholm: could it be that http://trac-hacks is dead? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: osx .5 leopard
Am 04.11.2007 um 11:47 schrieb Graham Dumpleton: Hmmm, very odd. I may have misinterpreted what I was told by person who got it working. They said: mod_wsgi was easier. I actually built it as a universal binary: CPPFLAGS = -Wc,-arch ppc -Wc,-arch i386 -Wc,-arch x86_64 -I/ System/Library/Frameworks/Python.framework/Versions/2.5/include/ python2.5 -DNDEBUG -DMACOSX -DENABLE_DTRACE CFLAGS = -Wc,-arch ppc -Wc,-arch i386 -Wc,-arch x86_64 LDFLAGS = -arch ppc -arch i386 -arch x86_64 -framework Python -u _PyMac_Error -framework Python Since the build line was: mod_wsgi.la : mod_wsgi.c $(APXS) -c $(CPPFLAGS) $(CFLAGS) mod_wsgi.c $(LDFLAGS) $ (LDLIBS) I saw the multiple listing of the options as redundant. What you may actually have to do is change CFLAGS as explained before, but also add '-arch ppc -arch ppc64 -arch i386 -arch x86_64' into LDFLAGS as well. Let me know if that works instead. Yay! you're a star! look at this now: file /usr/libexec/apache2/mod_wsgi.so /usr/libexec/apache2/mod_wsgi.so: Mach-O universal binary with 3 architectures /usr/libexec/apache2/mod_wsgi.so (for architecture ppc7400):Mach-O bundle ppc /usr/libexec/apache2/mod_wsgi.so (for architecture i386): Mach-O bundle i386 /usr/libexec/apache2/mod_wsgi.so (for architecture x86_64): Mach-O 64- bit bundle x86_64 beautyful! So only changing the CFLAGS, like suggested in the google article is not enough. Either CPPFLAGS or LDFLAGS must also be set (or both, which is what I tried to get the above result) Not, that it wouldn't make sense, but I am a totally noob (until now!) when it comes to compiling binaries. If it works out of the box, all is well, bit troubleshooting is another story. So I went on to compile mod_python with the same tweaks (CPPFLAGS + LDFLAGS + CFLAGS) and lo and behold: file /usr/libexec/apache2/mod_python.so /usr/libexec/apache2/mod_python.so: Mach-O universal binary with 3 architectures /usr/libexec/apache2/mod_python.so (for architecture ppc): Mach-O bundle ppc /usr/libexec/apache2/mod_python.so (for architecture i386): Mach-O bundle i386 /usr/libexec/apache2/mod_python.so (for architecture x86_64): Mach-O 64-bit bundle x86_64 !!! so just for the reference I'll post a steps to reproduce on my website and send a link here as soon as I made sure, that everything works. for now I only see, that it compiled for all platforms. I'll set up trac with mod_python now to check, whether it works. Thank you so much! The issue is that if you are using standard OS version of Apache 2.2 which is what I do. it is a full fat binary and if you have 64 bit CPU will run up as x86_64 and thus expect to have available x86_64 versions of all Apache modules and indirectly the Python framework, plus Python modules and libraries required by those modules. that's the reason it works for me: I am running it on a MBP, which is not a 64-bit architecture, is it? that may also be the reason for the trickery required to compile for 64-bit, is it? Python Framework on Leopard should be a full fat binary. See below example someone else sent me previously: [Macintosh:Library/Frameworks/Python.framework] benha% file Python Python: Mach-O universal binary with 4 architectures Python (for architecture ppc7400): Mach-O dynamically linked shared library ppc Python (for architecture ppc64): Mach-O 64-bit dynamically linked shared library ppc64 Python (for architecture i386): Mach-O dynamically linked shared library i386 Python (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 my python is the same, but my MBP may run the 32-bit version and therefore the mysql binaries for tiger work for me. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: osx .5 leopard
mod_python doesn't seem to work still. I get: apachectl configtest httpd: Syntax error on line 121 of /private/etc/apache2/httpd.conf: Can't locate API module structure `python_module' in file /usr/libexec/ apache2/mod_python.so: dlsym(0x100218cc0, python_module): symbol not found This is a new error, I'll investigate that further. mod_wsgi seems to work OK, but this time it refuses to use the mysql egg, because... you guessed it: wrong architecture. For now I revert to fastcgi, but I will investigate that further. thanks for all your help so far. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: osx .5 leopard
Am 04.11.2007 um 04:43 schrieb Graham Dumpleton: $: file /usr/libexec/apache2/mod_wsgi.so $: /usr/libexec/apache2/mod_wsgi.so: Mach-O bundle i386 For good measure, do a 'make distclean', rerun configure, and then only modify Makefile and rebuild/install, it should work. I acted on a fresh download, so I don't know, where make distclean would help. It should be obvious from the output of the build whether the options are being included with the compilation. all -arch options appear in the output for apxs and in the first output of libtool, the second libtool call doesn't have any -arch options. /usr/sbin/apxs -c -I/System/Library/Frameworks/Python.framework/ Versions/2.5/include/python2.5 -DNDEBUG -DMACOSX -DENABLE_DTRACE -Wc,- arch ppc -Wc,-arch ppc64 -Wc,-arch i386 -Wc,-arch x86_64 mod_wsgi.c -framework Python -u _PyMac_Error -framework Python -ldl /usr/share/apr-1/build-1/libtool --silent --mode=compile gcc- DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/usr/include/ apache2 -I/usr/include/apr-1 -I/usr/include/apr-1 -arch ppc -arch ppc64 -arch i386 -arch x86_64 -I/System/Library/Frameworks/ Python.framework/Versions/2.5/include/python2.5 -DNDEBUG -DMACOSX - DENABLE_DTRACE -c -o mod_wsgi.lo mod_wsgi.c touch mod_wsgi.slo /usr/share/apr-1/build-1/libtool --silent --mode=link gcc -o mod_wsgi.la -rpath /usr/libexec/apache2 -module -avoid-version mod_wsgi.lo -framework Python -u _PyMac_Error -framework Python -ldl Run file on .libs/mod_wsgi.so to work out what it was built for before installing. file .libs/mod_wsgi.so .libs/mod_wsgi.so: Mach-O bundle i386 :-( Another problem which has come up is MySQL. You can't use the precompiled MySQL distribution which is available as it was built on Tiger, which didn't produce x86_64 compatible binaries. I installed the precompiled tiger binaries of mysql (mysql-5.1.22-rc- osx10.4-i686) and it works so far on leopard. A little change was required in order to compile the mysql-python egg, but it seems to work so far. I thought, that python on leopard is 32 bit and therefore the 32 bit mysql-python egg and the 32 bit mysql distribution play happily together? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: osx .5 leopard
Am 02.11.2007 um 14:37 schrieb Emmanuel Blot: I understood most of the Trac requirements were already provided OOB on Leopard: http://www.cmlenz.net/blog/2007/10/python-on-leopa.html thanks for the link. interesting stuff. so far I am very pleased with leopard, as the underlying unix has gotten some attention this time. nonetheless I wasn't very lucky with the apache modules and it took me some time to get my msql server as I like it to be. do you really need mod_fcgi (vs. mod_python) ? no particular reason. I was used to fcgid from two linux boxes, but I wouldn't mind to run it with mod_python, but as I wrote, I hae the exact same problems with mod_python. will need to compile apache as 32 bit app? I thought there may just be an appropriate ./configure option when compiling mod_python...? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: help with autonav macro
Ok, to answer my own question, just for the record, the problem was, the old style name of the def: render_macro I changed it to: expand_macro which solved the problem with the formatter object. still the indentation of the downloaded file seems wrong on my end (using the download link, if I browse the source it seems to be correctly formatted) being a python noob, I was wrong earlier with the def link(page): function being wrong indented. indeed it works like it was before. only thing left is that the if statement at the beginning fails: if formatter.context.resource != 'wiki': it always is false as formatter.context.resource doesn't seem to be a string. commenting both lines out solved the problem in wiki pages, but still I think, they were put there for a good reason and might only get a little fix. can anybody help what the correct if test should look like ? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Creating Tables
Am 20.10.2007 um 08:14 schrieb ResumeWriter: I've been trying to figure out, for the last 4 hours, how to create complex tables in TracWiki. The TracWiki documentation is terrible for tables. I'm used to using MediaWiki, and I can do so much with tables with MediaWiki. you can just install the mediawiki plugin from trac-hacks on continue to use mediawiki formatting. (at least for tables) works like a charme. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Creating Tables
Am 20.10.2007 um 17:02 schrieb ResumeWriter: What's the name of the plugin? I did look at http:// trac.edgewall.org/wiki/PluginList, but nothing. Thanks to your suggestion, I learned about trac-hacks. But, I don't know the name of the plugin. I don't see anything called TablesPlugin. sorry, I thought it is called exactly as I wrote. mediawiki, but appearantly it isn't. it is. MediaWikiPluginMacro http://www.trac-hacks.org/wiki/MediaWikiPluginMacro --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: trac-hacks?
Am 25.09.2007 um 14:51 schrieb Manuzhai: Everyone is seeing this, and the admin has been notified. thanks for the info. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: syntax coloring in 0.11
Am 25.08.2007 um 09:18 schrieb a¿ex:
do in order that trac does not
treat .ls and .as files as plain text.
Somewhere I must tell trac to update the mime types.
I thought, that this information was read from the pygments
installation, but appaerently it isn't.
just for the record (if anyone ever googles for this info):
search for the file: trac/mimeview/api.py
and in that file you can add file extensions at:
...
...
# extend the above with simple (text/x-something: something)
mappings
for x in ['as', 'ada', 'asm', 'asp', 'awk', 'idl', 'inf', 'java',
'ksh', 'ls', 'lua',
'm4', 'mail', 'psp', 'rfc', 'rst', 'sql', 'tcl', 'tex',
'zsh']:
KNOWN_MIME_TYPES.setdefault('text/x-%s' % x, []).append(x)
...
...
in my case I added 'as' and 'ls' for actionscript and lingoscript files.
works like a charme now and i am a happy camper...
...for now at least :-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Re: Add image in TRAC wiki
Am 23.08.2007 um 10:11 schrieb Neena: Hello, I want to add image. How can i add image in wiki. I have done attached file and add image structure.jpg I would like to refer that image .I tried [img structure.JPG] It doesn't work try: [[Image(structure.jpg)]] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: wiki macros
I forgot to add a detail which puzzles me: the [[TracGuideToc]] works, although it is in the same directory like HelloWorld and TimeStamp, but it doesn't seem to be loaded from that place, since I changed some content and it doesn't get reflected. So it must be loaded from another place, which I can't find on my system. I guess once I know, where to make changes to [[TracGuideToc]] I will figure out how to get the others to work :-) -- Best regards Alex da Franca -- Multimedia Developer and Lingoist --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
