Archive for the ‘New Versions’ Category

Release Update: Event Espresso 4.4.7.p Now Available

A maintenance release for Event Espresso 4 is now available. Event Espresso 4.4.7.p offers 5 fixes.

Please backup your website before making any changes.

Bugfixes for Event Espresso 4.4.7

  • Fix issue in upcoming events widget where short event titles don’t bump images down & big images can overflow
  • Fix issue where expired events cannot be viewed
  • Fix unlocalized strings and labels for the admin
  • Fix Undefined variable + Cannot modify header information warning when updating attendee registration form in admin
  • Add check for wpdb::set_sql_mode (only existed since WordPress 3.9.0)

Interested in contributing to the Event Espresso 4 project? Request access to our project on GitHub

For a complete history of updates and changes to EE4 and the EE4-compatible add-ons, see the change log for Event Espresso 4.
(more…)

Posted in News, New Versions | No Comments »

Release Update: Event Espresso 4.4.6.p Now Available

A maintenance release for Event Espresso 4 is now available. Event Espresso 4.4.6.p offers 10 fixes and 3 enhancements.

Please backup your website before making any changes.

Bugfixes for Event Espresso 4.4.6

  • Fix datetimes being based on UTC rather than local time when being displayed on the front end
  • Fix events with a status of  ‘Cancelled’ still allowing registrations
  • Fix ESPRESSO_EVENTS shortcode where pagination stops working if used on the ‘Front Page’
  • Fix issue with prices with commas
  • Fix event category archives
  • Fix events with no limit set on a datetime importing as sold out
  • Fix error when attempting to remove a trashed registrant
  • Fix ‘Notice: Undefined index: test_transactions in /event-espresso-core-reg/modules/gateways/Paypal_Pro/EE_Paypal_Pro.class.php on line 781’
  • Fix “Allow Payment-retry for Pending and Deferred Payments?”
  • Fix STRICT_ALL_TABLES issue for WordPress 4.1

Enhancements for Event Espresso 4.4.6

  • Add a whole whack of filters to control displayed text within the ticket selector
  • Merge GitHub Pull Request #46: Updated Thank You page header to be consistent (props nickrouty)
  • Merge GitHub Pull Request #45: Removed line that isn’t applicable to Ticket Selector table columns (props nickrouty)

Interested in contributing to the Event Espresso 4 project? Request access to our project on GitHub

For a complete history of updates and changes to EE4 and the EE4-compatible add-ons, see the change log for Event Espresso 4.
(more…)

Posted in News, New Versions | No Comments »

Release Update: Event Espresso 4.4.5.p Now Available

A maintenance release for Event Espresso 4 is now available. Event Espresso 4.4.5.p offers 13 fixes and 2 enhancements.

Please backup your website before making any changes.

Bugfixes for Event Espresso 4.4.5

  • Fix issue where multiple required tickets causes some ticket options to become sold out
  • Fix datetimes being based on UTC rather than local time when being displayed on the front end
  • Fix Upcoming events widget does not display events that are currently active
  • Fix issue where the visibility of password protected on an event allowed registration through event listing page
  • Clean up translation strings
  • Fix untranslatable messaging verbiage
  • Fix issue where an extra space created a duplicate language domain entry for “In order to process your registration” message in SPCO
  • Fix the “Display expired events” options in the Template settings
  • Fix ability to remove price modifiers
  • Fix issue where events with no dates became unusable due to warning
  • Fix registration ticket price for tickets that get added to a secondary datetime
  • Fix Default Registration Status default setting option
  • Convert state number to state name for Authorize.net receipt

Enhancements for Event Espresso 4.4.5

  • Merge Pull Request: Added echo/return capabilities to template tags (ht: jonathan-dejong)
  • Merge GitHub Pull Request #42: Added markup around ticket info (ht: jonathan-dejong)

Interested in contributing to the Event Espresso 4 project? Request access to our project on GitHub

For a complete history of updates and changes to EE4 and the EE4-compatible add-ons, see the change log for Event Espresso 4.
(more…)

Posted in News, New Versions | 2 Comments »

Release Update: Event Espresso 4.4.3.p

A maintenance release for Event Espresso 4 is now available. Event Espresso 4.4.3.p offers 3 fixes and 1 enhancement.

Please backup your website before making any changes.

Bugfixes for Event Espresso 4.4.3

  • Error when auto-updating
  • Database error in front-end category shortcode page while in maintenance mode
  • Undefined property (slug) notice that shows on plugin list table

