To start, I did have to adjust the module to allow for weight consideration less than -50, since the pagination module I use is set at that weight. I had to adjust the weights of my social networking buttons (digg, tweet, facebook) to get them to remain floating above content on each page. All I did was change the range in the diggable.module to be between -75 and 15). All the buttons seemed to be working fine, except the digg buttons started dropping to the bottom of the page again, but for only "article" type content. The remaining content types are still working flawlessly. Running my buttons at weights of -60 (diggable), -61 (fb), & -62 (tweetmeme)

I have since had to uncheck all my content types for diggable (I would have removed it but I love the widget), and then I reactivated the diggthis module to show the buttons in my content. And it continues to work without this issue.

Anyone have any suggestions? I did check my css styles and also disabled/re-enabled the article content type. This was glitchy and actually worked for a minute then upon refresh, it dropped to the bottom of the page again. And it only does it for the one content type.

Any suggestions are appreciated.

Comments

Scott Reynolds’s picture

Scott Reynolds commented
Status: Active » Needs review

Using CCK you could able to move them around

at admin/content/node-type/article/fields and you can drag and drop it in the place you want. Module weight for this will not work.

Please confirm that works for you. Looking at the code I believe there is a bug there.

prolific_one’s picture

prolific_one commented

Ok, I must have moved the Digg Button field around when I was making other adjustments in the Article content type. I went in to another content type to test it and sure enough, now it does the same thing. If I don't touch the Digg Button field then the weight goes by what is set in the module or the DiggABLE admin settings page. Is there a way to get it to reset back to where DiggABLE controls the weight instead of the CCK field, other than completely uninstalling and reinstalling the module?

Scott Reynolds’s picture

Scott Reynolds commented

CCK attaches a property (something like '#content_type_weight') to the $node->content. So if you need to have it use the default weight provided on the admin screen you have to remove the diggable weight from that property. You can modify this property in a hook_nodeapi().

be advised this is by far not my recommended way. All of the fields (pagination, Facebook, tweetme etc) should instead integrate with the cck, so that all those fields can be adjust on this page. Weights only mean something when they are viewed relative to everyone else. And the only way to get that view is through hook_content_extra_fields.

The only reason Diggable provides the weight on the admin settings page is because some sites do not use CCK. This will change and be removed in D7 port as all sites will be using the Fields.