Viper’s Plugins Used

Version 1.1 released!

Messed up using quotes in the header for the “version” column in the table output. Upgrade to v1.11 if you use that column and the table output.

Oh, that’s not good. It just did the same to me when I logged out and then back in. I suspect my plugin is messing up the POST from the login form or something.

I’ll look into it immediately.

Should all be fixed now. Stupid mistake on my part by editing the $_POST array instead of just saving the edited string to my own variable.

Please download the new version (v1.12) and double check that I did indeed fix it.

Glad you like it! Nice site too.

However, as a result of seeing my plugin in work on your site, I realized that ksort() (the PHP function that sorts my plugin array) places capitalized items before lowercase items. I’ll work on getting it to sort in a case insensitive format.

Go to your theme’s folder (/blog/wp-content/themes/fblue/) and make a copy of page.php. Rename it to page-pluginsused.php or something (it doesn’t really matter what).

Open the copy up and add this to the top:

< ?php
/*
Template Name: Plugins Used
*/
?>

That makes it a custom Page template and will make it show up in the list of Page templates when writing or editing a Page.

Then just follow the rest of the instructions in the plugin’s readme.

Odd, that line looks fine to me and it’s the first I’ve heard of this. *shrugs*

It’s a shortcut for this:

if ($vipercustominfo[$editplugin]) {
$currentdescription = $vipercustominfo[$editplugin];
} else {
$currentdescription = $viperspluginsused->plugindata[$editplugin]['description'];
}

What version of PHP are you using? If you’re running a really old version or something, you could try replacing it with the above code, but I HIGHLY doubt it’ll fix it as I’m pretty sure WordPress uses that shortcut too. But, worth a shot.

No, the code I had is perfectly valid. I mean, you’re the first one to have any issues with that part of the plugin. You must have a weird PHP configuration or something. Odd.

I’ll be releasing a new version soon that should fix that as this new version will use the built in WordPress function that creates the plugins page in the admin area. Hang tight.

No, you need to create a custom Page template and then apply it to a WordPress Page. You don’t access the template directly.

http://codex.wordpress.org/Pages#Creating_your_own_Page_Templates

Speaking of which, work is continuing on the new version (that uses the WordPress core functions to get the plguin details as well as fixes some sorting issues) and it should hopefully be out in a week or two if I remember to keep working on it.

Yes, the next version of this plugin will have some functions that’ll basically call the class and run it so that you can use the PHP plugins.

That won’t work because viperspluginsused() isn’t a function. You’ll want this:

< ?php
if (class_exists('viperspluginsused')) {
$viperspluginsused = new viperspluginsused();
$viperspluginsused->output_table('id="pluginstable"', TRUE, TRUE);
}
?>

No, tags are useful, for example the code tag.

As for relative links, just use the options page of this plugin to edit the displayed description for the plugin to something else, i.e. remove the link and such.

Although I can’t remember if this plugin checks for only allowed tags or not. I really need to update this thing…

I really should update this plugin…

Anyway, yes, the rows already have alternating classes. All you need to do is create some CSS, no plugin editing needed.

Do you need help with the CSS or were you just thinking that modification of the plugin was needed?

[Comment ID #1172 Will Be Quoted Here]

http://www.viper007bond.com/wordpress-plugins/forums/viewtopic.php?id=150

[Comment ID #8841 Will Be Quoted Here]

Well, first make sure you don’t have any really long URLs or anything in the descriptions that are forcing the text to not line wrap. IF you do, use this plugin’s options page to edit the descriptions that get displayed.

After that, you can use CSS to control the overall width of the table. The table has the CSS id “pluginstable”, so something like this will probably work:

#pluginstable { width: 800px; }

[Comment ID #8843 Will Be Quoted Here]

Yeah, as I suspected, you have a long string that isn’t wrapping and it’s forcing the width of your table to be quite large. You need to edit the displayed description for “Landing sites” and remove this bit:

http://www.w-a-s-a-b-i.com/archives/2006/02/02/wordpress-related-entries-20/

or at least turn it into a hyperlink. It’s forcing that column to be really wide.

JYL on July 14th, 2006 at 7:03 PM2006-07-15T02:03:50ZF jS, Y \a\t g:i A wrote:

but can i set up the row color of table?

Yes, the rows are given alternating CSS classes, “pluginrow” and “pluginrowalt”. Just define the styles in your CSS file.

Martin Cleaver on August 22nd, 2006 at 5:59 PM2006-08-23T00:59:45ZF jS, Y \a\t g:i A wrote:

Does this work with wpmu?

Dunno, I have very little experience with MU. However, from what I do know, my guess is yes.

Erik J. Barzeski on December 21st, 2006 at 3:41 PM2006-12-21T23:41:07ZF jS, Y \a\t g:i A wrote:

The use of $title* variables leads me to believe it isn’t currently compatible with WP 2.1.

Mmm, so you’re right. I never checked that page after I updated my blog to 2.1. Whoops!

Conveniently enough though, I had actually already started a recode from scratch for just general improvement reasons. I’ve been coding it in the latest SVN, so it will indeed be compatible with 2.1.

ovidiu on December 24th, 2006 at 4:44 AM2006-12-24T12:44:05ZF jS, Y \a\t g:i A wrote:

you say it is not compatile with wp 2.1 but it works with wpmu which is based on wp2.1….

All I know is that a PHP error comes up in WP 2.1 and it didn’t previously. I haven’t had a chance to look into the exact problem due to other projects and the holidays.

And I doubt all of the changes to the SVN have been ported to MU. It’s probably a bit behind the main core.

ovidiu on December 24th, 2006 at 4:44 AM2006-12-24T12:44:05ZF jS, Y \a\t g:i A wrote:

another thing is, can I somehow modify your plugin to just list all available plugins? I need to show a list of all available plugins, rather than those I use.

Use get_plugins(). It returns an array of all plugins in the plugins directory. You may need to require/include in wp-admin/admin-functions.php.

Josh Nichols on January 26th, 2007 at 7:54 AM2007-01-26T15:54:03ZF jS, Y \a\t g:i A wrote:

I use it and upgraded to 2.1 and everything works for me.

http://joshnichols.com/house/about/

I’m such an idiot! I looked at my plugins used page and saw an error, so I figured it didn’t work.

Just turns out I had accidentally overwritten it with the half recoded version which of course wasn’t done, so…

*sigh*

Delores on October 23rd, 2007 at 10:58 AM2007-10-23T17:58:14ZF jS, Y \a\t g:i A wrote:

I don’t understand something. Why do I have to create a whole new page template instead of just pasting the `output_table(); ?>` code in a new page post (as you can with the contact form plugin)?

Because they are different plugins and work completely differently? Apples and oranges.

But yes, I need to rework this plugin to make it easier to implement.