Enhancements for Event Espresso 4.4.3

  • Enabled Payment Declined (Event Admin context) by default
For a complete history of updates and changes to EE4 and the EE4-compatible add-ons, see the change log for Event Espresso 4.

Updating to Event Espresso 4.4.3

One-click updates are available via the WordPress Plugins page within the WP dashboard to members who have activated their support license key. The support license key can be found on your Event Espresso account page and it is activated through the General Settings page for Event Espresso within your WordPress admin (WP dashboard).

Be sure to backup your WordPress site. Then login to your WordPress admin and click on Plugins in the WordPress admin menus. Locate Event Espresso within the list of plugins and click on Update Now.

You can also manually update your Event Espresso software. Here is information on how to manually update Event Espresso via SFTP or FTP.

What Happened to Event Espresso 4.4.1 and 4.4.2?

These versions were released within a few days of each other. Here is the changelog for Event Espresso 4.4.1 and the changelog for Event Espresso 4.4.2.

Pro-tip
Need to see more events or registrations per page in your WordPress dashboard?

Try clicking on the Screen Options tab in the top right corner of the events overview screen or registration overview screen and then adjust the pagination number and save changes. Here is an example: Increase the number of events shown in the events overview screen

Thanks for being a member of Event Espresso!

Posted in News, New Versions | 2 Comments »

Raising the PHP Requirements for Event Espresso 4

Here at Event Espresso, our mission has always been to empower business and organization leaders with the event registration, ticketing and management tools that maximize the success of their events. While our products are constantly improving as a result of that mission, we must also continue to evaluate systems our products are built with to ensure they contribute to this mission as well. One of these dependencies is the usage of the PHP programming language.

Since the release of Event Espresso 4, back in January 2014, we have made it clear on the Requirements page that EE4 requires at least PHP 5.3. As of EE version 4.4, we will no longer support PHP 5.2. If you try activating EE 4.4 on a site running on PHP 5.2 it will simply deactivate and display a minimum PHP version is required message. This is done on purpose to prevent serious issues on your site. If you wish to continue using EE 4.4, you will have to upgrade your server to PHP 5.3 or later. If you are unable to upgrade to PHP 5.3+ right away (maybe your host is slow to respond) you can continue to use EE 4.3.1.

Please note that the PHP 5.3 series will enter an end of life cycle and receive only critical fixes as of August 14, 2014. All users of PHP are encouraged to upgrade to PHP 5.4. PHP 5.3.29 is recommended for those wishing to remain on the 5.3 series.
Create an account now and download Event Espresso 4 Decaf for free.

Why are we raising the PHP requirements for EE4?

Dropping support for PHP 5.2 was a decision we did not make lightly. In fact, we tried to delay it as long as possible. Here are the three primary reasons prompting this decision:

  1. Security
    PHP 5.2 is a dead release. It became end-of-life on January 6th, 2011 when the final version, PHP 5.2.17, was released. As the PHP website reads on that page:

    If you are using these releases, you are strongly urged to upgrade to a current version, as using older versions may expose you to security vulnerabilities and bugs that have been fixed in more recent versions of PHP.

    This is exactly the case with PHP 5.2, a version of PHP which is end of life for over 3 years. As a matter of fact, just a mere days after it became end of life a major security flaw was detected. It was fixed in PHP 5.3 but not in PHP 5.2. If you are using PHP 5.2, and your hosting provider has not patched this version, you are exposed to known security threats which are being used to attack web sites. The nature of these attacks means that your server’s firewall and/or a security component (like Admin Tools Professional) cannot protect your site. If you are using an un-patched version of PHP 5.2 your site will be hacked. The question is not if, but when. So, using PHP 5.2 may hurt your site’s security.

  2. More Efficient Code
    PHP 5.2 lacks several features necessary for modern software development, like late static binding. To cut a long story short, if we kept on supporting PHP 5.2 we could no longer maintain our software in a way that is consistent with our commitment to providing up-to-date and easy to use software. We’d be stuck in the Stone Age until we reached a point that we could no longer provide new features and updates. So, using PHP 5.2 doesn’t allow efficient software development.
  3. Quicker Feature Development
    One of the major factors in the longer release times of our EE4 products has not only been extra development time working around PHP 5.2 deficiencies, but also having to test on PHP 5.2. Eliminating support for PHP 5.2 helps us speed up release times. Therefore allowing us to develop and test new features at a much faster rate.

