For now this is just a placeholder, and probably an announcement, for details and discussion on a rewrite of the Rep[lacement]Tags module.

Reptag was drafted in autumn 2005 and a first version was implemented shortly after (Feb 2006). However, in the last 3 years Drupal has evolved and now makes up an even more dynamic framework. We have CCK (and 'Fields in Core' for Drupal 7), Views, Panels and the competiting Token module. For that reason I started to rethink the internal design of the module about 2 months ago. The major design goals are (in no particular order) to make RepTag ...

  1. smaller and faster
  2. easier to interface/integrate (with cck, views, rules)
  3. compatible with Token (aka "move token.tags.inc into reptag core")

Due to heavy workload in my dayjob the redesign already takes much longer than I expected. However, I hope to commit a first version to CVS (6--2 branch) in May.

Comments

webel’s picture

webel commented

Today is 7 May 2009 (in Australia), I hope your wonderful hoped rewrite of this super hopeful module has taken place.

If I may place a major wish on your rewrite wishlist, I would like to be able to view all tags in the edit form without a pager, so that I can see all existing tags and definitions in one place ! Also, it would be nice to be able to generate a list/view of all occurrences (usages) of a given reptag. Keep up the $good$ work on $this$ great module.

laken’s picture

laken commented

This is great news, as I've said before this is a great, well-thought-out module that fills a real need.

My first wishlist item would be #462062: Reptag should be able to process non-node text easily

profix898’s picture

profix898 commented
Title: Rewrite of RepTag » Rewrite of RepTag for Drupal 7

After half a year of absence from this project, I'm back and working on a new version of reptag. The basic structure of the module stands and I'm currently trying to tie all pieces together. As some key components in Drupal 7 core changed , i.e. the revamped filter system, the field api, etc, I'm aiming at a new reptag module for Drupal 7.x compatibility now.

And yes, #462062: Reptag should be able to process non-node text easily is on my radar ;)

vizechef’s picture

vizechef commented
Component: Code / API » Miscellaneous
Category: task » feature
Priority: Normal » Minor

Hi Thilo,
perhaps you remember that we have been in contact in 2006 ?
I just want you to know that I have been using the RepTag-Module on all of my sites and still do.
Due to your long absence I was in sorrow that this module will not be maintained any longer, but I'm glad to read that you plan to realize a new D7 module version.
Keep on !! Your module is really useful !

webel’s picture

webel commented

I agree, this is a very important module, one which is responsible for a lot of served content on many sites. Please persist.

profix898’s picture

profix898 commented
Category: feature » task
Priority: Minor » Normal

@vizechef: Sure, I remember and I'm happy to read that you're still using reptag.

@all: I made significant progress on reptag for D7. Right now I'm playing with the new filter and token subsystems in core, trying to understand how to integrate best with the new options. I plan to commit the new code to CVS in the next weeks, but for now (until all basic API structures and features are restored) I'd prefer to keep it private. Stay tuned.

pillarsdotnet’s picture

pillarsdotnet commented

Also see Port flexifilter to Drupal7 which may overlap this functionality.

webel’s picture

webel commented
Issue tags: +6x upgrade to 7x

@ profix898

Just confirming my interest in a Drupal7 version of this.

As far as I am concerned, this is one of the most important, useful modules in Drupal.

It enables one to author more consistently, and opens up lots of possibilities not otherwise possible.

It is an expression of the crucial Don't Repeat Yourself (DRY) principle/pattern.

Token is not a replacement (tag).

Webel

webel’s picture

webel commented

From http://en.wikipedia.org/wiki/Don't_repeat_yourself:

In software engineering, don't repeat yourself (DRY) is a principle of software development aimed at reducing repetition of information of all kinds, especially useful in multi-tier architectures. The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system."

quadcomm’s picture

quadcomm commented

Confirming my interest in a Drupal 7 version as well, or is there another module like this?