Hi team,
I am facing this "headers have already been sent" error in an AJAX
call. I am not able to fix it. I need your hellp. Would be better if
someone could explain this issue.
2020-03-04 11:00:45,582 Trac[main] ERROR: [172.24.188.116] Internal Server
Error: , referrer
On Tue, Mar 3, 2020 at 3:10 PM Jeff McKenna wrote:
> Hi Ryan,
>
> I tried to explain here that what I found is that the latest release that
> supports all plugins is 1.2.5 from my testing. Indeed there are plugin
> issues with 1.4.1 which is my point, and why I recommend to others to go
> with
Hi Ryan,
I tried to explain here that what I found is that the latest release that
supports all plugins is 1.2.5 from my testing. Indeed there are plugin
issues with 1.4.1 which is my point, and why I recommend to others to go
with 1.2.5 (and save yourself 2 weeks of effort, spend that time on
On Tuesday, March 3, 2020 at 11:26:59 AM UTC-8, Iqbal Ahmad wrote:
>
> Hi,
>
> I have tried TracCrystalXTheme in Trac 1.4.1. But as soon as I enable
> them in the trac.ini, it throws the error as shown in the attached
> snap-shot.
>
> Any help is greatly appreciated. Thanks.
>
> Regards,
On Tuesday, March 3, 2020 at 11:09:38 AM UTC-8, Mr. Smith wrote:
>
> Here's our situation. We currently have a single Trac *0.12.3 *instance
> hosted by RepositoryHosting.com. We want to self-host, but it's a hassle to
> install old Trac versions.
>
> *What is the right way to get our data
Here's our situation. We currently have a single Trac *0.12.3 *instance
hosted by RepositoryHosting.com. We want to self-host, but it's a hassle to
install old Trac versions.
*What is the right way to get our data from 0.12.3 upgraded by or for a
Trac 1.4 installation?*
I just have no idea
Hi,
On Sat, Feb 29, 2020 at 2:19 AM Rakesh kumar wrote:
>
> HI,
>
> We have upgraded the OS from rhel 6.10 to 7.6.
>
> Not abe to start the trac, Its giving the error while starting the trac
>
> Traceback (most recent call last):
> File "/bin/tracd", line 5, in
^^
tracd is
On Tuesday, March 3, 2020 at 9:59:29 AM UTC-8, Jeff McKenna wrote:
>
> +1 for Ryan's recommendation for using Trac 1.2.5 now in production.
>
> I spent a few weeks of effort trying to upgrade my production Trac
> instances to 1.4.1 (and of course saw the many users reporting issues with
> that
+1 for Ryan's recommendation for using Trac 1.2.5 now in production.
I spent a few weeks of effort trying to upgrade my production Trac
instances to 1.4.1 (and of course saw the many users reporting issues with
that upgrade, and the response of 'see installation guide'), but in the end
I found