On 4/12/2011 2:17 PM, Matthew Caron wrote:
On 04/12/2011 05:44 AM, Hasibullah wrote:
# chmod 777 -r /usr/local/trac/mysite // i gave full permission
after doing this the problem was solved but .
This is fine for testing, but is a very bad idea for a permanent
solution. Set permissions correctly such that the apache user
(whatever user apache runs as) has rw permission to that directory -
NOT everyone.
It showed this error message and i don't know what to do, i upgraded
it but the trac server said "no need to upgrade"
error message
Trac Error
TracError: The Trac Environment needs to be upgraded.
Run "trac-admin /usr/local/trac/mysite upgrade"
If I understand you correctly, you are saying that trac is telling you
to run the above command, but when you do it says that there is no
need to upgrade, yet when you load trac it still says an upgrade is
needed?
If so, that is very strange.
This can eventually happen if trac-admin and the Trac web front-end are
not using the same Trac version (e.g. mixup of virtualenvs), although
from the description given by Hasibullah this doesn't seem to be the
case for him.
Looking at the Trac log (if activated at 'info' level, see
http://trac.edgewall.org/wiki/TracLogging) should give you a hint about
the problem, in particular if a plugin requires an upgrade but fails to
do so (look for "Trac database schema version is <...>", "Component
<...> requires environment upgrade" and "<...> upgrading..." lines).
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
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.
