deltafactory
Forum Replies Created
-
Quick follow-up:
If you’re using a newer PHP version, you may be having the same issue as detailed here: https://wordpress.org/support/topic/php-7-compatibility-229/
In that case, it’s not the use of [] but instead the & used before $this in lines 85, 86.
Forum: Plugins
In reply to: [Force HTTPS (SSL Redirect & Fix Insecure Content)] Force HTTPS not workingWhile the plugin converts calls to URL-generating functions and updates URLs in the post content, it won’t address URLs in widgets or template, nor external files.
On my own sites, I’ve added the content filter to the output buffer, which works seamlessly so far.
In your case, it may be one of those situations or a hard-coded URL in CSS/JS.
What version of PHP are you using? That line uses the “new” array notation [] introduced in v5.4. If you’re running an earlier version, that would explain the error.
On a separate note, I strongly suggest upgrading PHP versions. There are massive performance improvements, especially in v7.0+.
@wysija, is it possible for you to look into this issue?
Forum: Plugins
In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] MySQL errorNot sure if it’s related but someone had a similar issue last week and fixed it by reading my comments on this older post:
https://wordpress.org/support/topic/fatal-error-uncaught-pdoexception-sqlstatehy000/
Glad you found that helpful.
@wysija – when can this be patched in core? Others must be having this issue without reporting it.
@wysija, is there a timeline to address this? If not, please let me know so that I can make necessary adjustments.
@wysija/@mailpoet, is this something that you have addressed or can address in the near future?
Looks like the plugin needs to account for execution from the command line.
I’ll see if I can submit a patch…
@jack-kitterhing, would you happen to know which aspect is incompatible with EC2?
From my understanding, we customers purchase the raw computing time from AWS and should be able to do with it whatever we want. I know there are exceptions related to potential abuse, specifically outgoing email traffic. I would also understand regulated connection timeouts through ELB or CloudFront.
A long-running, self-contained process seems like a very common use-case. It’s a *weird* use of a single PHP request that may require special configuration of the PHP configuration, but that’s something that’s infinitely more configurable on EC2 than in other “managed” VPS environments primarily intended for web traffic.
BTW for my purposes I cloned the Cron Trigger class, added a DOING_CRON check, and made sure it loads prior to MailPoet’s implementation. It’s an ugly hack that hopefully won’t be needed for long.
I support this and have done something similar in my own work. However, WP definitely leads us to this as the correct way to do ajax.
Could you whitelist that one file to bypass your restrictions?
I wasn’t sure where it was beyond reading the code for the Event Manager plugin. 🙂
You’re very welcome.
I believe that the email action filters are part of the Mailpoet Premium plugin.
It’s not MailPoet’s job to find this out for you. They were pretty clear about the parameters they’re looking for. Nevertheless, it took only a few minutes to find a likely source of the difference.
In Events Manager’s custom post type declaration, the
exclude_from_searchoption looks like this:
'exclude_from_search' => !get_option('dbem_cp_events_search_results'),This corresponds with the prompt for “Include in WordPress Searches?” under the General Settings section of Page Options of Event Manager’s admin section. The visibility in MailPoet would be controlled by this setting, which is at the hands of the site’s administrator.
Hope that helps.
I see that the new release normalizes the emails through
validateSubscribersData()however when checking for existing users, the email value from the database is the one used via this call on line 376:Subscriber::selectMany(array('id', 'email'))->whereIn('email', $data)->findArray()The
strtolower()call needs to happen after that point, closer to when the email value is used as an array key.Thanks for your continued effort to address this.