Removing extension subasteve/flarum-ext-mailing

Dezibel1000

Hi everyone,

I'm new to Flarum and would appreciate your help.

I'm running Flarum 1.8.11 and installed the extension subasteve/flarum-ext-mailing via the Extension Manager. I have since learned that I should have used clarkwinkelmann/flarum-ext-mailing instead.

When attempting to enable the subasteve extension, Flarum throws an error in both the backend and frontend.

Error log:
flarum.ERROR: Error: Call to undefined method Flarum\Extend\ApiSerializer::mutate() in /mnt/web422/b2/23/544118623/htdocs/ecopark2/flarum/vendor/subasteve/flarum-ext-mailing/extend.php:18

Trying to uninstall the extension also fails.

What I’ve already tried:

Deleted the directory /vendor/subasteve

Removed the "subasteve" entry from composer.json and composer.lock

Current situation:

Both backend and frontend load correctly again

However, the "Mailing" item still appears in the left-hand Extension/Feature bar

So my question is:

What is the proper way to completely remove this extension, including its entry in the admin Feature bar? I assume there is still a reference in the database — if so, where should I delete it?

Any help would be greatly appreciated!

GreXXL

Dezibel1000 do you have access to your commandline (SSH)? If so the easiest way is to run composer remove subasteve/flarum-ext-mailing in your flarum installation directory.

Dezibel1000

no, I havn't any commandline access on this shared hosting account.

As posted before, I removed these entries from console.json and console.lock.
Further I found an entry in the database table "settings" for key "extension_enabled". Column val lists komma separated items (= the extensions used). I removed the item subasteve. But the "Mailing" item still appears in the left-hand Extension/Feature bar. More astonishing: the Disable <-> Enable Switch on the extension detail page "Mailing" is still working, although all the extension files "subasteve/flaarum-ext-mailing" have been removed. Also I delete the /storage/cache.

Any idea what else to do ?

GreXXL

Dezibel1000 you can try editing the composer.json and remove the extension from the file and then try to run an complete update via the extension manager. But as laid out in our documentation there are cases where you need access the commandline. You could also reach out to your hosting provider if he is able to run the commands for you.

KBExit

Dezibel1000 sounds to me you need to find another provider that would assist you 🙂

Dezibel1000

Hi there,

I found a solution that I’d like to share with you.

No need for an additional provider. As mentioned, I'm on a shared hosting account with no command line access and no Composer available.

Here’s what I did:

Download the full Flarum installation to your local machine (in my case: Ubuntu).

Run composer remove subasteve/flarum-ext-mailing locally in the project root.
Run composer require clarkwinkelmann/flarum-ext-mailing locally.
Zip the entire vendor folder and upload it to your shared hosting space.
Delete all files inside the vendor folder on the shared hosting server.
Extract your uploaded vendor.zip there.
Update composer.json (not composer.lock — although I'm not entirely sure whether this step is strictly required).

That's it — everything worked fine afterwards.

Thanks to Clark for providing us with an excellent mass mailing extension!

KBExit

Dezibel1000 band aid fix instead of a real solution... How are you keeping everything up to date? And what are you planning for Flarum 2.0 upgrade?

GreXXL

Dezibel1000 this is certainly possible, just make sure you are using the same PHP version like on your shared hosting otherwise you can run into issues if you have the wrong dependencies.

Dezibel1000

KBExit I get what you mean — and yes, Band-Aid was very successful, but I agree: on shared hosting this kind of workaround can only ever be a temporary solution and will make update procedures more complicated.