Hi, I have been using AddThis in a drupal 5.10 install for some time and it worked fine. When I tested the 2.0-beta5 however my links disappear, and there is no addthis item in the admin menu. The user permissions are set correctly so I don't know what is the trouble.

Comments

vesapalmu’s picture

Assigned: Unassigned » vesapalmu
Status: Active » Postponed (maintainer needs more info)

This could be a problem with Drupal menu cache. Try going to admin/build/modules and saving the modules once. You don't have to make any changes, this will reset the menu cache and you should have admin settings for the module again.

Let me know what happens.

twowheeler’s picture

Ok, no difference. Anyway, I ran the upgrade script after upgrading the module and that should have cleared all of the cache tables.

vesapalmu’s picture

And you can not access admin/settings/addthis even after clearing the cache? Do you get any errors with the module enabled?

I recommend a clean install of addthis just to be sure we are not dealing with any old file versions or cache issues.

twowheeler’s picture

Title: 5.x-2.0-beta5 not working for me » 5.x-2.0-beta5 menu item missing
Status: Postponed (maintainer needs more info) » Active

Here is an update. I can access the admin settings page by entering the url http://mysite.com/admin/settings/addthis manually. From there I can enter all of the settings and the widget appears normally. The only issue is that the menu item does not appear. There are no errors, and no matter what I do with the clean install - uninstall - reinstall - clearing cache - whatever, it has no effect. I looked at the menu settings to see if the menu item is installed but disabled, but it is not there.

I updated to 5.11 yesterday, with no change in this issue.

Edit:
Ah! Commenting out line 50 ("'type' => MENU_LOCAL_TASK,") allows the menu item to appear. The default would be MENU_NORMAL_ITEM. Is this a theme issue? I am using the artistsC01 theme.

vesapalmu’s picture

Status: Active » Fixed

You are right about that one. I wonder how that one got in there... This has now been fixed in 5.x development branch. I will do code review for the module and take 5.x version out of beta finally. Feel free to use the development snapshot for now. Unless any new bugs are found in near future it is mostly identical with the first actual release.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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