DamnSexyBookmarks Activation error “Plugin could not be activated because it triggered a fatal error.” – Solution

While trying to activate the DamnSexyBookmarks plugin for wordpress you might encounter the error:

Plugin could not be activated because it triggered a fatal error.

The problem is because the plugin interferes with the already activated plugion “Sexy Bookmarks”

So the solution is to simply deactivate the Sexy Bookmarks plugin and then activate the DamnSexy Bookmarks Plugin.

5 comments on “DamnSexyBookmarks Activation error “Plugin could not be activated because it triggered a fatal error.” – Solution

  1. Not sure if you know but DamnSexyBookmarks is now defunct and no longer maintained.

    It was merged with the Original SexyBookmarks a while ago: https://wordpress.org/extend/plugins/sexybookmarks/

    For the latest version you should deactivate DamnSexyBookmarks and active SexyBookmarks.

    I know the name makes damnsexybookmarks *sound* like it’s better, but really sexybookmarks is what is the latest and greatest! :)

    1. Thanks for the information Andrew.

      I have disabled the sexybookmarks plugin today on my blog because of some un optimized code and features (in my view atleast) including that it loads all the graphics and css for all the buttons even if we select to show a few of them on the post page. I might be editing the code myself before re enabling it here or otherwise i might go for manual links at the end of the article to social bookmarks. Also the word “sexy” in the source of every page might cause google attention too (my view! not sure)

  2. Five great plugin I have begun to use is WordPress File Monitor. This plugin scans your WordPress installation & reports if any files have been added, deleted, or changed. The plugin is customizable to run on a schedule that you set. You can also exclude directories from the plugin’s reporting so that you are not alerted every time you upload a picture to insert in to a post. I, however, recommend that you do not exclude directories as that directory may be the next location of the next exploit.

Leave a Reply

Your email address will not be published.