ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

How to fully remove an extension that’s causing problems?

November 01, 2010 7:15pm

Subscribe [3]
  • #1 / Nov 01, 2010 7:15pm

    djfenske

    17 posts

    Hi -

    A few weeks ago I installed an extension, that I now have discovered is causing a bit of a problem. I’m willing to lose the functionality of the extension; I first tried disabling it - the problem is still there. I tried removing the php files from the “extensions” and “language/english” folders, and I’m still getting the error message.

    The extension is “Relaxed Member Password Security” (thread here: http://ellislab.com/forums/viewthread/96971/#522028)

    I realize that the extension was unsupported and carried no guarantees…

    The problem it’s causing is this: after a member signs up, and then clicks the activation link in the email they receive, the activation is successful, and they see the confirmation page from the User Message template. I have modified the variable “mbr_may_now_log_in” in lang.member.php to include a link to an SAEF to create a first entry. If a member tries to click that link immediately from the confirmation page, they get the following error message:
    =======
    Error Message
    Unable to load the following extension file:
    ext.nsm_relaxed_member_password_security.php
    =======
    If, instead of clicking the link, I close the browser upon seeing the confirmation screen, then reopen it and type in the link, it opens the form with no errors.

    I’m not asking you to address the problem with the extension, but can you please help me find where it’s trying to load the extension file, even though it has had it’s files removed?

    Thanks very much!
    David

  • #2 / Nov 02, 2010 8:17am

    Sue Crocker

    26054 posts

    Hi, David. Unfortunately we can’t provide official support for third party add-ons. Moving to the CodeShare Corner in case other members of the community might know how to help.

  • #3 / Nov 02, 2010 10:40am

    djfenske

    17 posts

    Hi Sue -

    Thanks for moving my post. Just to re-emphasize - I don’t necessarily need to fix the extension, I just want to find whatever remnant is still in the system trying to call it and failing. If anyone can help, I would greatly appreciate it!

    Thanks, David

  • #4 / Nov 02, 2010 11:35am

    Lisa Wess

    20502 posts

    I’ve moved this back up to tech support since it’s not fixing an extension, but help eradicating it. 

    Are you comfortable with the database?  The way to completely remove this is to remove any references to it in exp_extensions, as well as ensuring any of its files are removed from the file-server.

  • #5 / Nov 02, 2010 12:13pm

    djfenske

    17 posts

    Hi Lisa,

    Thanks for the suggestion; I’m fine with working in the database. I did pull up exp_extensions, and browsed the content. There are 24 rows, and I can identify the extensions referenced in each row. None of the rows reference the problematic extension, “NSM Relaxed Member Security”. I’ve also doublechecked to make sure I have removed both the extension file and its language file from their respective directories.

    I also just tried clearing all the caches through the EE control panel, just to make sure none of the references were cached.

    Unfortunately, I’m still getting the error message that some process is trying to load the extension when trying to open my SAEF from the link in the User Message confirming the new member activation. If I close the browser, then go directly to the link, it does not try to launch the extension.

    Any other suggestions?

    Thanks, David

  • #6 / Nov 02, 2010 1:03pm

    djfenske

    17 posts

    Good news!

    It turns out that the problem was not with the extension being installed, but with the path of the link that I was having the user click on. I had not updated it to use the actual new domain name, but it still had the parent domain/subdirectory path which I used prior to going live with the new domain that pointed directly to the subdirectory.

    I’ve fixed the path and there is no more error message.

    Doh! I feel stupid! Sorry for wasting your time!

    Thanks, David

  • #7 / Nov 02, 2010 3:01pm

    Ingmar

    29245 posts

    Glad to hear you were able to solve this. Please post again as needed.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases