Toplist for Drupal 6 ? Is it the only Top referrers module ?

Hi, currently there are no plans to port it to Drupal6: I simply don't have time to do it, nor need it for any projects of mine.
I will be glad to give CSV access to anyone that shows up some serious intention to do so.

Bye,
Marco

Hi,

I think I would benefit from this in my projects. Sadly I am not a developer. Maybe I could test new versions.

By the way what about merging with the directory project?

Cheers,
Marc.

Hi, it doesn't seem that toplist is that success. I mainly developed this module for a website of mine and released in the hope that somebody could benefit and contribute to it.

I do not need to migrate the website to Drupal6, so I don't need to migrate toplist to Drupal6 and I don't have so much time to put in it.

Migration should be easy: if you can't do it yourself, I suggest that you place a bounty and somebody could possibly do it, or hire somebody to do it (in any case, it would be nice if you decided to release the resulting product in opensource - I could give you credits)

Bye,
Marco

+1 for drupal 6 migration. Would be happy to have link-exchange possibility on D6!
greetings,
Martijn

I hope someone gets on this project and produce a toplist module for Drupal.

Hello,

+1

How much would it cost to get it fast ?

Thanks !

@diggfrance: How much would you pay to get it fast?
cafetiere expresso

Can we setup a chipin? I would contribute some cash as well

As I said to diggfrance in private, I could do the activity of porting for 75 euros (or 100 USD) in two weeks' time after I receive the payment on PayPal (account to be specified)

In exchange, I could place a link to the site of the sponsor(s) from the toplist page specifying that those were those who sponsored the upgrade of the module to D6. The upgrade would be released to the community. If somebody releases a patch to D6 before I release the module, I will in any case end the porting and release it to the public, and no refund would be done.

Bye,
Marco

Hi, I would prefer that we reach the sum here "on the paper", before starting to accept money: I do not want to feel obliged of doing things if we do not reach the amount nor would like to deal with refunds. Please, only serious people.

So:
wwwoliondorcom - 20 USD

Total:
20 USD (target: 100 USD/75 EUR)

Let's keep going.

Hi,

I'll chip in $20, let me know when youre ready to start!

I can make a logo for toplist module, maybe that can count for $10?

I pledge to contribute $10 if a usable D6 version is there before end of July.

http://drupal.org/project/deadwood

Hi, any progress in this field please?
Thanks for sharing.
greetings, Martijn

Unluckily no news, the fundraising seems to be stopped since very few are contributing.

Bye,
Marco

Hello,

I wont be contributing for this as my interests shifted. Also I learned since that the module would enable giving a link back thus creating a link exchange scheme, which is detested by Google and the search engines.

I extend my pledge from #19 if there's a functioning non-beta D6 module by the end of October.

Hey there.

I go way back with toplists.

I'd love to port this to 6.x.

If you're still interested in someone taking this to 6.x, I'd be interested in CVS.

Tony

Hi Tony, great you are gonne take this to D6, looking forward to test for you. Would be great if it would have views 2 integration in D6!
Greetings, Martijn

http://github.com/skiquel/drupal-toplist <= work in progress

At the moment I'm working on getting our current version ported to 6.x

I think the next version would work pretty well if we had views working w/ it. :)

Tony

Hi skiquel, I'm glad that you are working on the porting to D6.
I have granted you the CVS access to the repository, so that you can create the Drupal6 branch and start committing there your work.

Hope to hear you soon.
Thank you, bye,
Marco

Any news? Toplist for D6 would be nice.

