Bug 124611

Summary: wrong upcoming event link in the news
Product: Documentation Reporter: Rodrigo OSORIO <rodrigo>
Component: Books & ArticlesAssignee: Murray Stokely <murray>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Rodrigo OSORIO 2008-06-15 13:30:10 UTC
In the FreeBSD events[1] registred in the website as "9th Libre Software Meeting", a yahoo upcoming event link was added, but it uses a wrong keyword.

The current link is : http://upcoming.yahoo.com/search?type=Events&q=9th%20Libre%20Software%20Meeting&Search=GO

But it must be: http://upcoming.yahoo.com/search/?type=Events&q=rmll&rt=1&loc=&Search=GO













[1] http://www.freebsd.org/events/#event:3
Comment 1 murray 2008-06-16 19:13:04 UTC
The upcoming links are automatically generated from the XML.  If the
events are added in a systematic way with the same title as they are
entered in events.xml this is not an issue.  In the future I think we
should just focus on having a script automatically add the events to
upcoming rather than making a manual fix for this one entry where the
upcoming title is different from the events.xml title.

           - Murray

On Sun, Jun 15, 2008 at 5:25 AM, Rodrigo OSORIO <rodrigo@bebik.net> wrote:
>
>>Number:         124611
>>Category:       www
>>Synopsis:       wrong upcoming event link in the news
>>Confidential:   no
>>Severity:       non-critical
>>Priority:       low
>>Responsible:    freebsd-www
>>State:          open
>>Quarter:
>>Keywords:
>>Date-Required:
>>Class:          sw-bug
>>Submitter-Id:   current-users
>>Arrival-Date:   Sun Jun 15 12:30:10 UTC 2008
>>Closed-Date:
>>Last-Modified:
>>Originator:     Rodrigo OSORIO
>>Release:
>>Organization:
> fug-fr
>>Environment:
>>Description:
> In the FreeBSD events[1] registred in the website as "9th Libre Software Meeting", a yahoo upcoming event link was added, but it uses a wrong keyword.
>
> The current link is : http://upcoming.yahoo.com/search?type=Events&q=9th%20Libre%20Software%20Meeting&Search=GO
>
> But it must be: http://upcoming.yahoo.com/search/?type=Events&q=rmll&rt=1&loc=&Search=GO
>
>
>
>
>
>
>
>
>
>
>
>
>
> [1] http://www.freebsd.org/events/#event:3
>>How-To-Repeat:
>
>>Fix:
>
>
>>Release-Note:
>>Audit-Trail:
>>Unformatted:
> _______________________________________________
> freebsd-www@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-www
> To unsubscribe, send any mail to "freebsd-www-unsubscribe@freebsd.org"
>
Comment 2 Murray Stokely freebsd_committer freebsd_triage 2008-06-16 19:21:43 UTC
Responsible Changed
From-To: freebsd-www->murray

Maybe we can add an optional <upcoming-searchterm> 
</upcomingsearchterm> tag for each event in events.xml, and when it 
exists, use that in the upcoming url. The default would just be to use 
the <title> as we do now.  This seems like a good compromise until the 
upcoming events are added automatically from events.xml.
Comment 3 dfilter service freebsd_committer freebsd_triage 2008-06-29 20:25:40 UTC
murray      2008-06-29 19:25:35 UTC

  FreeBSD doc repository

  Modified files:
    share/sgml           events.xml templates.events.xsl 
  Log:
  Add support for hardcoding the URL to the Y! upcoming page when the
  search result based on the name doesn't find the event.  Use this for
  OSCon and rmll.
  
  PR:       www/124611
  
  Revision  Changes    Path
  1.54      +3 -1      www/share/sgml/events.xml
  1.11      +8 -3      www/share/sgml/templates.events.xsl
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
Comment 4 Murray Stokely freebsd_committer freebsd_triage 2008-06-29 20:25:52 UTC
State Changed
From-To: open->closed

I have added support to hard-code the URL to upcoming events when the 
search based on the name doesn't find the right upcoming event.  I'ved 
used this to add correct links for rmll and the O'Reilly OSCon. 

Thanks for your submission.  The website will be updated with this fix 
within ~6 hours.