Why now?

Basically, we chose now as the time for dropping support because in the past year most major hosts have begun moving their customers over to newer PHP versions and are dropping support for PHP5.2. We delayed dropping support ourselves because we wanted to ensure that most of our existing customers are able to transition to newer versions of PHP fairly easily. Also, in the past year WordPress has made a number of fixes in its releases to address minor compatibility issues with PHP 5.4 and 5.5 that ensure it is fully compatible with the most recent versions of PHP.

Will my WordPress website stop working?

Upgrading your WordPress site to a new PHP version will not break the site unless you have a plugin/theme that uses a deprecated PHP function/method. Themes are less likely to have that, but plugins might. You will have to notify the plugin author of the affected plugin.

Customers can always download and install EE 4.3.2, from the pre-release channel within your account, which is compatible with PHP 5.2 until they can find a better web host.

Keep in mind WP will support sites up to PHP 5.4 (and even PHP 5.5 as of WP 3.9). So compatibility with WP is not a problem.

The only issue our customers might see in some circumstances is if they have WP_DEBUG on, plugins coded in a PHP 5.2 environment (or even PHP 5.3) might have things that throw warnings in PHP 5.4+ , but again that does not break sites if WP_DEBUG is off (which in a production environment SHOULD be off).

What if my host is still on PHP 5.2?

All the major hosts (Dreamhost, Bluehost, Hostgator, etc…) have PHP 5.3 by default.

And if there is a minor host where PHP 5.2 is the best you can have, then what’s the point with signing with a smaller and lesser known company if they cannot provide better services than big ones?

There are hosts which still offer PHP 5.2 by default but do support PHP 5.3 or 5.4 as an option. On these hosts you can ask them for the proper way to upgrade to PHP 5.3. Usually it’s a configuration option in your site’s control panel or in your .htaccess.

Even worse, there are still hosts which do not offer you any way to use PHP 5.3 or later. These hosts must be avoided at all cost. It means that the hosting company doesn’t care about investing the minimal amount of time required to properly setup their machines and ensure your security. Do you really want to trust them with your site? Would you tolerate a catering company serving stale food at your event? It’s the same question. If you’re stuck on such a host we strongly recommending moving to a decent hosting company. We have compiled a short list of quality hosts you might want to consider. Here you go, in no particular order:

TL; DR

As of EE 4.4, we are no longer supporting PHP version 5.2. If you cannot update to PHP version 5.2, then you cannot use EE 4.4. If your hosting company is still on PHP 5.2, you will need to have them update your server to PHP version 5.3 or greater. If they refuse, you should seriously consider switching to a different hosting provider.

Customers can always download and install EE 4.3.2, from the pre-release channel within your account, which is compatible with PHP 5.2 until they can find a better web host.

Why drop support for PHP 5.2?

  1. Security
  2. Ability to write more efficient code
  3. Quicker development of new features

Will my WordPress website still work?
Yes, your site will still work, as long as your WordPress theme and plugins are compatible with PHP 5.3+.

Host won’t update?
Move to a trusted hosting provider.

 

Tags: , ,
Posted in News, Development, New Versions | No Comments »

Major Update: Event Espresso 4.3

This release brings many improvements to existing core features and a few new features, such as duplicate events, iCal integration, batch email/newsletter system, registration form and payment system optimizations.

An Important Calendar Update is Available!
If you use the 1-click update feature, please be sure to update the EE4 Calendar to 3.1 BEFORE updating the EE4 core plugin.

New Features

  • Duplicate Event
  • Ticket Required Option
  • Added iCal Integration
  • Drag-n-drop Answer Values
  • Order Questions by Question Group
  • Question Editor Style Changes (thanks to Matt Van Andel)
  • Re-order Datetimes in Ticket Editor and Single Page Checkout
  • New Hooks and Filters for Developers Added to the Registration Process

Fixes

  • Gateways
  • Messages System
  • Migration Issues
  • Miscellaneous Spelling Errors

ImageSupport for “Ticket Bundles” & “Graduated Pricing”
Starting with Event Espresso 4.3 you can offer discount pricing and/or graduated pricing based on ticket quantities.

  • Ticket Bundles
    Can be used to set a per ticket price, based on a pre-defined quantity of tickets. This article shows how to create a ticket bundle where you can set a lower price per ticket when purchased in a bundle.
  • Graduated Ticket Pricing
    Can be used to set a per ticket price, based on a quantity range of tickets, similar to a tiered pricing structure. This article shows how to set graduated ticket pricing where you can set a lower price per ticket for larger quantity ticket purchases.

