eventespresso / eea-beaver-builder Goto Github PK

A Beaver Builder integration for Event Espresso 4

License: GNU General Public License v2.0

PHP 89.82% JavaScript 3.40% CSS 4.55% Shell 2.11% Hack 0.12%

beaver-builder beaver-themer event-espresso wordpress customizer events

eea-beaver-builder's Introduction

Event Espresso Beaver Builder Add-on

This plugin adds Event Espresso 4 event display and ticketing options to the Beaver Builder page builder plugin for WordPress. Currently, this version of the plugin adds a customizable event ticket selector and events list to Beaver Builder, while adding support for the Event Espresso 4 Grid View and Table View add-ons if either is installed.

Feature Videos:

Ticket Selector Video
Events List Video
Grid View (Now Available)
Table View (Now Available)

Be sure to check out the Beaver Builder Child Theme for Event Espresso.

Note, usage support is not provided here. Please read the entire contents of this document before posting any issues. If we encounter issues that give evidence of this document not having been read the issue will be closed.

Some Links
Support	Free support for this add-on is NOT provided through this repository. Please create a Github issue if you have questions or discover bugs or plugin incompatibilities.
Paid Support	Support tokens are available if you happen to get stuck.
Reporting Issues	Please create a Github issue if you have questions or discover bugs or plugin incompatibilities.
Newsletter	Be the first to know when we ship new features ... signup here.
Community Chat	Join a real-time community chat group for professionals that are leading the way in events from event management, event technology and event marketing to work-life balance. Join the Discussion →

Developers

This is the full version of the add-on and provides its full feature set. The repository is provided to assist you with evaluating whether it will solve your use-case.

We ask if you are using this to provide a solution for clients that you (or your client) purchase a support license for Event Espresso 4.

No Usage Support is provided in this repository.

Add-on Releases and Development

We follow a set pattern for releases and development of all our official add-ons:

Active development for new features happens on a FET-{ticket-number}-{brief-description} branch. We continually merge master into the feature branch while it's in development. Once it's complete, then testing is done on it and it's merged back to master ready for release.
Bug fixes are done on a BUG-{ticket-number}-{brief-description} branch. Same methodology is used as with feature branches.
Master is technically always production ready and release ready but may not be equal to what the current stable release is for.
When we do an official release of an add-on, the current master is tagged and the release is the zip for that tag.

Testing

For all testers of this add-on, please take note of the following when reporting issues.

There is a difference between a feature and a bug, we consider a bug is something that reveals brokenness in intended functionality. A feature, is something beyond intended functionality. To help determine the difference, think about your issue like this, "I know A does C, however I wish it did D." If you find yourself saying that, its a feature. This repository is not the place to suggest a new feature UNLESS you've already got a pull request to implement it (see pull requests section below). Info on sponsoring new features can be found here. If you aren't sure whether something is a feature or bug feel free to post the issue - however we give priority to bug issues here.
UI/UX issues may be considered a bug but not if it requires a major change in design. Feel free to report things you find confusing or needing improvement however reports accompanied by a pull request will likely get faster attention.
Report your issue as clearly as possible. By "clear" we mean:

i. Specify the branch this occurred in.

ii. Be specific about the steps you took to reproduce.

iii. Feel free to use screenshots/screencasts to illustrate

iv. Use URLs for the page the issue to place on where possible.
Don't "bump" bug reports if we don't respond right away. We see every report coming in, but we'll only reply if we need clarification or if we think its invalid. Otherwise, we're likely working on a fix and the issue will be updated when the fix is complete.

Pull Requests

One of the reasons we created this private repo on GitHub is because we wanted to open up EE development to 3rd party developers who might want to contribute to the codebase. GitHub makes this really easy to do so via pull requests. If you don't know what pull requests are, please read up on them via the GitHub help/documentation.

Here's how we deal with pull requests for our repo:

Any new FEATURES in a pull request should be based off of the master branch. If your feature pull request is based off any other branch it will not be considered.
Any BUGFIX pull requests should be based off of the branch the bug was found. Please verify if it is in master before submitting the pull request. If it is in reproducible on master, then the pull-request should be based off of master.
We greatly appreciate any pull-requests submitted for consideration, but please understand we are very selective in what we decide to include in our official add-ons. If the "feature" is something that expands too much on our design decisions for this add-on then we may suggest you develop your pull request into a different add-on for EE.

You may find our post on contributing to open source software helpful.

eea-beaver-builder's People

Contributors

Stargazers

Watchers

Forkers

sethshoultes shawnk45

eea-beaver-builder's Issues

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

I am seeing syntax errors when trying to save an EE4 BB ticket module, while the EEA BB add-on is active:

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data[Learn More] fl-builder-ajax-layout.js:11:77
	FLBuilderAJAXLayout http://801website.com/ee4-8/wp-content/plugins/bb-plugin/js/fl-builder-ajax-layout.js:11:77
	_renderLayout http://801website.com/ee4-8/wp-content/plugins/bb-plugin/js/fl-builder.js:2179:24
	_renderPreview http://801website.com/ee4-8/wp-content/plugins/bb-plugin/js/fl-builder-preview.js:608:4
	d http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:2:3854
	ajax/< http://801website.com/ee4-8/wp-content/plugins/bb-plugin/js/fl-builder.js:8452:6
	i http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:2:27444
	fireWith http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:2:28213
	y http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:4:22719
	c http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:4:26925

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data[Learn More] fl-builder.js:6418:17
	_saveSettingsComplete http://801website.com/ee4-8/wp-content/plugins/bb-plugin/js/fl-builder.js:6418:17
	_saveSettingsComplete self-hosted:1092:17
	ajax/< http://801website.com/ee4-8/wp-content/plugins/bb-plugin/js/fl-builder.js:8452:6
	i http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:2:27444
	fireWith http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:2:28213
	y http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:4:22719
	c http://801website.com/ee4-8/wp-includes/js/jquery/jquery.js:4:26925

