ellmann creative

What I’m trying to do is create a soft redirect from the offline page. I’m using it to mask a staging site, so I would like people to be redirected to the live site, but without invoking 3xx.

Except other e-mails from my site and/or domain are not affected — only the Wordfence e-mails are. For instance, Sucuri alerts (which we also use) come through without issue.

I’m tired of clicking “not spam”, been doing this for months.

Interestingly enough, Sucuri is using the e-mail we’ve set WordPress up with (Mail SMTP), while Wordfence seems to be using an imagined wordfence@ mailbox, which doesn’t exist on any of our hosts.

Notably, some of the sites are more susceptible to be affected than others, but we typically use the same hosting/service provider, and it’s a mixed bag — so I doubt hosting is the underlying cause (and if it is, it’s something that’s not exposed to us).

I’m actually more puzzled as to why a plugin that modifies the visuals of another, seems to involve itself with the core functionality of said plugin…

Unless you’re rebuilding the entire form, and then interfacing to CF7?

• This reply was modified 3 years, 8 months ago by ellmann creative.

Upon further investigation it has come to light that the issue is with “Smart Grid-Layout Design for Contact Form 7”.

Closing as resolved, and my apologies.

Also, I assume this is an issue and not intended behaviour? I would be extremely put off if you decided that silently discarding input was the right way to go forward…

I have just updated (mainly because I wasn’t at work and I blocked auto-update on the plugin in the interim), and from what I can see, the issue seems to be resolved.

Thank you.

That would be nice, thanks!

Since this is a website I’m setting up on a local dev server (I need something for plugin development for multisite in this instance), it’s obviously not a priority.

I just wanted to give you a heads-up — if WordPress recognises that the parent theme for the child is installed and fine (enough to display the child theme – which wouldn’t otherwise work), then maybe your plugin should recognise it too.

Here’s a screenshot to clarify how the situation looks in the network manager’s end:

https://i.postimg.cc/JhL3dbHG/Screen-Shot-2020-12-03-at-11-35-09.png

> share a screenshot

https://i.postimg.cc/QxFFgHtw/Screen-Shot-2020-12-03-at-11-27-05.png

The message is

“ThemeGrill Demo Importer – This plugin requires Official ThemeGrill Theme to be activated to work.”

> which child theme

A generic child theme:

/*
Theme Name: ColorMag Child
Theme URI: https://themegrill.com/themes/colormag/
Description: ColorMag Child, ellmann creative
Template: ColorMag
Author: ellmann creative
Author URI: https://ellmanncreative.com
Version: 1.0.0
Text Domain: colormag
*/

Great! Looking forward to being able to use both. ??

Note: the developer of “Enable Media Replace” is perfectly aware of this issue happening when your plugin is installed – they even have a FAQ page for this specific issue and your plugin. This issue has clearly been present for a long, long time.

• This reply was modified 4 years, 1 month ago by ellmann creative.

Both are latest versions:

> Enable Media Replace, version 3.4.2

> WooCommerce Product Attachment, version 1.6

As for any console output, I only have this:

Resource interpreted as Document but transferred with MIME type image/jpg: "{SITE}/wp-admin/upload.php?page=enable-media-replace%2Fenable-media-replace.php&action=media_replace&attachment_id=2095&_wpnonce={NONCE}".

This happens when both plugins are active, and I click on “Upload a new file”. Immediately after this, a download event occurs.

Note: the issue goes away immediately after disabling “WooCommerce Product Attachment”. I don’t even have to refresh the media page – it directly affects event handling, not page structure per se. I can keep Plugins and Media open in separate tabs, and as soon as I toggle the active state of your plugin, the bug is immediately affected. If I were to analyse the code, I’d start looking at anything that modifies the behaviour of upload handling.

• This reply was modified 4 years, 1 month ago by ellmann creative.

I have confirmed that this is indeed the case (conflict with Product Attachment for WooCommerce). Since this seems to be a bug on their end, I have reached out to their support to see if they can resolve the issue.

Do you have any other insight into why this is happening, which I could relay?

Thank you. ?? I just noticed this, because I hid that notification, it was bugging me too much.