Attendize is an open-source ticket selling and event management platform built on Laravel.

Overview

Attendize is an open-source ticketing and event management application built using the Laravel PHP framework. Attendize allows event organisers to sell tickets to their events and manage attendees without paying service fees to third party ticketing companies.

Attendize Attendize

Attendize

Open-source ticket selling and event management platform

Please report bugs here: https://github.com/Attendize/Attendize/issues. Detailed bug reports are more likely to be looked at. Simple creating an issue and saying "it doesn't work" is not useful. Providing some steps to reproduce your problem as well as details about your operating system, PHP version etc can help.

Take a look http://www.attendize.com/troubleshooting.html and follow the http://www.attendize.com/getting_started.html guide to make sure you have configured attendize correctly.

Documentation Website: http://www.attendize.com
Demo Event Page: http://attendize.website/e/799/attendize-test-event-w-special-guest-attendize
Demo Back-end Demo: http://attendize.website/signup

Current Features (v2.X.X)

  • Beautiful mobile friendly event pages
  • Easy attendee management - Refunds, Messaging etc.
  • Data export - attendees list to XLS, CSV etc.
  • Generate print friendly attendee list
  • Ability to manage unlimited organisers / events
  • Manage multiple organisers
  • Real-time event statistics
  • Customizable event pages
  • Multiple currency support
  • Quick and easy checkout process
  • Customizable tickets - with QR codes, organiser logos etc.
  • Fully brandable - Have your own logos on tickets etc.
  • Affiliate tracking
    • track sales volume / number of visits generated etc.
  • Widget support - embed ticket selling widget into existing websites / WordPress blogs
  • Social sharing
  • Support multiple payment gateways - Stripe, PayPal & Coinbase so far, with more being added
  • Support for offline payments
  • Refund payments - partial refund & full refunds
  • Ability to add service charge to tickets
  • Messaging - eg. Email all attendees with X ticket
  • Public event listings page for organisers
  • Ability to ask custom questions during checkout
  • Browser based QR code scanner for door management
  • Elegant dashboard for easy management.

Minimum Requirements

Attendize should run on most pre-configured LAMP or LEMP environments as long as certain requirements are adhered to. Attendize is based on the Laravel Framework

PHP Requirements

  1. PHP >= 7.1.3
  2. OpenSSL PHP Extension
  3. PDO PHP Extension
  4. Mbstring PHP Extension
  5. Tokenizer PHP Extension
  6. Fileinfo PHP Extension
  7. GD PHP Extension

MySQL Requirements

  1. MySQL version 5.7 or higher required

Contributing

Feel free to fork and contribute. If you are unsure about adding a feature, create a Github issue to ask for Feedback. Read the contribution guidelines

Submitting an issue

If you encounter a bug in Attendize, please first search the list of current open Issues on the GitHub repository. You may add additional feedback on an existing bug report. If the issue you're having has not yet been reported, please open a new issue. There is a template available for new issues. Please fill out all information requested in the template so we can help you more easily.

Please note: support is not offered from the project maintainers through GitHub. Paid support is available by purchasing a license.

Installation

To get developing straight away use the Pre-configured Docker Environment
To do a manual installation use the Manual Installation Steps

Testing

To run the application tests, you can run the following from your project root:

# If the testing db does not exist yet, please create it
touch database/database.sqlite
# Run the test suite
./vendor/bin/phpunit

This will run the feature tests that hits the database using the sqlite database connection.

Troubleshooting

If you are having problems please read the troubleshooting guide

License

Attendize is open-sourced software licensed under the Attribution Assurance License. See http://www.attendize.com/license.html for further details. We also have white-label license options available.

Code of Conduct

The Attendize community operates a Code of Conduct to ensure everyone is able to participate comfortably, equally and safely.

