Manually deleted add-on package; now "Add Block" doesn't work

Yikes! One of the add-ons I had installed was a file/resource hog, so I needed to remove it. Problem was that there was no "uninstall" option, and the "edit" button did nothing. So I went to my cpanel file manager, found the offending add-on under ~/packages and manually deleted it. (It still shows up under my dashboard list of add-ons, however.)

So now when I try to edit my site pages by adding a block, I get:

Warning: require_once(/home2/summite4/public_html/packages/gnt_mathjax/blocks/gnt_mathjax/controller.php): failed to open stream: No such file or directory in/home2/summite4/public_html/updates/concrete5.6.3.1_updater/concrete/core/libraries/loader.phpon line 217
Fatal error: require_once(): Failed opening required '/home2/summite4/public_html/packages/gnt_mathjax/blocks/gnt_mathjax/controller.php' (include_path='/home2/summite4/public_html/libraries/3rdparty:/home2/summite4/public_html/updates/concrete5.6.3.1_updater/concrete/libraries/3rdparty:.:/usr/php/54/usr/lib64:/usr/php/54/usr/share/pear') in/home2/summite4/public_html/updates/concrete5.6.3.1_updater/concrete/core/libraries/loader.phpon line 217

Clearly the Concrete5 installation I have still thinks the package is there, tries to look for it, can't find it, and gives up.

What to do?

As can be seen from the above snippet, I am currently running - if I update to, would that fix my issue? I am wary of getting my hands any further involved and really mucking things up, so I am hoping for a relatively easy solution that is not too complicated to implement.

Any tips or advice appreciated ~

View Replies:
AndyJ replied on at Permalink Reply
can you put the package back?

After putting it back - you 'should' be able to uninstall the package - failing that you can track the blocks down and remove them perhaps...
norbie replied on at Permalink Reply
I don't think it's possible to put the package back - the files have been deleted - but I couldn't uninstall the package before, so I don't think putting them back would remedy that.

Is there any way to clean things up manually? What do I look for in trying to eliminate whatever is necessary so Concrete5 will quit looking for components that no longer exist?
AndyJ replied on at Permalink Reply
the add on is this one by the looks of it:

Grab a copy and put it in your /packages directory. This should get you to the point where you can add blocks normally.

If, at that point there are issues with uninstalling that add-on then that will need looking into - but at least your site will be working.

You could manually try and delete references to this package and blocks etc from the db but you might end up in a worse state.
ntisithoj replied on at Permalink Reply
I have a similar problem. I uninstall a package and it says it is uninstalled, but it is still in the installed list. Deleting from the db would be a nightmare!

If the db actually had referential integrity in it (foreign keys), that would be a breeze, but it doesn't... which is very curious to me why they decided to keep the data in a totally unrelated state. was it for speed or some other 'good' reason? It would have to be a pretty good reason to disregarding the integrity of the data. Can anyone shed light on this?

As of now, I have no idea where to look for clues as to why it will not unintiall. Nothing the the server or db logs, no error messages. Especially with packe installations and upgrades, many fatal errors are not reported, so I kind of stuck as to how to debug this. Any suggestions?
norbie replied on at Permalink Reply
Just an update, in case it's useful to anyone else browsing the forums:

I ended up poking around in my c5 database and locating tables related to the manually deleted package. This made it so the "add block" script quit looking for the non-existent package, and now I have no further problems to add blocks.

Yay ;)