Thread: Timeline on new techdocs?
Folks, Magnus tells me that the new techdocs is usable, but it's not live on the site. What's the timeline on enabling it? -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
> Folks, > > Magnus tells me that the new techdocs is usable, but it's not > live on the site. What's the timeline on enabling it? It *is* live. It's just that the old one hasn't been killed off yet. But if you go for technical documentation under docs, you will get the new one. //Magnus
On Sat, 15 Apr 2006, Magnus Hagander wrote: >> Folks, >> >> Magnus tells me that the new techdocs is usable, but it's not >> live on the site. What's the timeline on enabling it? > > It *is* live. It's just that the old one hasn't been killed off yet. But > if you go for technical documentation under docs, you will get the new > one. Should we put a Redirect onto techdocs.postgresql.org so that it goes to the right site? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
> >> Magnus tells me that the new techdocs is usable, but it's > not live on > >> the site. What's the timeline on enabling it? > > > > It *is* live. It's just that the old one hasn't been killed > off yet. > > But if you go for technical documentation under docs, you > will get the > > new one. > > Should we put a Redirect onto techdocs.postgresql.org so that > it goes to the right site? Eventually, but not until everything is migrated and things are properly verified. //Magnus
On Sat, 15 Apr 2006, Magnus Hagander wrote: >>>> Magnus tells me that the new techdocs is usable, but it's >> not live on >>>> the site. What's the timeline on enabling it? >>> >>> It *is* live. It's just that the old one hasn't been killed >> off yet. >>> But if you go for technical documentation under docs, you >> will get the >>> new one. >> >> Should we put a Redirect onto techdocs.postgresql.org so that >> it goes to the right site? > > Eventually, but not until everything is migrated and things are properly > verified. At the *very* least, those links that ppl are reporting as broken should be added to the apache config file and redirected to the new site ... it really doesn't look good as it is :( ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
On Saturday 15 April 2006 16:14, Marc G. Fournier wrote:
> On Sat, 15 Apr 2006, Magnus Hagander wrote:
> >>>> Magnus tells me that the new techdocs is usable, but it's
> >>
> >> not live on
> >>
> >>>> the site. What's the timeline on enabling it?
> >>>
> >>> It *is* live. It's just that the old one hasn't been killed
> >>
> >> off yet.
> >>
> >>> But if you go for technical documentation under docs, you
> >>
> >> will get the
> >>
> >>> new one.
> >>
> >> Should we put a Redirect onto techdocs.postgresql.org so that
> >> it goes to the right site?
> >
> > Eventually, but not until everything is migrated and things are properly
> > verified.
>
> At the *very* least, those links that ppl are reporting as broken should
> be added to the apache config file and redirected to the new site ... it
> really doesn't look good as it is :(
>
I think your misreading the emails. There not broken links, but warnings that
php is emitting out to the page. I suspect there has been a php.ini change
that is causing this, but havent really looked (spending time on other
things, including migrating content). I do intend to start redirecting back
to the main site, but there are some unresolved bugs I've hit so I have been
overly agressive about it.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
On Sat, 15 Apr 2006, Robert Treat wrote: > On Saturday 15 April 2006 16:14, Marc G. Fournier wrote: >> On Sat, 15 Apr 2006, Magnus Hagander wrote: >>>>>> Magnus tells me that the new techdocs is usable, but it's >>>> >>>> not live on >>>> >>>>>> the site. What's the timeline on enabling it? >>>>> >>>>> It *is* live. It's just that the old one hasn't been killed >>>> >>>> off yet. >>>> >>>>> But if you go for technical documentation under docs, you >>>> >>>> will get the >>>> >>>>> new one. >>>> >>>> Should we put a Redirect onto techdocs.postgresql.org so that >>>> it goes to the right site? >>> >>> Eventually, but not until everything is migrated and things are properly >>> verified. >> >> At the *very* least, those links that ppl are reporting as broken should >> be added to the apache config file and redirected to the new site ... it >> really doesn't look good as it is :( >> > > I think your misreading the emails. There not broken links, but warnings that > php is emitting out to the page. I suspect there has been a php.ini change > that is causing this, but havent really looked (spending time on other > things, including migrating content). I do intend to start redirecting back > to the main site, but there are some unresolved bugs I've hit so I have been > overly agressive about it. Ah, you are right, I did mis-read ... can you post me one of those URLs, and I can see if I can correct the PHP? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
On Saturday 15 April 2006 22:59, Marc G. Fournier wrote: > On Sat, 15 Apr 2006, Robert Treat wrote: > > On Saturday 15 April 2006 16:14, Marc G. Fournier wrote: > >> At the *very* least, those links that ppl are reporting as broken should > >> be added to the apache config file and redirected to the new site ... it > >> really doesn't look good as it is :( > > > > I think your misreading the emails. There not broken links, but warnings > > that php is emitting out to the page. I suspect there has been a php.ini > > change that is causing this, but havent really looked (spending time on > > other things, including migrating content). I do intend to start > > redirecting back to the main site, but there are some unresolved bugs > > I've hit so I have been overly agressive about it. > > Ah, you are right, I did mis-read ... can you post me one of those URLs, > and I can see if I can correct the PHP? > http://techdocs.postgresql.org/redir.php?link=http://dancameron.org/pages/how-to-install-and-setup-postgresql-for-fedoralinux/ i'd start with looking up display_errors in the php.ini -- Robert Treat Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
fixed ... changed the code so that if HTTP_REFERER isn't set (ie. you come in directly and not through techdocs itself), it does the same as apache logs woudl do it, and sets it to "-" ... the second error was: $UserID = pg_result($dbresult, 0, userid); Instead of: $UserID = pg_result($dbresult, 0, "userid"); the first is read as a constant value, the second a field place within the result set ... Let me know if you see other stuff ... On Sun, 16 Apr 2006, Robert Treat wrote: > On Saturday 15 April 2006 22:59, Marc G. Fournier wrote: >> On Sat, 15 Apr 2006, Robert Treat wrote: >>> On Saturday 15 April 2006 16:14, Marc G. Fournier wrote: >>>> At the *very* least, those links that ppl are reporting as broken should >>>> be added to the apache config file and redirected to the new site ... it >>>> really doesn't look good as it is :( >>> >>> I think your misreading the emails. There not broken links, but warnings >>> that php is emitting out to the page. I suspect there has been a php.ini >>> change that is causing this, but havent really looked (spending time on >>> other things, including migrating content). I do intend to start >>> redirecting back to the main site, but there are some unresolved bugs >>> I've hit so I have been overly agressive about it. >> >> Ah, you are right, I did mis-read ... can you post me one of those URLs, >> and I can see if I can correct the PHP? >> > http://techdocs.postgresql.org/redir.php?link=http://dancameron.org/pages/how-to-install-and-setup-postgresql-for-fedoralinux/ > > i'd start with looking up display_errors in the php.ini > > -- > Robert Treat > Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
On Sat, Apr 15, 2006 at 10:55:02PM -0400, Robert Treat wrote: > I think your misreading the emails. There not broken links, but warnings that > php is emitting out to the page. I suspect there has been a php.ini change > that is causing this, but havent really looked (spending time on other > things, including migrating content). I do intend to start redirecting back > to the main site, but there are some unresolved bugs I've hit so I have been > overly agressive about it. <hindsight type='20/20'> If the migration was announced on both sites the errors would at least be more understandable to users... -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461