[Plugin: Link Shortcut] Warning messages during initial configuration

Like others, I received warning message like this on the admin pages of the Link Shortcut plug in after I installed and activated it.

Warning: include(<snip>/htdocs/wordpress/wp-content/plugins/link-shortcut/admin/footer.inc.php) [function.include]: failed to open stream: No such file or directory in /homepages/36/d183424680/htdocs/wordpress/wp-content/plugins/link-shortcut/admin/list.inc.php

I was able to fix these warning messages by editing these 4 plugin files:
wp-content\plugins\link-shortcut\admin\add.inc.php
wp-content\plugins\link-shortcut\admin\edit.inc.php
wp-content\plugins\link-shortcut\admin\list.inc.php
wp-content\plugins\link-shortcut\admin\options.inc.php

At the bottom of each of these files is a line like this:

<? include LINKSHORTCUT_UI_LOC . "/footer.inc.php" ?>

Change this file name from “footer.inc.php” to “main.inc.php” to get rid of the warning messages.
<? include LINKSHORTCUT_UI_LOC . "/main.inc.php" ?>

After I did this, I still had an issue where I was not seeing the Save buttons to create or edit the link shortcuts. I’m not sure why they weren’t showing because I could see the HTML in there when I did view source. However, I was able to fix this by copying the Save buttons out to a new location where for some reason it was visible. Not sure if this was a style issue or what, but it worked.

In wp-content\plugins\link-shortcut\admin\add.inc.php, I did the following:

Locate the Save button code around line 58:

<input name="save" type="submit" class="button-primary" id="publish" tabindex="4" accesskey="p" value="Add Link Shortcut" />

Copy this line down below the Shortcut Name section so that it still appears within the main body:

<input name="save" type="submit" class="button-primary" id="publish" tabindex="4" accesskey="p" value="Add Link Shortcut" />

	</div>
      </div>
      <!-- /main body -->

Do the same thing for wp-content\plugins\link-shortcut\admin\edit.inc.php
<input name="save" type="submit" class="button-primary" id="publish" tabindex="4" accesskey="p" value="Save Changes" />

Good luck! With these changes I was able to fix my issues and successfully use this plug-in.