Messages System Changes/Fixes
We’ve improved the Custom Template System, added a “Newsletter” Message Type for sending batch emails, and made a couple of minor updates.

  • Message Type – Newsletter message type
  • Messages Admin – Updated to implement a new Custom Template creation/edit process
  • Event Editor – Modify Messages metabox in event editor to use new custom template system
  • Messages System – Default ‘From’ Email shortcode changed to [CO_FORMATTED_EMAIL]

acf-home-panel-fieldsAdvanced Custom Fields Integration
Fully customize WordPress edit screens with powerful custom fields, using the Advanced Custom Fields plugin for WordPress. We’ve added several new hooks and filters throughout the Single Page Checkout system to give developers the ability to integrate with this awesome plugin.

Payment Gateway Fixes
This time around we’ve spent some time making sure the payment processing features work better, faster, and are easier to understand for your customers. We’ve also added better support for tracking partial payments.

  • Send address fields to Mijireh
  • Show failed payments in payment response
  • Thank You page now uses the WordPress Heartbeat API to automatically display payment status updates
  • Fix for Single Page Checkout so it displays the correct amount owed based on when a payment has already been entered into the system

Posted in News, New Versions | 6 Comments »

Release Update: Event Espresso 4.2.8.p

A maintenance release for Event Espresso 4 is now available. Event Espresso 4.2.8.p offers 4 fixes and 1 enhancement.

Please backup your WordPress before making any changes.

Bugfixes

  • Fix issue with ticket pricing being retrieved from PHP session
  • Fix issue with datetimes missing assigned tickets
  • Fix typos in language domain
  • Fix compatibility issue with WordPress 4.0

Enhancements

  • Translate month names in invoice payment gateway
For a complete history of the updates and changes to EE4 and the EE4-compatible add-ons, see the entire EE4 Changelog.

Posted in News, New Versions | 2 Comments »

Release Update: Event Espresso 4.2.7.p

A maintenance release for Event Espresso 4 is now available. Event Espresso 4.2.7.p offers 14 fixes.

Please backup your WordPress before making any changes.

Bugfixes

  • Prevent duplication of venues when migrating from Event Espresso 3
  • Show the current value when changes are saved through the default price type editor
  • Restore the [EVENT_LIST] messages shortcode for the [ATTENDEE_LIST]
  • Fix styling issue with dropdown menus in the Add New Registration screen
  • Fix undeclared variable in EE_Shortcodes::_validate_list_requirements()
  • Restore the ability for the messages system to display information from system questions
  • Correct a variable name to clear a PHP warning in EE_Event_List_Shortcodes.lib.php
  • Fix infinite loop issue related to event excerpts
  • Fix transaction time for offsite payments gateways (e.g. Mijireh, PayPal) so they are recorded with the correct timezone
  • Fix email links used by the messages system
  • Restore the [EVENT_AUTHOR_EMAIL] messages shortcode for the [EVENT_LIST]
  • Adjust saving of primary registrant information so this information is only saved to the primary attendee record
  • Fix insecure warning caused by Google maps loading over http while on an https page
  • Fix error from missing help tab for the Check-In Records screen
For a complete history of the updates and changes to Event Espresso 4 and the EE4-compatible add-ons, see the entire EE4 Changelog.

Posted in News, New Versions, Versions | No Comments »

Release Update: Event Espresso 4.2.6.p

An update for Event Espresso 4 is now available. Event Espresso 4.2.6.p offers one enhancement and 13 fixes.

Please backup your WordPress before making any changes.

Enhancements

  • Add option to show events from all categories in the Upcoming Events widget

Bugfixes

  • Upcoming events widget formatting, remove extra line breaks and spacing, defaults of false not selecting
  • Preview button not showing for regular WordPress post-types
  • Logo Sizes in Order Confirmation PDF
  • Clarifying that the “skip migrations” = “reset database and delete old data”
  • indexOf(s) is not a function
  • Event Access Information under Ticket Details shows “Remaining” but that heading no longer exists
  • Fix date display in content-espresso_events-header.php to allow for translation
  • Themes that use “get_the_excerpt()” instead of “the_excerpt()” are missing EE content.
    Please note many of the headings in the event templates of prior versions have been removed as part of the work done in this ticket
  • Move to Trash Link in Venues Editor allows you to Delete Locked Venues
  • Arabica 2014 – change category icon from “tags” to “category”
  • EE4 Core 4.1 DMS crashing during events_Question_group stage
  • Fix error on sorting venues by ID in venue list table
  • Fix errors getting hidden by try catch block
