Here is my Recent Log Message:

TYPE:	theme
DATE:	Tuesday, January 31, 2012 - 11:39am
USER:	admin
LOCATION:	...//tentofappointment.com/admin/config/content/linkit/list/default/edit?render=overlay
REFERRER	:       ...//tentofappointment.com/
MESSAGE:	Theme key "_linkit_theme_profile_form_table" not found.
SEVERITY: 	warning

How do I correct this, it continues to do this even after I made changes and saved.

Thanks!...

Comments

anon’s picture

Try clear the cache.

anon’s picture

Status: Active » Closed (fixed)
danny englander’s picture

Status: Closed (fixed) » Active

Hi I am sorry to reopen this but I am having the same exact issue. After I got this error, linkit no longer worked, i.e. I could not start typing to get node suggestions. I tried "drush cc all" and also tired clearing the cache in the Drupal UI as well but no joy.

anon’s picture

Ok, What did you do before this happend? Updated Linkit? Updated anything else? Uninstalled anything?

danny englander’s picture

I updated to Drupal 7.12. Nothing else really changed. I will try uninstalling the module and then reinstalling to see if that makes a difference.

anon’s picture

highrockmedia: Any progress yet in the reinstall

danny englander’s picture

Hi, I have fixed the issue. The steps were to disable the module and then remove the reference to linkit in the System table and remove the linkit profiles table as well. The reenabling the module made linkit work.

anon’s picture

Status: Active » Closed (fixed)

Ok, as this seems to be fixed, I will close this issue now.

carl.ben’s picture

Status: Closed (fixed) » Active

This message occurs even after the above steps. Caches flushed repeatedly.

Linkit 7.x-1.3 was installed, but not used before 7.x-2.1 was released. So it was disabled and uninstalled, then 7.x-2.1 installed. (this may not have anything to do with this issue)

The warning started appearing when the page at admin/config/content/linkit was visited.

I disabled/uninstalled 7.x-2.1, and removed the reference in the System table. (The profile table was removed by the uninstall)

After reinstalling 7.x-2.1, the warning continues to appear, but now apparently only when admin/config/content/linkit is saved. Just visiting the page does not give the warning.

Is it something to do with http://drupal.org/node/412730 ?

anon’s picture

Status: Active » Fixed

Commited a fix!

Thanks for reporting this.

See commit here http://drupalcode.org/project/linkit.git/commit/c8a33d2

carl.ben’s picture

I installed the 3/21 2.x-dev (which appears to incorporate the git changes), ran update.php, and get these ctools notices:

Plugin entity:uc_order of plugin type linkit:linkit_plugins points to nonexistent file sites/all/modules/linkit/plugins/linkit_plugins/linkit-plugin-uc_order.class.php for class handler handler.

Plugin entity:profile2 of plugin type linkit:linkit_plugins points to nonexistent file sites/all/modules/linkit/plugins/linkit_plugins/linkit-plugin-profile2.class.php for class handler handler.

Plugin entity:field_collection_item of plugin type linkit:linkit_plugins points to nonexistent file sites/all/modules/linkit/plugins/linkit_plugins/linkit-plugin-field_collection_item.class.php for class handler handler.

Plugin entity:comment of plugin type linkit:linkit_plugins points to nonexistent file sites/all/modules/linkit/plugins/linkit_plugins/linkit-plugin-comment.class.php for class handler handler.

After editing the Linkit Edit form, these php notices appear:

http://.../admin/config/content/linkit/list/default/edit
MESSAGE	Notice: Undefined index: label in LinkitPluginEntity->__construct() (line 65 of .../sites/all/modules/linkit/plugins/linkit_plugins/linkit-plugin-entity.class.php).

http://.../admin/config/content/linkit/list
MESSAGE	Notice: Undefined index: label in LinkitPluginEntity->__construct() (line 65 of .../sites/all/modules/linkit/plugins/linkit_plugins/linkit-plugin-entity.class.php).
carl.ben’s picture

Status: Fixed » Active
anon’s picture

Status: Active » Fixed

This is not related to the original issue.

Please, start a new issue for this.

Status: Fixed » Closed (fixed)

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