Issues
  • Payment gateway information is not saved

    Payment gateway information is not saved

    I am trying to use Coinbase or Stripe as payment gateway. When I enter API key, secret and account ID and click Save account details, I get message that everything was save. Unfortunately when I get back to Account setting, all the fields are empty again.

    opened by sipak 22
  • Booking not registering

    Booking not registering

    Getting error message "Whoops!, it looks like the server returned an error. Please try again, or contact the webmaster if the problem persists." after submitting a booking this is both with free and paid events,

    With paid events(using stripe) the payment does go through, just nothing registering on the system,

    it has me at a loss why, no logs are registering either and debug is set to true, im at a total loss

    opened by angrydogmedi 18
  • French localisation

    French localisation

    Hello,

    how can we translate attendize interface in french language ?

    Regards

    enhancement 
    opened by guidtz 17
  • installation error

    installation error

    I've just followed the steps for manual installation and when i'm trying to install it get this error

    Warning: require(/home/u771664184/public_html/attendize/bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in /home/u771664184/public_html/attendize/bootstrap/autoload.php on line 17 PHP Fatal error: require(): Failed opening required '/home/u771664184/public_html/attendize/bootstrap/../vendor/autoload.php' (include_path='.:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php') in /home/u771664184/public_html/attendize/bootstrap/autoload.php on line 17

    opened by cpalop 17
  • Install failure

    Install failure

    I couldn't get the install to work - having done the manual install and navigated to /public, I'm redirected to: https://cardiff.marketing/attendize/public/select_organiser with a 404.

    Am I missing something obvious?

    opened by yhorian 17
  • Which device use for QR Code and How To Setup In Local Device

    Which device use for QR Code and How To Setup In Local Device

    Hi,

    Thanks for making this type of Good System I like it..

    I have a question , How i read QR Code in below screen(sent screenshot) , I tried my system (laptop) camera but that camera not able to read this so Is there any device I need to purchase or any way for read this QR Code ?

    image

    Please help me

    Thanks&Regards

    opened by harshit1235 16
  • Support for multiple languages

    Support for multiple languages

    Laravel provides an excellent way to add translations to your web application. At this point. Almost none of these features are used. If all the sentences and words are stored in the translation files, I probably would add all dutch translations as well.

    feature 
    opened by markwalet 15
  • docker improvements for production enviroment

    docker improvements for production enviroment

    I made some improvements on docker installation for a "production" environment (#400). Now envs are loaded outside the container, no need to manually create a .env file inside the repo. I created a .env.dist file, this is used for references on what envs are copied inside the container folder at startup. Dockerfile is only one, it uses ubuntu 16.04 + apache + php7.1 + mysql-client. Composer install now runs during the image build, so no need to manually run it after the container start. I would like to use the docker cache system for avoid to run at every build but I found lots of references under the /app folder so I cannot copy only composer files (json, lock, package). I added two bash script: generate_env.sh: this script search in the environment if .env.dist envs exists and prepare a list of valorized envs to use for the .env file start.sh: this script runs at container startup, check for .env file and if not exists it creates a new one on the project path, generate the APP_KEY env and reload the cache config. This script also check for a WORKER env, used for launch the queue demon instead of apache. So with this logic the worker container generates the .env file for itself too and starts correctly. I also add the support for a unique APP_KEY env for both web and worker, so if it exists it doesn't generate a different one.

    The resulted docker-compose is really simple and you can launch with docker-compose -f docker-compose.production.yml up

    enhancement 
    opened by Leen15 15
  • [FEATURE] POST Return URL for off-site payment gateways with Omnipay

    [FEATURE] POST Return URL for off-site payment gateways with Omnipay

    Is your feature request related to a problem? Please describe. I'd like to setup an off-site payment mechanism with Omnipay but I can't figure out where to find the return URL that the offsite payment gateway will call back to. Does Attendize handles off-site payments with return urls ?

    Describe the solution you'd like Being able to have a return URL for off-site payments to confirm that the client has paid and has means to verify the data sent by the off-site payment gateway. Specifically, in my case, the payment gateway sends a POST to the return url with data to be able to verify if the order was successful or not. (order would go from Awaiting payment to Order Complete if it is successfull)

    Describe alternatives you've considered Just using on-site payments gateways, but the fees are greater.

    Additional context I'm trying to wrap my head both around Attendize and Omnipay. I'm a beginner in php and Lavarell, but I am willing to learn. I'm also trying to write an Omnipay wrapper for my payment gateway.

    Thanks for reading!

    feature 
    opened by storca 15
  • [BUG] Composer failed In PackageManifest.php line 131:   Undefined index: name

    [BUG] Composer failed In PackageManifest.php line 131: Undefined index: name

    Describe the bug Followed directions at https://www.attendize.com/getting_started.html on my site. Composer threw errors: `Generating optimized autoload files Class Tests\Features\UtilsTest located in ./tests/Feature/Utils/UtilsTest.php does not comply with psr-4 autoloading standard. Skipping. Class Tests\Features\OrganisationWithoutTaxTest located in ./tests/Feature/OrderCancellation/OrganisationWithoutTaxTest.php does not comply with psr-4 autoloading standard. Skipping. Class Tests\Features\OrganisationWithTaxTest located in ./tests/Feature/OrderCancellation/OrganisationWithTaxTest.php does not comply with psr-4 autoloading standard. Skipping. Class HTMLPurifier_Language_en_x_test located in ./vendor/ezyang/htmlpurifier/library/HTMLPurifier/Language/classes/en-x-test.php does not comply with psr-0 autoloading standard. Skipping.

    Illuminate\Foundation\ComposerScripts::postAutoloadDump @php artisan package:discover --ansi In PackageManifest.php line 131: Undefined index: name Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1`

    To Reproduce Steps to reproduce the behavior:

    1. follow install instructions
    2. composer install dies with above error

    Screenshots If applicable, add screenshots to help explain your problem.

    Environment the bug happens in (Desktop, Mobile, CLI) (please complete the following information):

    • OS: [Linux
    • Browser N/A
    • Version [e.g. 22]

    Version of Attendize you are using

    • Master branch or release tag Master 1.1 Where you are running Attendize
    • in Docker, a Virtual Machine, Shared Webhost, VPS etc

    What version or Operating System are you using on the above server cloudlinux:7.8:GA:server

    What version of PHP you are using on the above server

    • 7.4 What web server are you using Attendize with Apache.

    Additional context Add any other context about the problem here.

    bug 
    opened by jimrome 14
  • [FEATURE] Recurring Events

    [FEATURE] Recurring Events

    There are so many events that will happen yearly monthly or weekly,

    So I would suggest having a recurring solution-based event creation for such events. That will solve lots of problems.

    Right now we have the start and end date saved in the event table, for the recurring part we would need it in another table and manage the dates when the user is trying to book the ticket. Cause then the user will be able to select any date he wants to go to.

    feature 
    opened by princerai162 0
  • Integraton to Wordpress

    Integraton to Wordpress

    Is there any integration to MemberPress Wordpress plugin ?

    opened by JoopStringer 0
  • [BUG] Your e-mail is not working

    [BUG] Your e-mail is not working

    Describe the bug I cant send you an email. Support and hello emails...

    Your message couldn't be delivered to [email protected] because the remote server is misconfigured. See technical details below for more information.

    The response was: A delivery loop was detected which causes this email to be undeliverable.

    I send it from a @gmail.com

    To Reproduce

    Expected behavior

    Screenshots

    Environment the bug happens in (Desktop, Mobile, CLI) (please complete the following information):

    Version of Attendize you are using

    Where you are running Attendize

    What version or Operating System are you using on the above server

    What version of PHP you are using on the above server

    What web server are you using Attendize with

    Additional context

    bug 
    opened by lennert1986 0
  • [BUG] 'tickets_sold' doesn't have a default value

    [BUG] 'tickets_sold' doesn't have a default value

    Describe the bug When you visit a referral link, it says:

    We'll be back soon We're currently making improvements to our website.

    From the event settings, you cannot see anything about referral used.

    To Reproduce Visit any event with ?ref=something at the end.

    Expected behavior Purchase tickets and see stats in referral settings webpage.

    Screenshots No attachment.

    Environment the bug happens in (Desktop, Mobile, CLI) (please complete the following information):

    • OS: Windows
    • Browser: Google Chrome
    • Version:

    Version of Attendize you are using

    • Master branch or release tag (Attendize 2.4.0)

    Where you are running Attendize

    • VPS

    What version or Operating System are you using on the above server

    • Ubuntu 20.04

    What version of PHP you are using on the above server

    • e.g PHP 7.3.4

    What web server are you using Attendize with

    • Apache2

    Additional context The log file says:

    [previous exception] [object] (PDOException(code: HY000): SQLSTATE[HY000]: General error: 1364 Field 'tickets_sold' doesn't have a default value at /var/www/html/eventi.mydomain.it/html/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:121

    production.ERROR: SQLSTATE[HY000]: General error: 1364 Field 'tickets_sold' doesn't have a default value (SQL: insert into affiliates (name, event_id, account_id, visits , updated_at, created_at) values (test, 1, 1, 1, 2021-11-07 21:28:01, 2021-11-07 21:28:01)) at /var/www/html/eventi.oratoridisettimo.it/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php:669

    Fixed the error adding the Default value 0 in the Database (ALTER TABLE affiliates CHANGE tickets_sold tickets_sold INT(11) NOT NULL DEFAULT '0';). You can easily fix this problem in future versions

    bug 
    opened by TechBreakHelp 0
  • [FEATURE] Calculate addition/refund when ticket changed.

    [FEATURE] Calculate addition/refund when ticket changed.

    Is your feature request related to a problem? Please describe. If I edit an attendee and move them to a different ticket, they may owe us more, or be due a refund. The systemat reflects the ticket change for the attendee, but not any change in what might be due (see image below where I changed an adult ticket to a concession). In this scenario it would result in a refund due of £40 as the concession ticket is £40 less than the adult ticket:

    Screenshot 2021-11-03 at 16 36 28

    Describe the solution you'd like For the system to recognise changes to the tickets recalculate as appropriate, so allowing for the refund or additional payment to be taken or made through the payment gateway.

    feature 
    opened by justynpride 0
  • [BUG] Users with Stripe payment gateway can never cancel any ticket order

    [BUG] Users with Stripe payment gateway can never cancel any ticket order

    Attendize assumes that Omnipay's stripe sca support works, but it does not, and it never has: the library has never implemented support for refunds.

    Consequently if you're using Stripe-SCA as the payment gateway and you have a need to cancel any ticket or order at all, all db relationships start going out of sync immediately. Currently I have dozens of tickets which are both showing as "completed" under event orders, and cannot be cancelled because "all attendees in this order have been cancelled"

    image

    Additionally when at this point you push "confirm cancel"... nothing at all happens and the modal remains on screen.

    Version of Attendize you are using 2.2.0

    Where you are running Attendize Ubuntu 20.04 on Linode

    What version of PHP you are using on the above server PHP 7.3

    What web server are you using Attendize with Nginx and php7.3-fpm

    bug 
    opened by handelaar 1
  • Covid QR code

    Covid QR code

    Can the ability to optionally request a QR code to be uploaded if required? (could be photo ID to prove ticket authenticity or Covid19 QR code)

    opened by maccored 1
  • (Add) Model Factories and Base Tests

    (Add) Model Factories and Base Tests

    • Note this PR adds generated model factories, generated HTTP tests for controllers, generated unit tests for form requests, generated tests for console commands and configured a basic testing environment.
    • These tests are marked as incomplete!
    • This PR also updates dependencies so I could use PHP 8.
    vendor/bin/phpunit -d memory_limit=1024M
    PHPUnit 8.5.21 by Sebastian Bergmann and contributors.
    
    IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII  63 / 127 ( 49%)
    IIIIIIIIII.IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII 126 / 127 ( 99%)
    .                                                               127 / 127 (100%)
    
    Time: 15.41 seconds, Memory: 58.00 MB
    
    OK, but incomplete, skipped, or risky tests!
    Tests: 127, Assertions: 6, Incomplete: 125.
    
    opened by HDVinnie 5
  • Some questions related to Attendize undocumented functionnalities

    Some questions related to Attendize undocumented functionnalities

    I saw some code and some data structure, or posts into issues that make me wonder if:

    1. There's some possibility to let people create their own account on the platform like entity + user
    2. There's some super admin function to see all of them
    3. There's a possibility to create users and attach them to an existing entity
    4. There's a possibility to have a "platform fee"
    opened by clawfire 0
  • [BUG] Makefile don't work on OSX

    [BUG] Makefile don't work on OSX

    Describe the bug Error while running make setup

    To Reproduce Steps to reproduce the behavior:

    1. Clone project
    2. Run make setup
    3. See error

    Expected behavior A clear and concise description of what you expected to happen.

    Logs You can see the logs here https://pastebin.com/KbTQfSUs

    Environment the bug happens in (Desktop, Mobile, CLI) (please complete the following information):

    • OS: Mac

    Version of Attendize you are using

    • Master
    bug 
    opened by clawfire 20
Releases(v2.4.0)
  • v2.4.0(Oct 21, 2021)

    Fixes

    • Duplicated translation files https://github.com/Attendize/Attendize/issues/594
    • Sending messages from orders page is broken https://github.com/Attendize/Attendize/issues/955
    • Add request throttling to auth routes
    • Change the Publish event from a link to a form and button using POST so the request can be validated

    Additions

    • Improve German translations https://github.com/Attendize/Attendize/pull/986 and https://github.com/Attendize/Attendize/pull/985
    • Add SECURITY.md

    Deprecations

    • Remove Google+ https://github.com/Attendize/Attendize/pull/970
    Source code(tar.gz)
    Source code(zip)
  • v2.3.1(Aug 1, 2021)

  • v2.3.0(Aug 1, 2021)

    v2.3.0

    Additions

    https://github.com/Attendize/Attendize/pull/922 Add RTL (right-to-left) Language support https://github.com/Attendize/Attendize/pull/937 Add Russian language files and templates

    Fixes

    https://github.com/Attendize/Attendize/issues/950 Error in language file https://github.com/Attendize/Attendize/pull/954 Fix RTL styles https://github.com/Attendize/Attendize/pull/939 Make non-queued emails translatable https://github.com/Attendize/Attendize/pull/938 Fix untranslated email template

    Source code(tar.gz)
    Source code(zip)
  • v2.2.4(Jul 21, 2021)

  • v2.2.3(Jul 19, 2021)

    Additions

    None

    Fixes

    • #871: Undefined variable: organisers
    • #917: make setup to build a Docker Image does not work
    • #918: wrong import name
    • #923: call to undefined function lang() in reservation confirmation view
    • #924: Update OrderConfirmation.blade.php
    Source code(tar.gz)
    Source code(zip)
  • v2.2.2(May 4, 2021)

  • v2.2.1(Apr 16, 2021)

  • v2.2.0(Apr 11, 2021)

    Additions

    None

    Fixes

    • #811 [BUG] I found a possible security issue
    • #844 [BUG] Mail not sent with real queue

    #Changelog

    • https://github.com/Attendize/Attendize/pull/883 Refactor Queued Emails
    • https://github.com/Attendize/Attendize/pull/882 Address security issue issue reported by jrckmcsb
    Source code(tar.gz)
    Source code(zip)
  • v2.1.2(Dec 1, 2020)

  • v2.1.1(Nov 29, 2020)

    Additions

    None

    Fixes

    • #822 Fix workflow for database migrations during set up process

    Changelog

    • #822 Fix workflow for database migrations during set up process
    Source code(tar.gz)
    Source code(zip)
  • v2.1.0(Jul 1, 2020)

    Additions

    • Added captcha option to sign up, log in, and contact form pages
      • Option to use recaptcha or hcaptcha
    • Added new makefile command make autoload to dump and regenerate composer autoload files, for when new classes etc are added
    • Updated README documentation with minimum system requirements
    • Add database migrations to set up script

    Fixes

    • Use promises when initializing check in page
    • Fix typo in lang file

    Change log

    • Use promises to initialise camera for check-in #712
    • Allow use of both reCaptcha hCaptcha or no capture based on config #808
    • Fix syntax error #810
    • Add reCAPTCHA #585
    • Add hCaptcha #793
    Source code(tar.gz)
    Source code(zip)
  • v2.0.2(Jun 1, 2020)

    Summary

    • Updated docker config including apache support
    • Added German and Italian languages to translations
    • Additional translations for existing languages
    • Bug fixes

    Changes

    • Do not escape html for post order message #629
    • Fix XSS and 500 error if version check fails #743
    • Fix 500 error in ManageAccountController.php #789
    • Docker improvements for production enviroment #401
    • German translation #491
    • Prevent duplicate queries #534
    • Add Italian localization && Minor translation fixes #757
    • Enhancements to Docker Config #802
    Source code(tar.gz)
    Source code(zip)
  • v2.0.1(Apr 7, 2020)

  • v2.0.0(Apr 7, 2020)

    Summary

    We are looking to add stability and general improvements to the project. These changes are listed below as we continue to add the contributions from the community, general bug fixes, stability in product flows, test structure and developer experience to more easily allow for better contributions.

    Contributions or issues

    Please log an issue and label it with v2.0.0.

    Notes:

    To avoid errors, after checking out this version, the following steps should be performed:

    Install new libraries

    composer install
    

    Delete old views and cached configurations

    php artisan config:clear
    php artisan cache:clear
    php artisan view:clear
    php artisan route:clear
    php artisan optimize:clear
    php artisan clear-compiled
    composer dump-autoload
    

    Database

    The migrations include a fix script that need to retroactively fix orders and it's related data with the current state of the database. This is a mutation of data and is potentially dangerous. That said it was necessary to bring the order and refund flows under control to ensure consistent behavior when completing an order/refund flow.

    1. Make a backup of your current production database.
    2. Run php artisan migrate
    3. Open your laravel logs to see the retrofix output

    Changes

    • Calculations fixes (#645)
    • Dashboard details (#697)
    • Patch for Organizer View (#655)
    • Tests setup (#711)
    • Made the test database connection button more visible (#710)
    • Allow checking in with private reference number (#656)
    • Upgrade to Laravel 6.5.1 (#688)
    • Added TrustProxies Middleware for Reverse Proxy Compatability (#713)
    • Fixed payment gateway update migration (#706)
    • Makes it possible to process free payments (#705)
    • Bugfixes in routes, missing event_id (#731)
    • New markdown parser (#770)
    • Event create UI form error handling (#769)
    • Offline Payments Copy Fixes (#774)
    • General regression fixes after laravel 6 upgrade (#775)
    Source code(tar.gz)
    Source code(zip)
  • v1.3.0(Jun 7, 2019)

    1. #573 - Unique attendee ID on data export
    2. #575 - Fixed Feedback Url.
    3. #581 - Added Japanese translation.
    4. #586 - Nits (https and fix a dev console warning)
    5. #588 - Added more translatable strings.
    6. #600 - Manage event currency.
    7. #574 - Fixed HTML email template.
    8. #612 - Fixed Data picker which broke in google chrome.
    9. #613 - Added Dutch translation.
    10. #616 - Changed private reference numbers.
    11. #630 - Remove closures on route files.
    12. #632 - Fixed fix(qr-code scanning).
    13. #634 - Fixed the colour picker.
    14. #640 - Added the GTM container.
    15. #642 - Fix French translation.
    16. #646 - Removed terms and conditions route as its not used
    Source code(tar.gz)
    Source code(zip)
  • v1.2.0(Feb 18, 2019)

    1. Added new feature Access codes. If a ticket is set to hidden an Access Code can be assigned to it. Once a user enters the Access Code they can see and purchase the hidden ticket.
    2. Allow offline payments when no gateway defined.
    3. Fixed #409,#472 - Remove reserved tickets once they have been bought.
    4. Fixed #458,#524 - Fixed Attendize installation errors.
    5. Fixed #538 - Fixed Order exports.
    6. Fixed #556 - Use Date Time configuration from the .env file.
    7. Added #557 - Remove social sharing section when no share provider is enabled.
    8. Added extra French translations.
    9. Fixed url links in translation files.
    Source code(tar.gz)
    Source code(zip)
  • v1.1.3(Dec 1, 2018)

    Update 21/12/2018: If you are upgrading to 1.1.3 from 1.1.2 you will need to update your configuration file to have the following new date configurations.

    DEFAULT_DATEPICKER_SEPERATOR="-" DEFAULT_DATEPICKER_FORMAT="yyyy-MM-dd HH:mm"

    which replaces

    DEFAULT_DATE_FORMAT="Y-m-d" DEFAULT_TIME_FORMAT="H:i"

    1. Fixed #470 issue with password reset that was cause by Laravel upgrade.
    2. Fixed #376. Dont send messages to cancelled attendees.
    3. Fixed #327. php artisan route:list error was giving an error.
    4. Added French translation and Spanish Translation.
    5. Improved Logic in event checkout controller.
    6. Corrected some spelling mistakes.
    7. Fixed #469. New default error page so actual error message is logged correctly.
    8. Fixed #501. Calendar off by 1 error.
    9. Additional improvements. Fixed iframe from not loading on event page preview. Fixed broken license urls.
    10. Other improvements from @publicarray. Increase minimum password length to 8 characters. Improved session preferences and defaults. Improve private_reference_number Randomness. Fix 7.2 support when ordering tickets. Dates can now be customised in the config and better date validation.
    Source code(tar.gz)
    Source code(zip)
  • v1.1.2(Oct 2, 2018)

    1. This release fixes an XSS vulnerability thanks @publicarray #476 #478. All users of the Attendize 1.1 are encouraged to upgrade.
    2. Fixed bug where upcoming events were 1 month in the future. #414 #450 #434
    3. Fixed #475 where wrong database model was used.
    4. Fixed #448 where tax amount not set after importing users.
    5. Fixed bug where sales volume is not incremented correctly.
    6. Removed leftover code for migs and coinbase as default gateways.
    7. Update docker dev environment. Added SSL support and bumped MySQL version.
    8. Updated links to documentation and copy.
    Source code(tar.gz)
    Source code(zip)
  • v1.1.1(Sep 3, 2018)

    1. Fixed minor bugs with new Laravel 5.6 upgrade. Use send instead of queue when inviting attendees.
    2. Use Pluck instead of Lists on Attendee questions.
    3. Fixed text on installer screen.
    4. Fixed small bug with installation process.
    Source code(tar.gz)
    Source code(zip)
  • v1.1.0(Aug 22, 2018)

    This release contains the following

    1. Upgraded Attendize to use Laravel 5.6.
    2. Removed Potsky\LaravelLocalizationHelper as its no longer being maintained and doesn’t support Laravel 5.6.
    3. Added missing translations.
    4. Support out the box for Coinbase and Migs has been dropped due to upgrade of Omnipay to v3.
    5. Improvements on error handling when tickets can’t be generated and emails can’t be sent.
    6. Fixed a bug where tickets weren’t available after an event had started.
    7. Updated various composer dependencies so Attendize is using the latest versions.
    Source code(tar.gz)
    Source code(zip)
  • v0.5.2-alpha(Aug 10, 2018)

  • v0.5.1-alpha(Mar 23, 2016)

  • v0.4.0-alpha(Mar 14, 2016)

  • v0.2.0-alpha(Mar 4, 2016)

  • v0.1.0-alpha(Mar 2, 2016)

Owner
Attendize
Open-source ticket selling & event management
Attendize
Free, open-source, self-hosted CMS platform based on the Laravel PHP Framework.

October is a Content Management System (CMS) and web platform whose sole purpose is to make your development workflow simple again. It was born out of

October CMS 10.7k Nov 27, 2021
Free, open-source, self-hosted CMS platform based on the Laravel PHP Framework.

Winter is a Content Management System (CMS) and web platform whose sole purpose is to make your development workflow simple again

Winter CMS 779 Nov 30, 2021
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.

Orchard Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform. You can try it for free on DotN

OrchardCMS 2.3k Nov 22, 2021
[READ-ONLY] An open source Content Application Platform based on Flow. A set of core Content Management features is resting within a larger context that allows you to build a perfectly customized experience for your users

The Neos package Note This repository is a read-only subsplit of a package that is part of the Neos project (learn more on www.neos.io). Neos is an op

Neos 97 Nov 25, 2021
ApostropheCMS is a full-featured, open-source CMS built with Node.js that seeks to empower organizations by combining in-context editing and headless architecture in a full-stack JS environment.

ApostropheCMS ApostropheCMS is a full-featured, open source CMS built with Node.js that seeks to empower organizations by combining in-context editing

Apostrophe Technologies 3.7k Nov 29, 2021
A modular, high performance, headless e-commerce platform built with Python, GraphQL, Django, and ReactJS.

Saleor Commerce Customer-centric e-commerce on a modern stack A headless, GraphQL-first e-commerce platform delivering ultra-fast, dynamic, personaliz

Mirumee Labs 14.5k Nov 26, 2021
Reaction is an API-first, headless commerce platform built using Node.js, React, GraphQL. Deployed via Docker and Kubernetes.

Reaction Commerce Reaction is a headless commerce platform built using Node.js, React, and GraphQL. It plays nicely with npm, Docker and Kubernetes. G

Reaction Commerce 11.6k Dec 2, 2021
Business class content management for Node.js (plugins, server cluster management, data-driven pages)

PencilBlue A full featured Node.js CMS and blogging platform (plugins, server cluster management, data-driven pages) First and foremost: If at any poi

PencilBlue, LLC. 1.6k Nov 17, 2021
Subrion CMS - open source php content management system.

Subrion CMS What is Subrion? Subrion is a Content Management System (CMS) which allows you to build websites for any purpose. Yes, from blog to corpor

Intelliants 267 Oct 15, 2021
Radiant is a no-fluff, open source content management system designed for small teams.

Welcome to Radiant Radiant is a no-fluff, open source content management system designed for small teams. It is similar to Textpattern or MovableType,

Radiant CMS dev team 1.7k Nov 19, 2021
PushType is a modern, open source content management system for Ruby on Rails.

PushType PushType is a modern content management system for Ruby on Rails. It takes advantage of powerful new features available in the latest version

PushType 295 Nov 12, 2021
Open Source multi-language/multi-currency/multi-store E-commerce platform for Ruby on Rails with a modern UX, PWA frontend, REST API, GraphQL, several official extensions, and 3rd party integrations.

Spree Commerce Success Stories Documentation Integrations Spree is a complete open source e-commerce solution built with Ruby on Rails. It was started

Spree Commerce 11.5k Nov 30, 2021
Open-Source Data Platform 🐰 — Directus wraps any SQL database with a real-time GraphQL+REST API and an intuitive app for non-technical users.

?? Introduction Directus is a real-time API and App dashboard for managing SQL database content. Free & open-source. No artificial limitations, vendor

Directus 12.9k Nov 25, 2021
Storytime is a Rails 4+ CMS and blogging engine, with a core focus on content. It is built and maintained by @cultivatelabs

Storytime is a Rails 4+ CMS and blogging engine, with a core focus on content. It is built and maintained by CultivateLabs / @cultivatelabs Features S

CultivateLabs 750 Nov 13, 2021
Open Source eCommerce Platform on Symfony

Sylius is an Open Source eCommerce platform on top of Symfony. The highest quality of code, strong testing culture, built-in Agile (BDD) workflow and

Sylius eCommerce 6.6k Nov 25, 2021
Open Source Digital Experience Platform (DXP, MDM/PIM, CDP, DAM, CMS/UX & eCommerce

Pimcore - Open Source Digital Experience Platform: MDM/PIM, CDP, DAM, CMS/UX & eCommerce ?? Website - Learn more about Pimcore ?? Documentation ?? Hel

pimcore 2.3k Nov 23, 2021
The most powerful headless CMS for Node.js — built with GraphQL and React

A scalable platform and CMS to build Node.js applications. schema => ({ GraphQL, AdminUI }) Keystone Next is a preview of the next major release of Ke

KeystoneJS 5.3k Dec 2, 2021