Changes between Version 2 and Version 3 of sottopagina

Oct 30, 2020, 5:45:38 PM (15 months ago)



  • sottopagina

    v2 v3  
    1 == sottopagina
    2 === Pisa Merda
     1= Trac FAQ
     3Here you can find answers to some frequently asked questions about Trac.
     5If you have a question not answered on this page, you can ask it on the MailingList or in the IrcChannel. See the TracSupport page for more options on getting support for Trac.
     7**Note:** If you don't find the answer you are looking for here and you are using Trac 0.12 or older versions, also have a look in the old [wiki:"0.12/TracFaq"].
     13== What is Trac and how can it help me?
     15There's a list on TracFeatures.
     18Maybe directly from [ Edgewall]. Sounds like we need a TracFeatures page. Just as a first cut at an outline:
     19 - Project description
     20 - open source
     21 - Integrated Wiki
     22 - Version control support (primary is Subversion, but now others)
     23 - Milestones and Roadmap
     24 - Ticketing
     25 - Reporting (custom and fixed complex ones)
     26 - Tight integration for cross links between different types of data
     27 - Extensible (see custom ticket fields, plugins, macros)
     30== Installation troubleshooting
     32=== Installation from source
     34==== Q: Why do I get `NameError: global name 'log' is not defined` when trying to use ``?
     37../trunk/$ python egg_info
     38running egg_info
     40  File "build/bdist.linux-x86_64/egg/setuptools/", line 55, in get_sections
     41NameError: global name 'log' is not defined
     44**A:** You're most likely working from a Subversion **1.7** checkout and you're using a too old `setuptools` package, eg `/setuptools-0.7a1dev_r66608`. Upgrade to a newer setuptools, downgrade to svn 1.6.x, or use distribute. See also #7598.
     46==== Q: Why does installing `distribute` fail with `ValueError: A 0.7-series setuptools cannot be installed with distribute.`?
     48You tried to install `distribute` as advised elsewhere:
     50$ curl | python
     53but you're greeted with:
     55ValueError: A 0.7-series setuptools cannot be installed with distribute. Found one at /packages/trac/virtualenv-0.13/lib/python2.7/site-packages/setuptools-0.7a1dev_r66608-py2.7.egg
     58**A:** Don't give up, it's just `setuptools` giving you a last fight. You can remove the offending setuptools .egg and if it keeps re-appearing, you have it installed not only in the virtualenv but also in the parent Python installation, the one in which you installed virtualenv itself. If this is the case, remove it from there as well and installing distribute should now work.
     60==== Q: Why does Apache crash (500) with a `ZipImportError` in the error log?
     63[Tue Aug 07 09:08:26 2012] [error] [client] mod_wsgi (pid=16444): Exception occurred processing WSGI script '/packages/trac/virtualenv-0.13/bin/trac.wsgi'., referer: http://dserver/trac/bct/timeline
     65[Tue Aug 07 09:08:26 2012] [error] [client]   File "build/bdist.linux-x86_64/egg/", line 1197, in _get, referer: xxx/trac/bct/timeline
     66[Tue Aug 07 09:08:26 2012] [error] [client] ZipImportError: bad local file header in /packages/trac/virtualenv-0.13/lib/python2.7/site-packages/Genshi-0.6-py2.7.egg, referer: xxx/trac/bct/timeline
     69**A:** You probably forgot to stop and restart your server during an upgrade. The zip importer mechanism keeps an internal cache which has trouble detecting replaced files, so a restart is needed, see TracUpgrade#ZipImportError.
     71==== Q: Why do ticket notification emails contain unexpected backslash characters?
     73You installed Trac from PyPI using `easy_install` or `pip`, along with Genshi 0.7. Your ticket notification emails have unexpected backslash characters (for an example, see #11572).
     75**A:** This is the result of a defect in Genshi 0.7 (genshi:#569). Until Genshi 0.7.1 is released, your options are:
     76 * Use Trac 1.0.3 or later. The zip archive has been built on Linux rather than Windows since 1.0.3.
     77 * Downgrade to Genshi 0.6.1
     78 * Convert the line endings of the ticket notification email template from `CRLF` to `LF`. For example, on a Unix-like system you can run the following from the directory in which the egg is installed:
     79 {{{#!sh
     80$ dos2unix Trac-1.0.1-py2.7.egg/trac/ticket/templates/ticket_notify_email.txt
     82 You may need elevated privileges, and your egg may have a different name depending on your Trac and Python versions.
     84==== Q: Why do I see `IndexError: pop from empty list` when trying to add an attachment?
     86The issue is seen with Genshi 0.6.1 and 0.7 for languages other than English. The issue can be avoided by downgrading to Genshi 0.6 or upgrading to Genshi 0.7.1.
     88=== Upgrade troubleshooting
     90==== Q: Trac /about says 1.0, but the style looks pre-1.0
     92**A:** You probably just need to convince your browser that the CSS files have changed. Try force reloading by entering `CTRL+R` or `CTRL+Shift+R`, depending on your browser. This is a common issue, see #10797.
     94If that still doesn't work, look in your server configuration to see where the chrome files are supposed to be served from (`Alias` or `AliasMatch` directive), and maybe you are serving them as static files from a different location:
     96Alias /trac/bct/chrome /packages/trac/virtualenv-0.13/share/htdocs
     99In this case, don't forget to:
     101$ trac-admin <yourenv> deploy /packages/trac/virtualenv-0.13/share
     104See TracUpgrade#a5.Refreshstaticresources.
     106==== Q: Attachments are missing after upgrade
     108**A:** Most likely failed. See #11370. Please report any additional information on the MailingList.
     110If the attachments are not moved when upgrading your Trac instance, add the following code to ``:
     112# -*- coding: utf-8 -*-
     114# Execute `do_upgrade` in trac/upgrades/
     116# Usage: python /path/to/tracenv
     119from __future__ import with_statement
     121from trac.env import Environment
     122from trac.upgrades import db28
     124def main(args):
     125    for arg in args:
     126        env = Environment(arg)
     127        with env.db_transaction as db:
     128            cursor = db.cursor()
     129            db28.do_upgrade(env, 28, cursor)
     131if __name__ == '__main__':
     132    import sys
     133    main(sys.argv[1:])
     136Then run the script against the broken environment:
     138$ python /path/to/tracenv
     141== Trac development
     143=== Q: How to extend Trac?
     145**A:** The primary way to extend Trac is to write [TracPlugins plugins] in Python. Look for the extensive documentation below TracDev/, maybe starting with the [TracDev#Overviews overview] pages. Also, we regularly migrate plugin functionality into Trac core, if that functionality is used often enough.
     147The community site [TracHacks:WikiStart] is the portal where close to 1000 Trac plugins are hosted, and there is a [ trac-hacks organization on GitHub]. It also contains a few [TracHacks:wiki:tutorial tutorials] to get you started.
     149=== Q: How to contribute to Trac?
     151**A:** There are many ways to contribute back, see HowToContribute for details.
     153Also have a look at the documentation below TracDev/, in particular the pages below the [TracDev#Contributing Contributing] section.