@alliax (#30): yepp! ;)

@skiquel (#28): What's the status of your porting attempt? I'm getting this when cloning the git repository:

# git clone http://github.com/skiquel/drupal-toplist
Initialized empty Git repository in /var/www/test/sites/all/modules/drupal-toplist/.git/
warning: remote HEAD refers to nonexistent ref, unable to checkout.

Result of running the 'Toplist' module toplist-5.x-1.x-dev.tar.gz through Deadwood: there's too much manual intervention required:

/* TODO New hook_mail implementation
Because of changes to drupal_mail function, you need to move the variables
setup and string replace commands into the hook_mail implementation and then
call drupal_mail with the name of the module which contains this
implementation, the mailkey, the recipient, the language of the user the mail
goes to and some arbitrary parameters. */

/* TODO FormAPI image buttons are now supported.
FormAPI now offers the 'image_button' element type, allowing developers to
use icons or other custom images in place of traditional HTML submit buttons.

/* TODO Check node access before emailing content
Modules like Organic Groups and Project Issue send the same content as an
email notifications to many users. They should now be using the new 3rd
parameter to node_access() to check access on the content before emailing it.
Note that db_rewrite_sql() provodes no protection because the recipient is not
the logged in user who is receiving the content. */

/* TODO Remove $row argument from db_result() method
The $row argument of db_result() was removed from the database abstraction
layer in 6.x core, as it was a database dependent option. Developers need to
use other handling to replace the needs of this method. */

/* TODO Remove db_num_rows() method
The db_num_rows() method was removed from the database abstraction layer in
6.x core, as it was a database dependent method. Developers need to use other
handling to replace the needs of this method. */

/* TODO Change 'Submit' to 'Save' on buttons
It has been agreed on that the description 'Submit' for a button is not a
good choice since it does not indicate what actually happens. While for
example on node editing forms, 'Preview' and 'Delete' describe exactly what
will happen when the user clicks on the button, 'Submit' only gives a vague
idea. When labelling your buttons, make sure that it is clear what this
button does when the user clicks on it. */

/* TODO New user_mail_tokens() method may be useful.
user.module now provides a user_mail_tokens() function to return an array
of the tokens available for the email notification messages it sends when
accounts are created, activated, blocked, etc. Contributed modules that
wish to make use of the same tokens for their own needs are encouraged
to use this function. */

/* TODO
There is a new hook_watchdog in core. This means that contributed modules
can implement hook_watchdog to log Drupal events to custom destinations.
Two core modules are included, dblog.module (formerly known as watchdog.module),
and syslog.module. Other modules in contrib include an emaillog.module,
included in the logging_alerts module. See syslog or emaillog for an
example on how to implement hook_watchdog.

/* TODO Implement the hook_theme registry. Combine all theme registry entries
into one hook_theme function in each corresponding module file.

/* TODO
Non menu code that was placed in hook_menu under the '!$may_cache' block
so that it could be run during initialization, should now be moved to hook_init.
Previously we called hook_init twice, once early in the bootstrap process, second
just after the bootstrap has finished. The first instance is now called boot
instead of init.

In Drupal 6, there are now two hooks that can be used by modules to execute code
at the beginning of a page request. hook_boot() replaces hook_boot() in Drupal 5
and runs on each page request, even for cached pages. hook_boot() now only runs
for non-cached pages and thus can be used for code that was previously placed in
hook_menu() with $may_cache = FALSE:

Dynamic menu items under a '!$may_cache' block can often be simplified
to remove references to arg(n) and use of '%' to check
conditions. See http://drupal.org/node/103114.

The title and description arguments should not have strings wrapped in t(),
because translation of these happen in a later stage in the menu system.

/* TODO Create a hook_mail($key, &$message, $params) function to generate
the message body when called by drupal_mail. */

I'd sponsor a working D6 port as per #15, also.

However, I've not yet seen this module in action, so I don't know to which degree it is integrated into Drupal at all, what features it offers (banners? tabular listings? backlink checking?), and I'm not really comfortable with a module maintained on a minimal effort basis.

If the Drupal framework isn't used seriously (no views integration, no CCK integration, doesn't use taxonomy...), we might be better off to use an external script like ToplistX, Aardvark Topsites PHP or Top XL and make it match our website's design. Anyway, even a simple Drupal-based approach would be favourable.

What's the current state of the TopList -module development? ...I'm willing to donate as well.

I will commit 20Euros for this ....and pay up .....too !

I will commit also 20 euro for a drupal 6 version, but under the conditions of #35, with views integration, may be also panels..
greetings, Martijn

And what about Drupal 7 ?

Let's first have it for D6, a lot of sites will be on D6 for the coming year I think.
greetings, Martijn