[Plugin: Events Manager Extended] Released 4.0.0: prelimanary paypal support

  • Plugin Author Franky

    (@liedekef)


    13 years, 3 months ago

    Much has changed since the last version, about 20 feature requests were implemented for this one, so I bumped up the major version.
    Some of the most visible changes: access right management and paypal support for events. Now the payapl thingie is something that is still in early development, meaning: it works ok in my paypal sandbox, but I advise you to test in a sandbox as well first.

    For the rest, I quote from the changelog:

    * Feature: added option “show_ongoing” to [events_list], to indicate you want the scopes to include end dates (ongoing events) upon evaluation (like e.g. future events include events starting in the past, but ending in the future), or just the start date. Default: 1
    * Feature: you can now set the desired capability a user must have in order to do things (access right management). Use a plugin like “User Role Editor” to add/edit capabilities and roles.
    * Feature: eme_add_booking_form_filter and eme_delete_booking_form_filter filters added, so you can change the form html to your liking
    * Feature: split the function eme_display_single_event_shortcode into 2 parts, creating the function eme_display_single_event() that takes as single argument the event id, returning the html output for that event
    * Feature: recurrent events can now span multiple days
    * Feature: new shortcode [events_countdown], with one optional parameter (event ID): returns the number of days until the next event or the event specified
    * Feature: the shortcode [events_ical_link] now also accepts category as an option
    * Feature: locations now also can have categories on their own, and the “category”-option in [events_locations] will now show locations in those categories if the “eventful”-option is not set
    * Feature: locations now also have an author, and people can have the right to add, edit own or edit all locations
    * Feature: #_CATEGORIES for locations now returns the categories a location is in (as for events)
    * Feature: new option link_showperiod for shortcode [events_list]: if showperiod=daily and link_showperiod=1, then the shown days are links that will go to events for just that day
    * Feature: new option notcategory for shortcode [events_list]: works as the category option but serves to exclude categories
    * Feature: for conditional tags, I added 1 extra shortcode:
    #_IS_SINGLE_DAY (‘1’ if you’re viewing a single day, ‘0’ otherwise)
    * Feature: new shortcode #_CALENDAR_DAY, returning the day being viewed when viewing a specific day on the calendar
    * Feature: added filter to do own email obfuscating: eme_email_filter. If defined, the standard ascii obfuscating won’t take place and you can use your own
    filters, eg. from an obfuscating plugin, if you define it it functions.php:
    add_filter( ’eme_email_filter’, ‘c2c_obfuscate_email’ );
    * Feature: locations now also can point to an external url, as events can already
    * Feature: extra html headers can now be added, usefull for e.g. meta tags for facebook or seo
    * Feature: now you can delete events of an recurrence or the whole recurrence (no longer needed to take an event out of an recurrence before being able to delete just that event)
    * Feature: the permalink prefix for events and locations can now be changed in the settings page. After each change, you need to press save on the wordpress permalinks settings page before changes take effect.
    * Feature: the event or location permalink slug can now be changed manually, but for now the event/location ID remains required
    * Feature: the pending email body text can now also be changed per event
    * Feature: basic Paypal integration
    * Improvement: the RSVP form now always prefills the name and email if you’re logged in, if no WP membership is required you can change the values
    * Improvement: the no-events-message needs to be formatted by the user, not in the code using ul/li constructs
    * Improvement: for format: sometimes people want to give placeholders as options, but when using the shortcode inside another (e.g. when putting [events_list format=”#_EVENTNAME”] inside the “display single event” setting, the replacement of the placeholders happens too soon (placeholders get replaced first, before any other shortcode is interpreted). So we add the option that people can use “#OTHER” as prefix for any placeholder inside format (like #ESC works)
    * Improvement: “change registrations” now only shows the approved registrations, not pending ones
    * Improvement: in the events/locations admin section (add/edit), the categories are now sorted alphabetically
    * Improvement: #_NAME has been deprecated in favor of #_EVENTNAME
    * Improvement: #_LOCATION has been deprecated in favor of #_LOCATIONNAME
    * Improvement: #_PLAIN_CONTACTEMAIL has been deprecated in favor of the existing #_CONTACTEMAIL
    * Bugfix: AND categories for [events_list] were no longer working and resulted in all categories being used
    * Bugfix: some filtering fixes in admin panel
    * Bugfix: scope=this_week/next_week now takes the “start day of week” WP setting into account
    * Bugfix: cancelled registrations reported the wrong number of seats cancelled in the mail
    * Bugfix: an inappropriate mysql warning when updating a location without changing anything (wpdb->update returns 0 because 0 rows changed) has been eliminated
    * Bugfix: the names of users logged into WordPress were not pre-filled in the delete booking form
    * Bugfix: fixing a bug with quotes in category names
    * Bugfix: cancel emails were not being sent
    * Bugfix: #_IMAGEURL didn’t return the location image url for events (it worked ok for locations itself)
    * Bugfix: wordpress inserts canonical url’s since 3.0, but these point to the page url. Fixed so the correct canonical url is inserted for single locations or events.
    * Bugfix: get rid of some php notices in the event creation form

    https://www.ads-software.com/extend/plugins/events-manager-extended/

Viewing 4 replies - 1 through 4 (of 4 total)

  • Hi Franky, seeing as you’re taking this further and still following suit of EM, why not change the plugin name? It’s confusing now.

    Would love it if a WP plugin mod could step in here and weigh in an opinion. Given the amount of spare time I’ve dedicated to WP over the years it’d be appreciated.

    This is also a request from the authors you forked this plugin from and are still basing it on, and also for the benefit of the community. I still have people coming to me with EME issues to this day when trying my plugin and it’s not fair to them either it’s a waste of all our time.

    hope this resolves itself once and for all.

    Best,
    Marcus

    This is getting ridiculous.
    I also get e-mails weekly asking questions about EME.

    God knows I hate managing private questions publicly, but maybe this is a public question, since users are confused about the two plugin, and this is more even serious now that the’ve diverged.

    We never got an answer to the last email we sent you (October 2010), to find a way out of this mess TOGETHER.
    I cannot but think it is your interest to keep this confusion alive, and to keep “Events Manager Extended” as a name that implies EME extends EM (which is not quite accurate, just look at the code).

    I see malevolence here, and even if I am not responsible for the plugin anymore it’s not pleasant.

    It’d be nice to get a feedback.
    Davide

    Plugin Author Franky

    (@liedekef)

    Please stop bashing my head here: “malovelence” is a bit too harsh.
    I already explained in length why I forked and where the name came from (a simple request mail to wordpress admins with a suggestion and they accepted the name. I didn’t even wanted that name at the time, but since you guys were not responding at all on your own forum, I didn’t care).
    I already put this in my readme, upon your request: “Events Manager Extended (EME) is a fork (NOT an extension) of the older Events Manager (EM) version 2.2.2 (April 2010).”
    I’ll add a red warning on the EME settings page: “Please bare in mind that Events Manager Extended” is *NOT* an extension of “Events Manager”. For all support questions regarding “Events Manager Extended”, please go to this link.”
    But unless you know of an automagical way of transparently changing a plugin name and users also get the new plugin for the next update, I’m not wasting any more time on this. I also am working long hours on this plugin, without getting payed for it, so I can do better things with my time than discussing this over and over again.

    I still kindly request you change the name. Not making judgements, but you must admit it’s annoying to everyone.

    This is to prevent further confusion and conflict. Wouldn’t it be nicer if you were honored for the efforts in your own plugin name rather than this way?

    Been in this for so many years, never seen it come to this on another plugin and honestly don’t know why it has to here as well.

    FYI, what a coincidence but i just notice Event Espresso changed their plugin names on this repo, so you can too.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: Events Manager Extended] Released 4.0.0: prelimanary paypal support’ is closed to new replies.