Add Calendar Support

This will add support for the Event Espresso 4 Calendar add-on.

Fatal error: Call to undefined function espresso_display_ticket_selector

To reproduce, create a new page, then add the EE4 ticket selector to the page using Beaver Builder. Save the page, then try to edit the page using Beaver Builder.

Fatal error: Call to undefined function espresso_display_ticket_selector() in /Users/sethshoultes/Documents/Websites/espresso-4-9.dev.cc/wp-content/plugins/eea-beaver-builder/beaver-builder-modules/ticket-selector/includes/frontend.php on line 4

Create a stand-alone plugin for the EE4 BB integration

I created an integration with the Beaver Builder Power Pack add-on and EE4 but now I want extract the code into's it's own BB add-on.

Ticket Selector JS not being enqueued

Beaver Builder doesn't execute wp_enqueue_scripts, so our ticket selector scripts aren't getting loaded when needed

Certain settings are not saving

When adding an event to the BB page and saving, then refreshing the page, the button settings are not saving. There are few other settings that are not saving either.

Would be great to support BB Field Connections

Beaver Builder offers the ability to use something called a field connection to pull in a post types specific content.
https://kb.wpbeaverbuilder.com/category/544-field-connections

It would be great if there were field connectors so that I can make an single event details page that works for all events.

Currently when adding an event ticket module, you have to select what event you want it for, instead it should pull based off the post itself.

Tickets widget not appearing until page saved

This has been happening since #4 got fixed

Add events list support

This will basically display a customizable events list.

EE polluting BB ajax responses without compatibility shim

BB 2.1 contains this code

/**
* Fixes ajax issues with Event Espresso plugin when builder is open.
* @since 2.1
*/
function fl_ee_suppress_notices() {
   if ( FLBuilderModel::is_builder_active() ) {
       add_filter( 'FHEE__EE_Front_Controller__display_errors', '__return_false' );
   }
}
add_action( 'wp', 'fl_ee_suppress_notices' );

/**
* Dont load ee core, fixes the text editor tabs missing issue.
* @since 2.1
*/
function fl_ee_no_load_builder_active() {
   if ( isset( $_GET['fl_builder'] ) && class_exists( 'EE_System' ) ) {
       remove_action( 'init', array( EE_System::instance(), 'core_loaded_and_ready' ), 9 );
   }
}
add_action( 'after_setup_theme', 'fl_ee_no_load_builder_active' );

/**
* Stops ee from outputting HTML into our ajax responses.
* @since 2.1
*/
function fl_ee_before_ajax() {
   add_filter( 'FHEE__EE_Front_Controller__display_errors', '__return_false' );
}
add_action( 'fl_ajax_before_call_action', 'fl_ee_before_ajax' );

On #15 Simon Prosser from BB agreed fl_ee_no_load_builder_active is no longer necessary, but I'd like to investigate the other compatibility shims and see if those might be affecting other plugins and whether EE core should make any adjustments

EE breaking visual/text tabs on WYSIWYG editors in Page Builder modules.

Hello,

We have Event Espresso installed on our site, however we are also using Beaver Builder’s Page Builder module to author non-EE pages.

What we have noticed is that for pages that have WYSIWYG modules, the Visual/Text tabs have disappeared. When EE is disabled, these tabs reappear.

I’m just wonder if you have any idea of why EE is getting in the way of Page Builder and how we can rectify it.

Cheers!

Crashed my site

I've got the latest version of BB 2.0.6, and EE 4.9.58p. When I installed this plugin it gave me this error: https://www.screencast.com/t/dBkH1vvPD. I'm also using Beaver Themer. I used my staging site, so no harm, just thought you should know. I can live without the plugin for now, but would love to see more features added.

Thanks.

Add People Add-on Support

This would add support for the Event Espresso 4 People Add-on.

Add Table View Support

Adding in table view support

Add Grid view support

Need to add support for the events Grid View EE4 add-on.

Hide Table Template Venues

Looks like the EE4 table template supports hiding the venue details using a shortcode parameter. We should use that instead of hiding the venue using CSS.

This plugin prevents normal EE events from saving properly

When you save an event with this add-on active, the event fields from the posts table don't get saved

Can't change the font size of the tickets

Hello, I just downloaded this plugin to use with Event Espresso and Beaver Builder. The Typography section of the Event Module should allow me to change the font size in the Tickets section. But no matter what I enter for a font size, the font-size doesn't change. So then I tried to fix it via CSS. The ticket size in the CSS is 8px with "! important" after it. However, when I change it to 16px, it appears to change while I'm still using Beaver Builder's Page Builder, but as soon as I publish BB and refresh my page, the fonts show up small - at - I guess - 8px. My client needs to launch this golf tournament this weekend. Can anyone help me (rather quickly)? Thanks so very much in advance.