For a complete history of the updates and changes to EE4 and the EE4-compatible add-ons, see the entire EE4 Changelog.

Posted in News, New Versions, Versions | 2 Comments »

Event Espresso 4 (Beta) Officially Released

2014-02-10_00-10-21Event Espresso 4 (Beta) is now available! This is really exciting and there is a lot we’d like to share with you!

How do I get access to EE4?

EE4 is currently available to the public for sale and is released to Event Espresso 3 users for FREE. If you purchase a EE3 Support License you will also have free access to EE4.

You can even launch your own demo site for EE4 in just a few minutes. Click here to get started with your EE4 test drive site!

Attention Bloggers – Wanna get your hands on a free copy of EE4 to review or want to do an interview? Please reach out to us on Twitter, Facebook, or contact us.
Create an account now and download Event Espresso 4 Decaf for free.

 

How is EE4 different than EE3?

2014-02-10_00-06-40EE4 is very different from EE3 in more ways than we can probably list/describe/remember—so you’re going to want to check it out. In general there are several important changes to the EE4: features, user interface, data structure,  coding method and price.

Features

EE3 and EE4 have different feature sets; some features are available in EE4 that have never been available in EE3:

….and 30+ more!

User Interface

2014-02-10_00-07-23The user interface has been rebuilt to follow the new WordPress 3.8+ standard. We’ve rebuilt all the pages, added new icons, added mobile browser compatibility, optimized notifications and much more. We believe that EE4 is more elegant, easier to use and more powerful all at the same time.

Data Structure

The data structure has changed so that some event data is now custom post types (CPTs). CPTs make event-related data more available to standard WordPress functions and themes. This will make Event Espresso more accessible for both back-end (core) developers and front-end (theme) designers.

Coding Method

The coding method has changed from procedural coding to more heavily object-oriented programming. That means there are more files, but less code to do more advanced things. Experienced developers should appreciate all the work that went into this change. We believe it makes our event registration more powerful and robust, helping make your event registration experience better.

We really think you’ll like what you see—especially as you get used to EE4 and realize all the new types of events it can power. We will continue making improvements in all of these areas and look forward for what is to come.

Price

While “in Beta”, Event Espresso 4 will be discounted significantly (approx. 50%). As the EE4 matures to a “stable” development status, the price will rise. Those who purchase at this discounted rate are still entitled to 12 months of support and upgrades.

 

Screen Shots

Here are a few screen shots to show off some of the awesome new features!

2014-02-10_00-13-43 2014-02-10_00-23-26 2014-02-10_00-07-53
2014-02-10_00-18-37 2014-02-10_00-18-12 ticket_editor
2014-02-10_00-19-15 2014-02-10_00-16-37 2014-02-10_00-17-31

Why did we spend so much time and money building Event Espresso 4?

We have sought feedback from you, the thousands of event managers and developers who rely on Event Espresso to make their events successful. Your feedback has focused on one general theme. You want Event Espresso to do more and be more stable.

It is difficult to add more features to a system that was initially designed to for a more narrow focus. As we continue to add those new features Event Espresso has become more difficult to use, setup and/or customize. The added features has also made the core code more complex and less reliable, thus the increase in bugs.

As your requirements for Event Espresso have evolved (and continue to evolve), it became clear that parts of the code have gotten too complex and must be refactored in order to support new ideas. The longer we delayed refactoring Event Espresso, and the more code is written for EE3, the more difficult it becomes to refactor Event Espresso to meet your needs today and in the future.

In short, we spent a lot of money and several years building Event Espresso 4 because we wanted to help you and your events be more successful.

 

Why did it take so long to build Event Espresso 4?

When we started building version 3.2, we didn’t anticipate that it would be such a major change. However, as we started to refactor one system we saw it necessary (and better timing) to refactor other systems. Event Espresso 4 introduces several major changes including:

  • A new user interface
  • A single page checkout
  • A new messages system
  • New transaction management
  • A new pricing management system
  • A new taxes management system
  • Custom post types for events, venues, and contacts
  • Changing our programming approach to object-oriented programming
  • and much more!

All those systems are quite interconnected and complex, so updating it took a lot of time and resources. We’re just as frustrated EE4 took as long to release as you, but we feel this decision will be the best for you in the long-run. We’re confident that we (and other developers) can build really great event registration websites on EE4 for a very long time to come.

 

