Delete permanently seems to be missing from trash section.

We are experiencing this issue as well. Flamingo has logged over 49000 spam entries for a client site we are managing. We are also experiencing the very slow form processing redirect as noted in another submission to this forum.

We need to remove the over 49,000 spam entries from Flamingo.

Please let us know how we can identify the information in the database for ALL Flamingo entries so we can clean up this mess.

The same problem here. It is impossible to permently delete the entries. I will wait until this is solved before carry on evaluating this plugin. I do need to remove all the test forms before I can go live.

Same problem here – my “Empty Trash” button has vanished (possibly since CF7 updated to 4.1.2 about a week ago).

Also I’ve just noticed I cannot mark anything as “Not Spam” either.

Have tried deactivating, deleting and reinstalling Flamingo (not CF7 though), and still the same.

??

Can this issue please be resolved?

We need to clean up a database for a client ASAP so we can move it to a development environment- all the bloat in the DB from the 49,000 spam entries has pushed the db file to over 200mb.

If at all possible PLEASE SEND mysql queries so we can clean this up, or at least fix so we can trash entries.

A temp fix.

So this will change obviously depending on what you named your DB. Log in to your DB manager and run this query from the **_posts table.

DELETE FROM wp_2posts
WHERE post_status='flamingo-spam';

Replace “wp_2posts” with whatever you have named your DB but those are the tables you want to drop.

The same should work for trash although I only tested the spam one. It is probably a good idea to run a quick backup on your DB before running these.

DELETE FROM wp_2posts
WHERE post_status='trash';

To the developers of the Flamingo plugin,

The Flamingo Plugin does not give the option to “delete permanently” when emptying out the “Trash” on the UI of the plugin. As the others stated, it use to be there, but when I updated the plugin to version 1.2, it is no longer there!

I did the temporary solution according to mirandarma and purged all the old inbound messages in the Flamingo Trash area. Can someone look into this, please!

This is what I have under the hood:

• WordPress 4.2.2
• Theme is Education Pro Theme utilizing the Genesis framework by StudioPress

Plugins:

• Akismet Version 3.1.1 (ACTIVE)
• Back Up Buddy Version 6.0.1.0 (ACTIVE)
• Capcha Code Version 2.5.3 (ACTIVE)
• Contact Form 7 Version 4.1.2 (ACTIVE)
• WP Download Manager Version 2.7.92 (ACTIVE)
• Flamingo Version 1.2 (ACTIVE)
• Genesis eNews Version 1.4.1 (ACTIVE)
• Genesis Responsive Slider Version 0.9.2 (ACTIVE)
• jQuery Updater Version 2.1.4 (ACTIVE)
• Login LockDown Version v1.6.1 (ACTIVE)
• Really Simple CAPTCHA Version 1.8.0.1 (ACTIVE)
• Schema Creator by Raven Version 1.050 (ACTIVE)
• Theme Check Version 20141222.1 (ACTIVE)
• Ultimate Coming Soon Page Version 1.14.3 (ACTIVE)
• WordPress Importer Version 0.6.1 (ACTIVE)
• WordPress SEO Version 2.1.1 (ACTIVE)
• WP-Activity Version 2.0 (ACTIVE)
• WP-Edit Version 3.1 (ACTIVE)
• WP Super Cache Version 1.4.4 (ACTIVE)

I would greatly appreciate it!

Kind Regards,
David

Someone knows the point and the change to do so that we can re-delete messages in the trash and spam?

@loganless

I am sorry I don’t know what you are asking.

I posted kind of pain in the butt manual delete instructions up a few posts if that what is what you are asking.

I’m not sure why this bug exists or why the plug-in hasn’t been updated in so long, but here is the fix:

NOTE: This was performed on the latest WordPress v4.2.2, with Flamingo Version 1.2 installed.

File to fix: class-inbound-messages-list-table.php
File location: /wp-content/plugins/flamingo/admin/includes/

First section to fix:

CHANGE THIS:

if ( ! empty( $_REQUEST['post_status'] ) ) {
			if ( $_REQUEST['post_status'] == 'trash' ) {
				$args['post_status'] = 'trash';
				$this->is_trash = true;
			} elseif ( $_REQUEST['post_status'] == 'spam' ) {
				$args['post_status'] = Flamingo_Inbound_Message::spam_status;
				$this->is_spam = true;
			}
		}

TO THIS:

if ( ! empty( $_REQUEST['post_status'] ) ) {
			if ( $_REQUEST['post_status'] == 'trash' ) {
				$args['post_status'] = 'trash';
			} elseif ( $_REQUEST['post_status'] == 'spam' ) {
				$args['post_status'] = Flamingo_Inbound_Message::spam_status;
			}
		}

Second section to fix (in the same file):

FIND THIS:

function get_bulk_actions() {
		$actions = array();

ADD THE FOLLOWING CODE TO CHANGE TO:

function get_bulk_actions() {

		if ( ! empty( $_REQUEST['post_status'] ) ) {
			if ( $_REQUEST['post_status'] == 'trash' ) {
				$is_trash = true;
			} elseif ( $_REQUEST['post_status'] == 'spam' ) {
				$is_spam = true;
			}
		}

		$actions = array();

Hi duey.d,
sorry but your fix seems doesn’t works.
I still can’t delete the message in the trash or the spam message in the spam section.

I went and added a few lines of sql to clear out the postmeta table also, you need to figure out what your flamingo adds. That said, I really would like a button….

DELETE FROM wp_posts WHERE meta_status='flamingo-spam';
DELETE FROM wp_postmeta WHERE meta_key='_from';
DELETE FROM wp_postmeta WHERE meta_key='_from_name';
DELETE FROM wp_postmeta WHERE meta_key='_from_email';
...

@jamiefehr

me too. The instruction of duey.d seems doesn’t work. I’m searching a temporary solution, changing the code of the plugin, hoping it will be updated.

@loganless: what version of wordpress & flamingo are you running?

@jamiefehr (and anyone else): can you confirm whether my code above fixed your problem?

EDIT: My code above fixed the problem indicated in this thread, on a site running the WP version and Flamingo version I mentioned previously.

@duey.d

Contact Form 7
Version 4.2

Flamingo
Version 1.2

WordPress
Version 4.2.2

EDIT:
2 screeshots of the trash page (wp-admin/admin.php?page=flamingo_inbound&post_status=trash):
https://s28.postimg.org/h2wx6gwv1/screen.jpg
https://s3.postimg.org/6w01nq2yb/screen2.jpg

@loganless: Which WordPress version?

Also, did you make sure you edited the correct file in the correct location/folder?

My fix is based on an English install of WordPress, and I’m not familiar with the structure of files in an Italian (or another language) install, and not sure if that might have affect anything.

Maybe other members can confirm whether my fix works for them.