Attendize is an open-source ticketing and event management application built using the Laravel PHP framework

Last update: May 19, 2022

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.

GitHub

https://github.com/attendize/attendize
Comments
  • 1. 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.

    Reviewed by sipak at 2016-07-04 17:13
  • 2. 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

    Reviewed by angrydogmedi at 2016-12-09 13:14
  • 3. 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

    Reviewed by cpalop at 2017-01-28 13:54
  • 4. 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?

    Reviewed by yhorian at 2016-03-14 16:11
  • 5. 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

    Reviewed by harshit1235 at 2019-04-04 14:06
  • 6. [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!

    Reviewed by storca at 2021-11-03 16:30
  • 7. 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

    Reviewed by Leen15 at 2018-07-13 12:31
  • 8. 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.

    Reviewed by markwalet at 2016-03-10 01:22
  • 9. [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.

    Reviewed by jimrome at 2020-10-20 16:51
  • 10. 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

    Reviewed by CristianDeluxe at 2019-09-20 04:46
  • 11. Strong Customer Authentication | Stripe

    Hi,

    I am not a developer, but I would like to ask my developer to work on Strong Customer Authentication in Stripe to ensure two-factor authentication, either as a separate checkout page or within the Attendize payment flow via the Payment Intents API.

    I would like to know if there is someone else working on this feature in the Attendize community.

    Reviewed by CiaranTuvens at 2019-07-25 09:19
  • 12. [FEEDBACK] Used Attendize for two big events!

    I've set up Attendize for two big events, one at ~1000 people, the other one was at ~6000 tickets sold. In those two events, I needed to use the branch feature-roles-and-permissions for the volunteers to scan tickets without accessing other functionalities of Attendize.

    Here's what came back of it, ordered from the most problematic, to the least

    • Disable development mode in production... Don't forget it please...

    • The scan of the QR Codes highly depends on the conditions of the day ! If there's sun, if the phone's screen is broken it doesn't work! Scan on printed tickets works. Ideas : Change the QR Code scanning library ; develop some kind of hardware for the 1D barcodes, with the API It would be fun to do

    • The scan page lags The scan page is a bit unstable : out of the +50 people that scanned tickets, it was clear that the page worked for some time, but then is starts lagging quite a lot (delays when pressing the QRCode button, the image of the camera lags, stops, stays black, ...) There may be maintenance work to do around here!

    • Access codes It would have saved me hours (not joking) if there was a limit on how much tickets can a access code order.

    • PDF documents Questions were very usefull! But uploading documents would be a great addition, we lacked this functionality a lot and had to work with Google Drive. Idea : As in Google's own file system, a unique time-based hash is generated for each file, file is renamed to this hash and is publicly accessible. The file's hash is set as answer_text in question_answers

    • Load-Balanced environment With a HTTPS proxy, the setup is a bit tricky, you have to edit the URL generator to force https on the node's side, once that's done it works!

    Attendize is great sotware! It just needs a bit more attention It's a bit buggy sometimes BUT these minor issues can be worked around easily and don't compromise the overall function of Attendize. The database design is well done and can be understood easily. Attendize truly saved me a lot of time with the refunds, once my patch with Stripe was applied.

    I'll add more things here if I remember more

    Thanks again to all the community of contributors who helped in any way!

    Reviewed by storca at 2022-05-27 16:23
  • 13. [BUG] Whoops!, it looks like the server returned an error. Please try again, or contact the webmaster if the problem persists.

    Describe the bug A clear and concise description of what the bug is. dummy payment or Pay using offline methods or if ticket is free same error To Reproduce Steps to reproduce the behavior: after enable the debug in .env I got 1 error with payment-gateway but now stuck with this error Whoops!, it looks like the server returned an error. Please try again, or contact the webmaster if the problem persists. but the ticket subscription is registered in CPanel

    i have tried to make changes in /config/session but nothing happen

    log [2022-05-26 13:56:53] production.ERROR: Undefined index: order_requires_payment {"userId":1,"exception":"[object] (ErrorException(code: 0): Undefined index: order_requires_payment at location/Attendize/app/Http/Controllers/EventCheckoutController.php:400) [stacktrace] #0 location/Attendize/app/Http/Controllers/EventCheckoutController.php(400): Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(8, 'Undefined index...', '/www/e....', 400, Array) #1 [internal function]: App\Http\Controllers\EventCheckoutController->postCreateOrder(Object(Illuminate\Http\Request), '1') #2 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): call_user_func_array(Array, Array) #3 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(45): Illuminate\Routing\Controller->callAction('postCreateOrder', Array) #4 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Route.php(219): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(App\Http\Controllers\EventCheckoutController), 'postCreateOrder') #5 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Route.php(176): Illuminate\Routing\Route->runController() #6 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Router.php(681): Illuminate\Routing\Route->run() #7 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(130): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request)) #8 location/Attendize/vendor/mcamara/laravel-localization/src/Mcamara/LaravelLocalization/Middleware/LaravelLocalizationViewPath.php(33): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #9 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Mcamara\LaravelLocalization\Middleware\LaravelLocalizationViewPath->handle(Object(Illuminate\Http\Request), Object(Closure)) #10 location/Attendize/vendor/mcamara/laravel-localization/src/Mcamara/LaravelLocalization/Middleware/LaravelLocalizationRedirectFilter.php(45): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #11 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Mcamara\LaravelLocalization\Middleware\LaravelLocalizationRedirectFilter->handle(Object(Illuminate\Http\Request), Object(Closure)) #12 location/Attendize/vendor/mcamara/laravel-localization/src/Mcamara/LaravelLocalization/Middleware/LocaleSessionRedirect.php(64): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #13 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Mcamara\LaravelLocalization\Middleware\LocaleSessionRedirect->handle(Object(Illuminate\Http\Request), Object(Closure)) #14 location/Attendize/app/Http/Middleware/SetViewVariables.php(44): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #15 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): App\Http\Middleware\SetViewVariables->handle(Object(Illuminate\Http\Request), Object(Closure)) #16 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php(41): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #17 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure)) #18 location/Attendize/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php(76): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #19 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure)) #20 location/Attendize/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php(49): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #21 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure)) #22 location/Attendize/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(56): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #23 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure)) #24 location/Attendize/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #25 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure)) #26 location/Attendize/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(66): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #27 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure)) #28 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(105): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #29 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Router.php(683): Illuminate\Pipeline\Pipeline->then(Object(Closure)) #30 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Router.php(658): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request)) #31 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Router.php(624): Illuminate\Routing\Router->runRoute(Object(Illuminate\Http\Request), Object(Illuminate\Routing\Route)) #32 location/Attendize/vendor/laravel/framework/src/Illuminate/Routing/Router.php(613): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request)) #33 location/Attendize/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(170): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request)) #34 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(130): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request)) #35 location/Attendize/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #36 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure)) #37 location/Attendize/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #38 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure)) #39 location/Attendize/vendor/fideloper/proxy/src/TrustProxies.php(57): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #40 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure)) #41 location/Attendize/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #42 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure)) #43 location/Attendize/app/Http/Middleware/GeneralChecks.php(26): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #44 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): App\Http\Middleware\GeneralChecks->handle(Object(Illuminate\Http\Request), Object(Closure)) #45 location/Attendize/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(63): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #46 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure)) #47 location/Attendize/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(105): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request)) #48 location/Attendize/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(145): Illuminate\Pipeline\Pipeline->then(Object(Closure)) #49 location/Attendize/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(110): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request)) #50 location/Attendize/public/index.php(55): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request)) #51 {main} "}

    thanks

    Reviewed by el3ashe2 at 2022-05-26 13:33
  • 14. [BUG] Install via Softaculous does not work

    Describe the bug I have a webhost with CPanel and Softaculous. In Softaculous I searched for Attendize and clicked install. First I got an error saying that the fileinfo php extension was missing. I fixed this by enabling it in CPanel. After that I clicked install again.

    The install took about 1 minute and I was shown a screen which said 'Congratulations, the software was installed successfully' and it showed me two links, one with [domain]/public and one with [domain]/public/login. When I open any of the links I get a blank page with the message 'This page isn’t working right now' and it shows 'HTTP ERROR 500'. I opened the developers tool but didn't find any thing in the request responses. I also looked in the logs but could not find an error.

    I once installed Attendize locally via Docker and I remember after installation I had to go through a config on localhost:8080/install. When I go to [domain]/install or [domain]/public/install I get a 404.

    Does anyone know what I can try to do to resolve the issue? Thanks in advance!

    Version of Attendize you are using

    • 2.4.0

    Where you are running Attendize

    • Webhost

    What version of PHP you are using on the above server

    • 8.0
    Reviewed by KevinBrok at 2022-05-24 21:07
  • 15. Is anyone getting any support?

    I would like to purchase a license but I'm concerned that there is no activity happening with the project in github. I emailed the [email protected] address only to get a reply that their email configuration is wrong and the message is not delivered. I've also tried to message the two owners via twitter and other means without any success.

    33 open PRs and 207 issues, most recently one indicating that stripe transactions are being rejected 50% of the time...

    I will have a php developer building web services to support the creation of events/tickets remotely which I would consider contributing.

    I'm just pinging you here to see if you are alive.

    It is a very well done project and will be hoping to leverage it soon. Is there a reason these pull requests aren't moving forward?

    Reviewed by gainer-twister at 2022-03-16 09:52
  • 16. [FEATURE] can someone help me integrate a main layout with attendize?

    I have a front-end project for a website with several events, would it be possible for someone to integrate this layout with the attendize platform? If so, what would be the budget for this?

    Grateful.

    Reviewed by levycamara at 2022-02-13 17:16
An open source Laravel Soundboard with Admin Panel CRUD (Create Read Update Delete) built on Laravel, Bootstrap, and Vue.js
An open source Laravel Soundboard with Admin Panel CRUD (Create Read Update Delete) built on Laravel, Bootstrap, and Vue.js

Laravel Soundboard An open source Laravel Soundboard with Admin Panel CRUD (Create Read Update Delete) built on Laravel 5.8, Bootstrap 4, Vue.js, Boot

Jan 10, 2022
ergodnc (Ergonomic Desk & Coffee) is an open source Laravel project that's being built live on the official Laravel YouTube Channel

About This Project ergodnc (Ergonomic Desk & Coffee) is an open source Laravel project that's being built live on the official Laravel YouTube Channel

May 15, 2022
Free and open-source Laravel admin dashboard interface built with Livewire & Alpine.js based on Bootstrap 5
Free and open-source Laravel admin dashboard interface built with Livewire & Alpine.js based on Bootstrap 5

Volt Dashboard Laravel Free Frontend Web App for Laravel with Livewire & Alpine.js Never start a development project from scratch again. We've partner

May 21, 2022
PlayZ is an esport event organization and management website allowing the creation of tournaments on the most popular video games of the esport scene.

PlayZ the playz to play Table of Contents Description "What is Playz?" In one sentence PlayZ is "an esport event organization and management website a

Dec 7, 2021
Freelancer notes is an open source web application

#What is Freelancer Notes Freelancer Note is an freelance project management application. It is very light weight and easy to use. You are able to man

Sep 4, 2021
Manage your staff from one place. Featuring Staff leave management 🏖, payslips 💵 generation & emailing, messaging 📨and more 🛠! Built with ❤️ with Laravel

Staff Management System This little buddy can help you manage your staff database! Built with ?? with Laravel #FEATURES 1 Staff management/ database S

Apr 6, 2022
An issue tracking tool based on laravel+reactjs for small and medium-sized enterprises, open-source and free, similar to Jira.
An issue tracking tool based on laravel+reactjs for small and medium-sized enterprises, open-source and free, similar to Jira.

ActionView English | 中文 An issue tracking tool based on php laravel-framework in back-end and reactjs+redux in front-end, it's similar to Jira. You co

May 27, 2022
Laravel application project as Sheina Online Store backend to be built with Laravel and VueJS

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

Jan 11, 2022
Transaction-aware Event Dispatcher for Laravel

Transaction-aware Event Dispatcher for Laravel This Laravel package introduces Transaction-aware Event Dispatcher. It ensures the events dispatched wi

May 13, 2022
A simple Laravel event log package for easy model based logging.

Karacraft Logman A simple Model Event Logging Package Usage Installation composer require karacraft/logman Migrate php artisan migrate Publish php a

Dec 28, 2021
A minimalistic event calendar Tool for Laravel's Nova 4
A minimalistic event calendar Tool for Laravel's Nova 4

Event calendar for Laravel Nova 4 An event calendar that displays Nova resources or other time-related data in your Nova 4 project on a monthly calend

May 5, 2022
Laravel Event Visualizer
Laravel Event Visualizer

Laravel package to visualize events with their handlers, including jobs to chain them together.

May 9, 2022
An Easy, Customizable & Open Source Robux Rewards Website Made With Laravel
An Easy, Customizable & Open Source Robux Rewards Website Made With Laravel

RbxDream - Robux Earning Rewards Website Coming Soon Current repo not stable. This is an open source Robux rewards site. Understanding Core Concepts T

Feb 15, 2022
This is an open source demo of administration panel for polymorphic relationship and SEO content

Laravel SEO admin This application demonstrates usage of polymorphic relationships described at (http://maxoffsky.com/code-blog/using-polymorphic-rela

Mar 3, 2022
A simple blog app where a user can signup , login, like a post , delete a post , edit a post. The app is built using laravel , tailwind css and postgres

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

Mar 6, 2022
A lightweight domain event pattern implementation for Doctrine2.
A lightweight domain event pattern implementation for Doctrine2.

Knp Rad Domain Event A lightweight domain event pattern implementation for Doctrine2. Official maintainers: @Einenlum Installation With composer : $ c

Aug 23, 2018
An event stream library based on tail

TailEventStream An event stream library based on tail. Note: I don't think you should use this library in a real project, but it's great for education

Feb 19, 2022
Open source Unifi controller

imperian-systems/unifi-controller Note: This package is backend only, no user interface is included Install snappy PHP extension https://github.com/kj

Mar 24, 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

May 25, 2022