128 thoughts on “Viper’s Plugins Used”

1. Pingback: WordPress Station » Blog Archive » Viper’s Plugins Used

2. Easy install! Much better than the old one!

3. Version 1.1 released! 🙂

4. 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.

5. Nice plugin, easy install. But it inconsistently broke my site, and I can’t quite figure out why. The site pages themselves displayed happily, and the dashboard displayed happily, but the login screen stopped re-directing to the dashboard and displayed a blank screen. Most odd. Maybe it’s not playing nice with one of my other plugins?

6. 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. 🙂

7. 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. 🙂

8. Awesome plugin, thanks! I too was not completely happy with the pluginsusedPlugin — yours rocks 🙂

9. 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. 🙂

10. Hey Viper, glad you knew what was going wrong. I thought I’d stuffed up immensely. Have downloaded and installed 1.12 and it all seems to be working happily. Thanks!

11. Pingback: mertex.de.tc » Blog Archiv » Benutzte Plugins

12. Pingback: OS X Code (r,s) - A Mac blog about coders and the code they write. » Top 20 Wordpress Plugins

13. Pingback: Xrossblog » Blog Archive » Neue interne Seite: plugins

14. I am really frustrated with this damn thing please someone explain how i make the template and dont refer me to the codexcuz i dont get it.

15. 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:

    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.

16. hey thanks for reply and help Viper works fine now 🙂

17. Pingback: tylerwillis.com - Hurricane Wilma eats tylerwillis.com

18. Hi viper, This is just what I was looking for except… it’s killed my site. All I get now is the following error:

    Parse error: parse error, unexpected $ in /home/chowitco/public_html/qwertyrash/wp-content/plugins/vipers_pluginsused.php on line 238

    Line 238 looks like this

    $currentdescription = ($vipercustominfo[$editplugin]) ? $vipercustominfo[$editplugin] : $viperspluginsused->plugindata[$editplugin]['description'];

    I’ve deleted the plugin for now and my site is working again.

    thanks

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

20. lol. As a sometime programmer I can so relate. Can you explain that line of code, what it’s trying to do, and what the “?” and “:” do

21. 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. 🙂

22. Thanks. That worked. I know that doesn’t make sense except… are you sure that “?” is right? wouldn’t it be a “:” too?

    My host is running PHP 4.4.1 and MySQL 4.1.13

23. 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.

24. I installed this plugin, everything looks perfect but just some warning occured.

    Warning: file(c:\program files\apache group\apache\htdocs\wp//wp-content/plugins/): failed to open stream: Permission denied in c:\program files\apache group\apache\htdocs\wp\wp-content\plugins\vipers_pluginsused.php on line 93

    Warning: implode(): Bad arguments. in c:\program files\apache group\apache\htdocs\wp\wp-content\plugins\vipers_pluginsused.php on line 93

    How can i avoid this?

25. 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. 🙂

26. ok, i’ve made the copy of the page and it is founf in the theme editr, but where or what is the link to the page ive made? doh i’m so stupid i hate myself, is it
    http://www.philip.hotserv.dk/wp-content/themes/FallingLeaves/pluginsused.php

    cause then i only get: Fatal error: Call to undefined function get_header() in
    /var/www/hotserv.dk/users/philip/wp-content/themes/FallingLeaves/pluginsused.php on line 6

27. 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

28. [Comment ID #377 Will Be Quoted Here]

    Hi,

    I got the same error first time I used your plugin. In some cases the $plugin-Array contains an empty [0]-index. so just insert a

    if(isset($plugins[0]) && empty($plugins[0])) { unset($plugins[0]); }

    between

    function viperspluginsused() {
    $plugins = get_option(‘active_plugins’);

    and

    $output = array();

    to throw away these error.

    regards

    Arno

29. 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. 🙂

30. Pingback: Blue Mint » Viper’s Plugins Used

31. Would it be possible to use something like runPHP to call your plugin instead of making a dedicated template?

32. 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. 🙂

33. One more… I tried taking precaution with plugin deactivation and plugin calls inside my themes by using the function_exists PHP call. Here’s what I did for yours:

    < ?php if (function_exists('viperspluginsused')) { ?>
< ?php $viperspluginsused = new viperspluginsused(); ?>
< ?php $viperspluginsused->output_table('id="pluginstable"', TRUE, TRUE); ?>
< ?php } ?>
    (minus the spaces between the

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

    output_table('id="pluginstable"', TRUE, TRUE);
}
?>

35. Thanks, worked great!

36. Nice plug 🙂

    Worked great for me in just minutes.

37. Thanks Viper! I had this exact plugin in mind and I was tempted to write one myself 😉 Now you’ve saved me time to … well… do what I’m paid to while I’m at work 😉

    One question though – I would like to integrate the css styles more tightly with the rest of my blog, which is currently utilizing the ‘blix’ theme. Do you know of a quick n’ easy way to do this? Something like …

    oh wait… reading id=pluginstable now… SWEET!

    Cheers!

38. Great plugin.

    One suggestion would be to use a strip_tags() function call on the description as without it relative links (which many people use in their descriptions) get a 404 error.

39. 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…

40. Pingback: DonsTag » Fix (II)

41. Thanks for making this plugin.

    Just letitng you k now I had to use:
    http://www.viper007bond.com/wordpress-plugins/vipers-plugins-used/#comment-377

    to get rid of an error message and I also had to use:
    output_table(‘id=”pluginstable”‘, TRUE, TRUE);
    }
    ?>

    as you suggested.

42. On row 160 you have:

    $rowstyle = ($rowstyle == ‘class=”pluginrow”‘) ? ‘class=”pluginrowalt”‘ : ‘class=”pluginrow”‘;

    Is this for displaying alternate row colours as in the admin display?

    Basically, I’m wondering if you could please help me work out how to display the plugins list with the css styling exactly like that in the wp-admin/plugins.php page.

    It looks like you’ve already set this up for alternate row styling, etc. At least you have definitely done this for the admin. Are you able to help please work this out?

43. 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?

44. Hi, it seems that the plugin is having problems with accented characters, see here as compared to there where they display ok. TIA.

45. [Comment ID #1172 Will Be Quoted Here]

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

46. re: question marks: Sorry, my bad, it was just an encoding problem.

47. Pingback: 羅賓のweblog » [2006/04/22 - 2006/05/08] 書籤摘錄 | 每天早上都會被自åÃ

48. Pingback: 無由亂記 » ‧Plugins Used

49. Thanks so much for the plugins widget. V useful //!

50. Arno Simon, thank you so much for the tip about the $plugin-array! Thanks to you, I can use this great plugin! 🙂

Comments are closed.