Hi,

Today I'm trying to implements this module in my Drupal 7. When I trying to add a "Publish link" field type in views, it doesn't work. The error message is: "The handler for this item is broken or missing and cannot be used. If a module provided the handler and was disabled, re-enabling the module may restore it. Otherwise, you should probably delete this item."

Thanks!

Comments

Initsogar’s picture

Initsogar commented

So, I was trying again and again... I think now it's solved.
I edit publishcontent.module at line 213 in publishcontent_views_data_alter() method:

    'field' => array(
      'handler' => 'publishcontent_views_handler_field_node_link',
    ),

With this:

    'handler' => 'publishcontent_views_handler_field_node_link', //SOLVED
Initsogar’s picture

Initsogar commented
Status: Active » Fixed
mr.andrey’s picture

mr.andrey commented
Status: Fixed » Needs work

the above fix just made the option disappear for me

Sinan Erdem’s picture

Sinan Erdem commented
Version: 7.x-1.0-beta1 » 7.x-1.x-dev

same here...

jg314’s picture

jg314 commented
Version: 7.x-1.x-dev » 7.x-1.0-beta1

I am having this same issue on 7.x-1.0-beta1. Subscribing.

amanire’s picture

amanire commented

Subscribing

aaronbauman’s picture

aaronbauman
he/him
commented
Version: 7.x-1.0-beta1 » 7.x-1.x-dev

I can't reproduce this on a clean install.
Are you upgrading from d6 to d7 and running into this issue?

Please provide more details.

If this is an issue with DEV, please don't change the version number back to BETA1.
If this is only an issue with BETA1, then it should be marked fixed and I'll roll a new release.

jg314’s picture

jg314 commented

So the issue is fixed in the dev release, but not in the beta release? Right now I am using the beta1 release and have the issue. Would you recommend I upgrade to the dev release?

Thank you.

aaronbauman’s picture

aaronbauman
he/him
commented

As far as I can tell this issue does not exist in the dev branch, though I have not thoroughly tested.
If anyone on this thread can confirm that this issue is fixed in dev, then I will close this issue and roll a stable 7.x-1.0 release.

jg314’s picture

jg314 commented

I just tested the dev release on a Drupal install running 7.7 and I am still seeing the handler issue.

aaronbauman’s picture

aaronbauman
he/him
commented

Please provide more info about your setup and complete steps to reproduce the issue:
Minimal or Standard install profile?
What other modules?
What version of views?
Any additional info that might be helpful.

I cannot reproduce this using:
Drupal core 7.7 -- Minimal install profile
Chaos tool suite (ctools) 7.x-1.0-rc1
Publish Content 7.x-1.x-dev (2011-May-24)
Views 7.x-3.0-rc1

jg314’s picture

jg314 commented

I am using Drupal 7.7 with the following modules:

Views 7.x-3.0-rc1
Chaos Tools 7.x-1.0-rc1
Publish Content 7.x-1.x-dev

I have a whole host of other modules that I'm using. Do you want me to list them all?

aaronbauman’s picture

aaronbauman
he/him
commented

Like I said, I can't reproduce the issue on a clean install, so there must be a conflict with another one of the modules you're using.
Let us know if you can figure out which.

cateye’s picture

cateye commented

I have this issue too.

aaronbauman’s picture

aaronbauman
he/him
commented
Status: Needs work » Postponed (maintainer needs more info)

Postponed on comment #11
Please provide steps to reproduce.

kmetz’s picture

kmetz
he/him
commented

I had the same issue, with the current dev version, and it fixed itself after I disabled and re-enabled the publishcontent module, cleared all caches (on admin/config/development/performance), explicitly cleared the views cache (admin/structure/views/settings/advanced) and ran cron. Unfortunately I did thatin one step so I don't know what exactly 'fixed' it.
HTH.

fizk’s picture

fizk commented

You could get this error if files[] = publishcontent_views_handler_field_node_link.inc was missing from publishcontent.info, but the 7.x-1.0 release already has this.

simon georges’s picture

simon georges commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

So, apparently, when every cache is cleared, it's working (at least in -dev branch).