A template to show “editing in progress” articles

There is no way in SPIP’s private area to list all the articles on a site whose status is “editing in progress”. This template does it.

The problem

On a fairly large site with many authors and translators, “editing in progress” articles can begin to accumulate. The administrators can wonder whether they are mistakes, or if they have been forgotten (or lost!) by their authors, — or if they are indeed being worked on.

Now in SPIP’s private area you can see your own [1] “editing in progress articles”, but not those of other authors. There is, it is true, the page articles_tous.php3 [2], which (if you are an administrator) offers the option of viewing “editing in progress” articles. However there is a catch: the list displayed shows only original articles. If the articles in question are “translations” they will not be shown.

A solution

The stand-alone template contained in the zip file below does two things:

  • checks if the visitor is logged in to the private area of the site. If not, it asks them to log in.
  • displays a list of articles with the status “editing in progress” as a series of links. It also shows the article language and date when work on the article began.

Here’s a screenshot:

To use the template, simply place the two files prep.php3 and prep.html in the root directory of your site and call it directly from your browser, thus: http://mysite.net/prep.php3

Footnotes

[1i.e. those of which you are the author

[2Access through the leftmost button on the SPIP (1.8) toolbar: “The entire site”

Note: There are other ways of solving this problem. See, for example, this article and this newsgroup thread.

With the change made to the criterion (statut) in the CVS version on 19/05/2005 (see this message) it should now be possible to display these articles using ordinary Spip loops.

Discussion

No discussion

Add a comment

Avant de faire part d’un problème sur un plugin X, merci de lire ce qui suit :

  • Désactiver tous les plugins que vous ne voulez pas tester afin de vous assurer que le bug vient bien du plugin X. Cela vous évitera d’écrire sur le forum d’une contribution qui n’est finalement pas en cause.
  • Cherchez et notez les numéros de version de tout ce qui est en place au moment du test :
    • version de SPIP, en bas de la partie privée
    • version du plugin testé et des éventuels plugins nécessités
    • version de PHP (exec=info en partie privée)
    • version de MySQL / SQLite
  • Si votre problème concerne la partie publique de votre site, donnez une URL où le bug est visible, pour que les gens puissent voir par eux-mêmes.
  • En cas de page blanche, merci d’activer l’affichage des erreurs, et d’indiquer ensuite l’erreur qui apparaît.

Merci d’avance pour les personnes qui vous aideront !

Par ailleurs, n’oubliez pas que les contributeurs et contributrices ont une vie en dehors de SPIP.

Who are you?
[Log in]

To show your avatar with your message, register it first on gravatar.com (free et painless) and don’t forget to indicate your Email addresse here.

Enter your comment here

This form accepts SPIP shortcuts {{bold}} {italic} -*list [text->url] <quote> <code> and HTML code <q> <del> <ins>. To create paragraphs, just leave empty lines.

Add a document

Follow the comments: RSS 2.0 | Atom