Alan Fuller

1.3.20 is a very old version and include( and out of date version of) the Fremius library which may be the root of your issue as it does funly things, this was back when I thought I might create a premium version.

The current version does not contain any libraries.

The composer.json exists in the code as part of the build process and as required by www.ads-software.com build toold need to be included, but there is no link to the update process it is just there.

( I did notice that the WordPress SVN copy of composer.json is out of sync with the master on github, that will need fixing but it is not material as it is not used in WP )

syslog( LOG_INFO, esc_html( "Attempted user enumeration from " . $ip ) );

this will log to whatever your syslog is.

If you are testing make sure you are logged out as it deliberately doesn’t stop enumeration of authorised users.

I’m glad that seems to sort it .

@gpguy please start your own thread, this is considered best practice, for several reasons, your issue may look the same but very often the cause is different and the visibiliy on old threads is very limited to those that participated but a new thread will have many eyes looking.

Not sure closed plugins can be hijacked as the slug is never released.

Reporting on closed plugins 2 weeks before 6.6 is just noise. In other times it is a low priority information that a plugin will no longer be actively supported.

As mentioned, authors can not comment on closure reasons. The plugin repo does not report the reason for security reasons as explained and authors are expected to do the same.

The only calming measure is for the plugin authors to work with the plugins team to get the plugin re opened as soon as they can.

I know that does not help much, but the free plugin directory is managed in that way to be on the best interests of the community that uses the plugin contributions.

here is the issue, you can’t and shouldn’t acknowledge publicly.

Why, because if you acknowledge it is not a security issue this time, but next time it is a security issue and so you can’t acknowledge without giving hackers a heads up but deduction then not acknowledgement implies a security issue giving hackers heads up.

WordFence creating noise is a Wordfence issue.

If they are reporting things just because they are closed without a security CVE then they are reporting something that means nothing.

To be clear, when there is a new release plugin authors are emailed. If their email bounces their plugin is temporarily closed.

so yes this happens a lot about 2 weeks before a point release.

I am not a commiter, not related to Mailgun so I can’t help, you I just contributed a small fix once as it is open source software and they rightly acknowledged my contribution.

Personally I not longer use this plugin for different reasons and use one of the alternatives.

When a plugin is closed there can be many reasons, but at this time of year just before 6.6 release any plugin emails that bounce get their plugins closed. Whilst impossible to rule out other reasons such as security, the balance of probabilities is it is the commiter email bouncing. Ironic really.

I can’t really give you examples on how to code contributions but to contribute you can fork https://github.com/alanef/quick-event-manager and if you get a working solution that has some flexibility you can create a pull request to consider merging

The main function to look at is get_event_calendar_icon ( starts line 369 ) and around the else in 482 – warning it is complex so I’d recommend adding a filter and then applying your logic external to the plugin.

https://github.com/alanef/quick-event-manager/blob/master/legacy/qem-event-build-functions.php#L369

Hi thanks for using the free version.

The options show_end_time and show_end_date are premium only. It appears that the demo doesn’t disable these correctly when switching to free demo mode, mainly because the demo has to use the premium version.

In terms of the two spaces, this is simply because your text has two spaces on Eventbrite.

Unfortunately the code only uses the options avaiable on that page ( DMY YMD etc ) and does not use the system settings.

To do so would required code changes, either to add a filter so you can override with code or additional settings.

I have worked out what settings you have used = remove date icon style.

Oh can you describe of screen shot the settings because that is not default and with so many settings I need to try and track down what you have

By default the event date appears as in a ‘box’ like

https://fullworksplugins.com/event/multi-day-event-24/

• This reply was modified 3 months, 2 weeks ago by Alan Fuller.

Hi, is this in the list or event detail. A screen shot helps. You can link images from an image share service here.

If they are not arriving at all, not just going to spam, it is likley that your host does not support PHP email ( you can ask your host support )

There are plugins that help you debug WP email delivery this one would be OK https://en-gb.www.ads-software.com/plugins/email-log/ you should be able to see if they are actually going out or stuck.

Or if PHP email is not supported you can move to an SMTP plugin like https://www.ads-software.com/plugins/fluent-smtp/