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.

Comments
  • 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
  • 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
  • [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
  • 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
  • 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
  • [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
  • Upgrade to Laravel 6.5.1

    Upgrade to Laravel 6.5.1

    Here we go again!

    I know that there are many files changed but it is necessary to do it well and I think that a "step by step" update would give many errors.

    I created a new Laravel project with 6.2 and copied file by file from Attendize, integrating, updating and merging.

    It's a big change (a lot of files) but I think it was necessary to start as clean as possible.

    You can follow the changes more simply by looking at my commits separately.

    • Updated everything to 6.2 and tested everything I could (create organizer, create event, buy ticket, use widget, send email, etc ...) Please if someone could do some more tests it would be perfect.
    • Updated all possible composer packages and deleted some unused ones
    • Now all routes use the new Laravel 6 syntax.
    • Some helpers have been rewritten and now use ServiceProviders
    • Deleted some Service Providers and Aliases from config/app.php file because from Laravel 5.5 some have activated the auto discovery function.

    Please @jeremyquinton do everything possible to merge this, if I have to change things I will change them, if there is something broken I will fix it :)

    I have spent quite a few hours both in this PR and in the two previous attempts, please don't let it be forgotten for months.

    My idea with this step is to have a good base to start with the new tests, refactored and simplified classes and of course to fix bugs :)

    Notes:

    To avoid errors, after cloning the repository and checking out the "update-laravel" branch, 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

    opened by CristianDeluxe 14
  • Error after checkout

    Error after checkout

    After i check out i get this error "Whoops!, it looks like the server returned an error. Please try again, or contact the webmaster if the problem persists."

    opened by nihar53 14
  • Add file upload question, validation, storage, and preview

    Add file upload question, validation, storage, and preview

    Hi!

    Following issues, I added a file upload question in Attendize surveys (fixes #1041 and fixes #1027).

    How does it work ?

    • When users submit files, they are validated by : mimetype, size and the 'required' flag of the question
    • If files are validated, they are stored in a temporary directory
    • If the order is successfull, files are moved in a permanent location
    • The partial path to the uploaded documents is stored in answer_text in the question_answers table like so docs/<custom_hash>/<laravel_file_hash>.ext

    Publicly accessible ??

    Yes, but the files are hidden via the following path structure /docs/<custom_hash>/<laravel_file_hash>.ext

    The custom_hash is made in an effort to make sandwich-proof hashes in case it is possible to get hashes during the order process.

    The hash is generated using php time and OS-based randomness here.

    Files are not accessible or editable by the user.

    Files can also stay on the server in case the order is cancelled or abandoned ; this is why I added a RemoveOldTempFiles job that removes files that are older than an hour.

    I'm happy to share this PR with you, feel free to test it and suggest changes!

    opened by storca 5
  • [FEATURE] support content in multiple languages

    [FEATURE] support content in multiple languages

    Is your feature request related to a problem? Please describe.

    My users are using 3-4 different languages, I would like to have a clean UI presenting each event in their language. And that all interactions (email and UI messages) be translated in their language.

    Describe the solution you'd like

    • Support for multi-language content, with a default/reference/mandatory language and multiple translations.
    • Platform would suggest automated translations (eg via deepl.com), admin could improve them.
    • User would be able to switch from language to another.
    • Non translated content would be either shown in default language or hidden completely based on setting by admin.

    Describe alternatives you've considered

    wordpress + event registration plugin + WPML or other multi-language plugin.

    feature 
    opened by berteh 0
  • Question: where/how to add more info to the Stripe process?

    Question: where/how to add more info to the Stripe process?

    Hi, After each event, I have to reconcile Stripe and have a hard time filtering the stripe data to match our Attendize events. Is there an additional field I can populate with the event_id or something to make reconciliation easier?

    Can someone please point me to the file/code where the stripe payload is prepared so I can see what fields might be available for posting additional data into stripe?

    I'm on version 2.4.0

    Thanks for any hints you can offer.

    opened by gainer-twister 1
  • [FEATURE] unfurl for attendize website

    [FEATURE] unfurl for attendize website

    Is your feature request related to a problem? Please describe. No, just for the website. It would be nice for the attendize website to have unfurl so when i post the link on discord, facebook, etc, it has a proper preview for folks to look at.

    Describe the solution you'd like Could we have better unfurl with the attendize website? Something like the below so we can have good previews in slack or discord: Screen Shot 2022-11-17 at 11 23 02 AM

    An explanation how to is here: https://blog.cristiana.tech/adding-website-previews-on-twitter-facebook-and-slack-link-unfurling

    Example of this in play on my personal website (not trying to show off, just a quick example in case folks need one) https://github.com/alexjyong/alexjyong.github.io/blob/main/index.html#L6

    Describe alternatives you've considered N/A

    Additional context N/A

    feature 
    opened by alexjyong 0
  • Change QrCode scanning to nimiq/qr-scanner and improve scan UI readability

    Change QrCode scanning to nimiq/qr-scanner and improve scan UI readability

    Hello!

    Following issue #1027 regarding the issues I've had with Qr Code scanning, I'd like to change the legacy QrCode scanning library to nimiq/qr-scanner.

    What I've done :

    • Changed the scanning library to qr-scanner
    • Adapted blade template, CSS and JS to fit the library
    • Enhanced UI readability when scanning tickets (clearer distinction between what's important and what's not)

    Note : I've had to change the way the video is displayed in the check-in page, the video preview is now smaller.

    Let me know what you think!

    opened by storca 3
Releases(v2.6.0)
  • v2.6.0(Sep 6, 2022)

    v2.6.0

    Fixes a major bug with refunding Stripe transactions not processing correctly. Also fixes a UI issue that allowed multiple/duplicate charges to go through due to the payment submit button not being locked correctly. Thank you to @storca for contributing these fixes.

    What's Changed

    • Fix StripeSCA not refunding and charging multiple times by @storca in https://github.com/Attendize/Attendize/pull/1016
    • Fix broken tests by @quentincaffeino in https://github.com/Attendize/Attendize/pull/978

    Full Changelog: https://github.com/Attendize/Attendize/compare/v2.5.0...v2.6.0

    Source code(tar.gz)
    Source code(zip)
  • v2.5.0(Jun 4, 2022)

    🎉 ! Support for Composer V2 ! 🎉

    Finally reached this big milestone in upgrading the legacy code. Big thanks to all who contributed, especially @quentincaffeino and @justynpride for providing code changes and testing feedback.

    What's Changed

    • Updated laravel framework to support composer v2 by @quentincaffeino in https://github.com/Attendize/Attendize/pull/936

    Full Changelog: https://github.com/Attendize/Attendize/compare/v2.4.0...v2.5.0

    Source code(tar.gz)
    Source code(zip)
  • v2.4.0(Oct 22, 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 20, 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 12, 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 2, 2020)

  • v2.1.1(Nov 30, 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 2, 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 15, 2016)

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

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

Owner
Attendize
Open-source ticket selling & event management
Attendize
Vuedo is a blog platform, built with Laravel and Vue.js.

Vuedo What is Vuedo? Vuedo is an open source project built with Laravel and Vue.js. It is a live example of how everything works together. Interested

vuedo 2.3k Dec 24, 2022
Deployer is a free and open source deployment tool.

Deployer Deployer is a PHP Application deployment system powered by Laravel 6.0, written & maintained by Stephen Ball. Check out the releases, license

Stephen Ball 886 Dec 15, 2022
📛 An open source status page system for everyone.

Cachet is a beautiful and powerful open source status page system. Overview List your service components Report incidents Customise the look of your s

Cachet 13k Dec 31, 2022
Invoices, Expenses and Tasks built with Laravel and Flutter

Invoice Ninja Hosted | Self-Hosted We're on Slack, join us at slack.invoiceninja.com or if you like StackOverflow Just make sure to add the invoice-ni

Invoice Ninja 6.8k Jan 9, 2023
A Laravel publishing platform

Introduction Canvas is a fully open source package to extend your existing Laravel application and get you up-and-running with a blog in just a few mi

Todd Austin 3.1k Jan 2, 2023
"Student Management System (SMS) is a solution tool that is designed to track, maintain and manage all the data generated by a School, including the grades of a student.

STUDENT-MANAGEMENT-SYSTEM "Student Management System" (SMS) is a solution tool that is designed to track, maintain and manage all the data generated b

SAMBIT RAJ 13 Aug 21, 2021
Simple and Robust solution to manage your software development project

Project moved to GitScrum CE https://github.com/gitscrum-team/GitScrum-Frontend More than 6.600 business use GitScrum to manage their agile projects W

GitScrum 2.8k Jan 8, 2023
Personal CRM. Remember everything about your friends, family and business relationships.

Personal Relationship Manager Monica is a great open source personal relationship management system. Introduction Purpose Features Who is it for? What

Monica 18.5k Jan 2, 2023
Free and Online Accounting Software

Akaunting™ Akaunting is a free, open source and online accounting software designed for small businesses and freelancers. It is built with modern tech

Akaunting 5.8k Dec 27, 2022
The Laravel.io Community Portal.

Laravel.io This is the repository for the Laravel.io community portal. The code is entirely open source and licensed under the MIT license. We welcome

Laravel.io 2.2k Dec 23, 2022
Laravel e-commerce Application.

Antvel Introduction Antvel is an ecommerce project written in Laravel 5.* intended for building a friendly eStore either for startups or big companies

Antvel - Official 650 Dec 28, 2022
Examples of using each Illuminate component in non-Laravel applications

Torch - Using Laravel's Illuminate Components Independently Torch is a project to provide instructions and examples for using Illuminate components as

Matt Stauffer 1.7k Dec 30, 2022
Attendize is an open-source ticketing and event management application built using the Laravel PHP framework

Attendize is an open-source ticketing and event management application built using the Laravel PHP framework. Attendize allows event organisers to sel

Attendize 3.6k Dec 27, 2022
Open source for selling social media accounts or accounts on other platforms.

SELLACC - Open Source Selling Accounts SELLACC is open source for selling social media accounts or accounts on other platforms. ⚠️ We not update sourc

PHAM DUC THANH 6 Nov 17, 2022
A free and open-source Laravel 5.5 and VueJS (SPA) Ticket system

Ticket-conductor A Laravel 5.5 and VueJS (SPA) Ticket system app (This project was mostly for myself to learn Vue Js a bit better, and will not be mai

Casper Bottelet 51 Dec 17, 2022
DooTask is a lightweight open source online project task management tool that provides various document collaboration tools, online mind mapping, online flowcharting, project management, task distribution, instant IM, file management and other tools.

DooTask is a lightweight open source online project task management tool that provides various document collaboration tools, online mind mapping, online flowcharting, project management, task distribution, instant IM, file management and other tools.

kuaifan 3k Jan 5, 2023
MOFHY Lite is a priceless MyOwnFreeHost Client Area for account management, ticket support system and a free ssl service

MOFHY Lite is a priceless MyOwnFreeHost Client Area for account management, ticket support system and a free ssl service. It has easy to use features much like the WHMCS Digit UI interface.

MOFHY Developers 1 Oct 21, 2022
A high-performance license server system service for creating and managing products, major versions, and software licenses for the purpose of selling installable software products.

A high-performance license server system service for creating and managing products, major versions, and software licenses for the purpose of selling installable software products. Comes with a SDK and command-line tool. Works anywhere that PHP runs.

CubicleSoft 32 Dec 5, 2022
Bus ticket booking management system

About Laravel Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experie

Tasnim Farah 2 Jul 8, 2022
Composer Repository Manager for selling Magento 2 extension and offering composer installation for ordered packages.

Magento 2 Composer Repository Credits We got inspired by https://github.com/Genmato. Composer Repository for Magento 2 This extension works as a Magen

EAdesign 18 Dec 16, 2021