My site previously was Drupal 5.x, and I utilized signatures for forums to plug sigs into our forum posts.

I have recently upgraded my site to Drupal 6.8 which now has a core signatures feature. The core feature now
allows signatures to be added to comments in different content types.

My question: Is there an efficient way to copy profile signatures that were entered in Signatures for Forums profiles
to the Drupal 6 core signatures tables? The signatures needs to be saved in core signatures in order for them to be used
with other content types. The only way I can think to do this is to copy each signature from a backup database into each
users profile manually. Any other ideas how to do this?

I still plan to use signatures for forum module to post signatures for original node authors.

Comments

snsace’s picture

It turns out there is no issue here.

When I uninstalled the signatures for forums module completely, the user signatures which had originally been entered
were still in the core user tables. I thought uninstalling the SFF module would dump the signatures and they would have
to be re-entered by each user in their profile.

It is strange though that WITH SFF installed, only signatures showed in forum posts. Comments to other content types
failed to show signatures.

So if core is handling signatures now...what is the point of SFF in 6.x ?

liam mcdermott’s picture

Status: Active » Fixed

It is strange though that WITH SFF installed, only signatures showed in forum posts.

Signatures for Forums makes it possible to select which node types signatures should be displayed under. If signatures are only showing under forum posts, it's likely that this is the only node type checked on the Signatures for Forums admin page. :)

So if core is handling signatures now...what is the point of SFF in 6.x ?

See the list on the module project page, Drupal 6 core only provides items one and two on that list. Probably the biggest problem for Drupal core signatures is that they're only 255 characters long, this gets eaten up when you allow HTML/BBCode.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.