2011/10/18 Yannick Torrès <yannick.tor...@gmail.com>:
> 2011/10/17 Christopher Jones <christopher.jo...@oracle.com>:
>>
>>
>> On 10/17/2011 01:03 PM, Hannes Magnusson wrote:
>>>
>>> On Mon, Oct 17, 2011 at 21:28, Christopher Jones
>>> <christopher.jo...@oracle.com>  wrote:
>>>>
>>>>
>>>> On 10/11/2011 05:00 AM, phpdoc@lists.php.net wrote:
>>>>>
>>>>> Hello PHP Documentation team,
>>>>>
>>>>> Below is a list of URL entities that are experiencing fatal errors:
>>>>>
>>>>> HTTP_NOT_FOUND
>>>>> -&url.xhprof.docs.facebook; :
>>>>> http://mirror.facebook.net/facebook/xhprof/doc.html
>>>>> -&url.pecl.package; : http://pecl.php.net/package/
>>>>> -&url.oracle.drcp.configure; :
>>>>>
>>>>> http://download.oracle.com/docs/cd/E11882_01/server.112/e17120/manproc004.htm
>>>>> -&url.jpeg; : http://pecl2.php.net/downloads/php-windows-builds/source/
>>>>>
>>>>>
>>>>>
>>>>
>>>> How is this list being generated?  I fixed the
>>>> &url.oracle.drcp.configure; URL entity after seeing it flagged in the
>>>> previous report. The URL in the above email works fine for me.
>>>
>>> It didn't work 6 days ago, I tested it too.
>>>
>>> There is a tool in docweb that runs through the entities and checks
>>> their status.
>>> Think this is the one:
>>>
>>> http://svn.php.net/viewvc/web/doc/trunk/scripts/checkent.php?revision=308163&view=markup
>>>
>>> -Hannes
>>
>> Thanks.  Let's see if it reoccurs next time the report is run or if it was a
>> glitch.
>>
>> Chris
>>
>> --
>> Email: christopher.jo...@oracle.com
>> Tel:  +1 650 506 8630
>> Blog:  http://blogs.oracle.com/opal/
>>
>
> This email is send by the online editor and the script used is a port
> of the once hannes spotted.
> You can view the ported version here :
>
> http://svn.php.net/viewvc/web/doc-editor/trunk/php/ToolsCheckEntities.php?view=markup
>
> Best,
> Yannick
>


Just forget : the script have just been run (by cron or Hannes ?).
You can view the current result directly into the online editor (Main
menu => EN Tools ) and your URL is no more into the failed result,

Best,
Yannick

Reply via email to