What’s coming next in Event Espresso 4?

We view our roadmap in two ways: short(er)-term projects and long(er)-term projects. Our roadmap is subject to change at any time.

Our short(er)-term projects include:

  • Making EE3 add-ons compatible with EE4.
  • Promotion codes.
  • Refactoring gateways.

Our Long(er)-term projects include:

  • Integration with third-party plugins and services.
  • Advanced messages functionality.
  • Advanced registration form functionality.
  • New add-ons.
  • Event themes.
  • Continued code optimization.

As always, you’re invited to participate as developers or sponsors.

 

What’s the plan for Event Espresso 3?

EE4 beta begins the official process of phasing out EE3. Going forward, we will focus new feature development resources on EE4 and only maintenance resources to EE3. As the EE4 feature set (including add-ons) exceeds those that are currently available with EE3 we will no longer sell or support EE3.

Those who purchase a EE3 support license  also have access to the core EE4 files and we recommend that they evaluate EE4 to see if will meet your needs at this time. We have provided tools to use EE3 data in EE4 which can help you start using EE4 sooner.

The future of event registration and ticketing is with Event Espresso 4 and we hope you’ll join us today for that amazing journey.

 

Can I Use EE4 instead of EE3?

Depending on your situation you might (or might not) want to replace EE3 with EE4. In general, our recommendation hinges on: what features you require, and whether you want to use your EE3 data in EE4.

Some features are not available in EE4 that are available in EE3:

  • Coupon/Discount codes
  • Wait lists
  • Staff manager
  • Support for EE3 add-ons (see below)
None of the EE3 add-ons are compatible with EE4 at this time (but they are on our short-list). You will need to make the determination about which features your project requires and which Event Espresso version will meet your needs.

Using EE3 Data in EE4

Event Espresso 4 is ready to accept unaltered data that has been prepared by Event Espresso 3.1.36 (or greater). If you’ve not modified your EE3 database structure then you can migrate your data from EE3 to EE4. If you have modified your database structure, the migration scripts may not function properly (see below).

As a good practice, please backup your website database before migrating.

When to migrate EE3 data to EE4:

If you are using  Event Espresso version  3.1.36 (or greater) without customization that changes the data structure (e.g. additional database tables, columns, etc.) you can migrate your database from EE3 to EE4.

As a good practice, please backup your website database before migrating.

When NOT to migrate EE3 data to EE4:

We recommend NOT migrating your EE3 data to EE4 if you: have customized Event Espresso database tables or columns that weren’t included with EE3 OR are using EE3 on a multi-site installation of WordPress.

 

What is the development status of Event Espresso 4?

After years of development and months of testing, we have finished adding features (to this version) and all major bugs have been resolved. We do expect you to be able to use EE4 as if it were a stable product, with the exception that additional bugs may be identified through more extensive testing with your specific use-case. Please report any suspected bugs to the support forums. For a short period, we will be focused on fixing bugs that are found by users and that can be verified by our support staff, then release patches ASAP. After EE4 is released as a “non-Beta” product we will commence work on our development road map.

 

Reporting Bugs

We have spent, literally, thousands of hours developing, testing and debugging EE4, but undoubtedly some of you may encounter issues with EE4 while testing it in your given use-case, the plugins and themes you use, etc. Please report any unexpected behavior, error messages, or bugs to the support forums so we can keep all the requests organized and fixed as soon as possible. Please create a new thread for each issue so that it can be addressed specifically. Otherwise it might confused with other issues or missed among a lengthy discussion.

As a good practice, please backup your website database before using EE4 on the same website where you are using EE3 and before migrating.

 

Questions or Comments? Tell us what you think

Event Espresso 4 is a big step forward in the functionality and power of WordPress events plugins. We really think you’ll like what EE4 is now, what you can do with it now, and what it will become. Launch your own test drive of Event Espresso 4 in minutes and let us know what you’re thinking.

Posted in Home Page, News, New Versions, WordPress Plugins, Beta, EE4 | 53 Comments »

Do NOT follow this link or you will be banned from the site!
[for="input_96_5_3"]
[for="input_96_5_3"]
[gravityform id=96 title=false description=false]
  • This field is for validation purposes and should be left unchanged.
[i]
[i]
[gravityform id=69 title=false description=false]
  • This field is for validation purposes and should be left unchanged.