On 27/01/2011 5:48 PM, Jennifer Hodgdon wrote:

Just to clarify, all of the API documentation for any Drupal release is contained in in-code comments, so if you download Drupal 4.6 (or get it from CVS), you will have all of the API documentation along with it. It looks like the 4.7 API is also gone from api.drupal.org.

I'm not familiar with the exact rationale behind removing the old documentation, but I previously found it handy to be able to go back to unsupported releases to learn about the history and the changes in current functions. While I can understand removing old releases to hammer in that they aren't supported, it would still be useful to have old release API documentation existing somewhere on *.drupal.org for historical and educational purposes. Perhaps we could have a static HTML version of the old APIs posted somewhere? --Andrew

One thing you could do would be to use an IDE (Eclipse, NetBeans, Komodo) that supports "mouse hovering" or autocomplete "balloon" documentation of functions, once it has digested a complete Drupal 4.7 site. Victor On Fri, Jan 28, 2011 at 5:03 AM, Buzai Andras <buzai.andras@gmail.com>wrote:

Yes, I second that. It would be nice to have a place on *.drupal.org. for the old API's.

Buzai

On Fri, Jan 28, 2011 at 6:17 AM, Andrew Berry <andrewberry@sentex.net> wrote:

...

On 27/01/2011 5:48 PM, Jennifer Hodgdon wrote:

...

Just to clarify, all of the API documentation for any Drupal release is contained in in-code comments, so if you download Drupal 4.6 (or get it

from

...

CVS), you will have all of the API documentation along with it.

It looks like the 4.7 API is also gone from api.drupal.org.

I'm not familiar with the exact rationale behind removing the old documentation, but I previously found it handy to be able to go back to unsupported releases to learn about the history and the changes in current functions. While I can understand removing old releases to hammer in that they aren't supported, it would still be useful to have old release API documentation existing somewhere on *.drupal.org for historical and educational purposes.

Perhaps we could have a static HTML version of the old APIs posted somewhere?

--Andrew

I could set up 4.7 and 4.6 on drupalcontrib.org if there is enough interest. -- psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/

On Fri, 2011-01-28 at 11:57 +0000, Richard Burford wrote:

I could set up 4.7 and 4.6 on drupalcontrib.org if there is enough interest.

We definitely need to have them somewhere. Thanks, Richard.

Richard, thanks for this excellent service (I never knew who was behind it) and for your responsiveness on this request. -Randy On Fri, Jan 28, 2011 at 7:22 AM, Richard Burford < lists@freestylesystems.co.uk> wrote:

Ok, I have added Drupal core and developer documentation from cvs.drupal..org for 4.6 and 4.7. There are 9317 queued jobs, so it could take a while to run. I'm running cron via drush now but the number isn't going down (actually, it's going up so there must be more to index). I commented out the break in job_queue_dequeue() so it runs as quickly as possible. I also added job_queue module to the API since it wasn't there already.

I'll leave it running, should be up by the end of the day.

-- psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/

-- Randy Fay Drupal Module and Site Development randy@randyfay.com +1 970.462.7450

The API is still not up-to-date yet. I have been fighting with max_execution_time and memory_limit problems with running 10000 jobs. It is down to almost 6000 now, I'll keep trying and it *should* be up soon. Sorry for the delay. -- psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/

The Contrib API is finally up to date with 4.6 and 4.7 branches now available for your referencing pleasure! Sorry it took so long to get up, job_queue module was really chugging through them (roughly 10000 jobs) and finally managed to get through. I had to increase the memory_limit and max_execution_time on the server, commented out the break in job_queue_cron and ran drush cron in a while true loop for it to even start to parse the files. I should probably just bypass cron altogether and create a function that I can call from drush php-eval when I need to update the index with so many jobs. -- psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/

Thank you Richard :) There is no need to apologize. You did us a great favor :) Best regards, Buzai On Thu, Feb 3, 2011 at 1:43 PM, Richard Burford <lists@freestylesystems.co.uk> wrote:

The Contrib API is finally up to date with 4.6 and 4.7 branches now available for your referencing pleasure!

Sorry it took so long to get up, job_queue module was really chugging through them (roughly 10000 jobs) and finally managed to get through. I had to increase the memory_limit and max_execution_time on the server, commented out the break in job_queue_cron and ran drush cron in a while true loop for it to even start to parse the files. I should probably just bypass cron altogether and create a function that I can call from drush php-eval when I need to update the index with so many jobs.

-- psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/

On 1/28/2011 12:03 AM, Buzai Andras wrote:

Yes, I second that. It would be nice to have a place on *.drupal.org. for the old API's.

The Drupal documentation team is moving towards not displaying documentation for unsupported versions of Drupal (especially versions as old as 4.x), aside from pages that tell how to upgrade your site to newer versions. The main reason for this decision is that these doc pages show up in internal d.o as well as Google searches, and tend to confuse people who don't realize they're looking at something that is far from current. That said, if you did want to have api.drupal.org display the doc for 4.x, the way to make that happen would be to file an issue (probably in the drupal.org webmasters project), rather than discussing it on this mailing list. Regards, Jennifer -- Jennifer Hodgdon * Poplar ProductivityWare www.poplarware.com Drupal web sites and custom Drupal modules