Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I would really like to use the EVENTS TICKETING SUITE from Moneyscript. Have tried to contact the owner several times without answer, no way I will send him money and risk to get nothing.
If someone has this module, please can you add it to this project? Thanks!
Comment | File | Size | Author |
---|---|---|---|
#3 | ms_events-7.x-1.3.tar_.gz | 37.94 KB | efruin |
Comments
Comment #2
Farreres CreditAttribution: Farreres commentedWe will happily inclued this module if someone provides us with the source. All modules in this suite have been provided by some user for us to maintain in community.
Comment #3
efruin CreditAttribution: efruin commentedI have the event system code (version 7.x-1.3) but I'm not sure if that is/was the latest version - it's just the latest one I have access to before my license expired with Money Scripts. I would be happy to contribute it to this project so that it can live on.
EDIT: attached file to this post.
Comment #4
Farreres CreditAttribution: Farreres commented@efruin: thanks a lot! As soon as I have time I will process it to include it in moneysuite. There are editions to do. It will be added to the dev version and it will hit stable when we check editions cause no error.
Comment #5
MarcoPBazz CreditAttribution: MarcoPBazz at Bazzmann Agency commentedThat's really cool!
But maybe i'm missing something :-*
I'm getting a strange error with those conditions:
Here's the log error:
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 't.eid' in 'where clause': SELECT t.* FROM {ms_events_tickets} t WHERE (t.entity_id = :db_condition_placeholder_0) AND (t.entity_type = :db_condition_placeholder_1) AND (t.field_name = :db_condition_placeholder_2) AND (t.eid = :db_condition_placeholder_3) ; Array ( [:db_condition_placeholder_0] => 5411 [:db_condition_placeholder_1] => node [:db_condition_placeholder_2] => field_prova_biglietto [:db_condition_placeholder_3] => L6Q1M4B9W6 ) in ms_events_seatmaps_get_event_seats() (linea 735 di /var/www/staging.venipedia.it/sites/all/modules/moneysuite/ms_events/modules/ms_events_seatmaps/ms_events_seatmaps.module).
Comment #6
Farreres CreditAttribution: Farreres commentedI haven't yet included ticketing into suite, so I can't understand where do these errors come from.
Comment #7
Anonymous (not verified) CreditAttribution: Anonymous commentedI also would love to have this module :D
I can test if you need ;)
Best regards
ArchGalileu
Comment #8
Farreres CreditAttribution: Farreres commentedOk, today I start working on this. I hope to have it available soon in dev. I will update this issue when done. The 1.3 version is the latest one.
Comment #9
Farreres CreditAttribution: Farreres commentedTicketing suite has been added to dev version. Please, could someone test everything is working ok?
Comment #10
Anonymous (not verified) CreditAttribution: Anonymous commentedI will test ;)
Saying something later ;)
Best regards
ArchGalileu
Comment #11
Anonymous (not verified) CreditAttribution: Anonymous commentedHello
I can add the seats plan :)
But when i add a "Events" field to content than when gives the following error
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 't.eid' in 'where clause': SELECT t.* FROM {ms_events_tickets} t WHERE (t.entity_id = :db_condition_placeholder_0) AND (t.entity_type = :db_condition_placeholder_1) AND (t.field_name = :db_condition_placeholder_2) AND (t.eid = :db_condition_placeholder_3) ; Array ( [:db_condition_placeholder_0] => 2 [:db_condition_placeholder_1] => node [:db_condition_placeholder_2] => field_comprar_bilhete [:db_condition_placeholder_3] => P5C2A7Y9J2 ) in ms_events_seatmaps_get_event_seats() (line 737 of /srv/http/money/drupal/sites/all/modules/moneysuite/ms_events/modules/ms_events_seatmaps/ms_events_seatmaps.module).
:(
Best regards
ArchGalileu
Comment #12
Farreres CreditAttribution: Farreres commentedFrom the error it looks like the database table hasn't been installed. The problem you are having is related to a database column that is not there. Could you please check your database and see what tables you have in it? When you installed did you execute update.php? Can you check the logs to see if there was some error when executing .install file?
Comment #13
anahatadesign CreditAttribution: anahatadesign commentedHI
just setting up Events Ticketing Suite on a a site to test.
i am removing the following error on the event page. any ideas?
trict warning: Only variables should be passed by reference in ms_events_basic_field_formatter_view() (line 119 of .../sites/all/modules/ms_events/modules/ms_events_basic/ms_events_basic.module).
any help would be great
Comment #14
Farreres CreditAttribution: Farreres commented@anahatadesign: I have been checking what does this error mean. I have found this page: http://stackoverflow.com/questions/2354609/strict-standards-only-variabl...
As I see in https://api.drupal.org/api/drupal/includes!common.inc/function/drupal_re... function drupal_render uses a parameter by reference: 7 common.inc drupal_render(&$elements) but in the original code the parameter is a function, not a variable.
I suggest you to do this change:
edit file ms_events/modules/ms_events_basic/ms_events_basic.module
go to line 119
change
into
If this corrects the error, please reply in this thread and I will apply this edition to dev.
Comment #15
Anonymous (not verified) CreditAttribution: Anonymous commentedIt persists Farreres
I will test at home, day 5 April, and i post the code error
Best regards
ArchGalileu
Comment #16
hansvaneylen CreditAttribution: hansvaneylen as a volunteer commentedHi Farreres,
thanks for including this module in MoneySuite ! I did some testing today :
I was able to create a Seating Map and Ticket Types.
The content type was easily created.
Upon creating actual content, I got the same Strict warning but on a different module :
Strict warning: Only variables should be passed by reference in ms_events_seatmaps_field_formatter_view() (line 713 of C:\Users\Administrator\Sites\devdesktop\drupal-7.43\sites\all\modules\ms_events\modules\ms_events_seatmaps\ms_events_seatmaps.module).
When I changed this to
That problem went away. I didn't need to change anything in the ms_events/modules/ms_events_basic/ms_events_basic.module. However as soon as I change the "Registration Opens" date to a day in the past, I get the error about missing columns/tables :
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 't.eid' in 'where clause': SELECT t.* FROM {ms_events_tickets} t WHERE (t.entity_id = :db_condition_placeholder_0) AND (t.entity_type = :db_condition_placeholder_1) AND (t.field_name = :db_condition_placeholder_2) AND (t.eid = :db_condition_placeholder_3) ; Array ( [:db_condition_placeholder_0] => 5 [:db_condition_placeholder_1] => node [:db_condition_placeholder_2] => field_toegangskaarten [:db_condition_placeholder_3] => E8L8S3Q1W4 ) in ms_events_seatmaps_get_event_seats() (line 741 of C:\Users\Administrator\Sites\devdesktop\drupal-7.43\sites\all\modules\ms_events\modules\ms_events_seatmaps\ms_events_seatmaps.module).
I tried to run update.php but it did not create any tables.
Hans
Comment #17
Anonymous (not verified) CreditAttribution: Anonymous commentedHello Farreres
Same to me, i confirm that a date before gives the following error
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 't.eid' in 'where clause': SELECT t.* FROM {ms_events_tickets} t WHERE (t.entity_id = :db_condition_placeholder_0) AND (t.entity_type = :db_condition_placeholder_1) AND (t.field_name = :db_condition_placeholder_2) AND (t.eid = :db_condition_placeholder_3) ; Array ( [:db_condition_placeholder_0] => 6 [:db_condition_placeholder_1] => node [:db_condition_placeholder_2] => field_comprar_bilhete [:db_condition_placeholder_3] => G7H4F6E1R8 ) in ms_events_seatmaps_get_event_seats() (line 737 of drupal/sites/all/modules/moneysuite/ms_events/modules/ms_events_seatmaps/ms_events_seatmaps.module).
Also confirm the the error
Notice: Only variables should be passed by reference in ms_events_seatmaps_field_formatter_view() (line 713 of drupal/sites/all/modules/moneysuite/ms_events/modules/ms_events_seatmaps/ms_events_seatmaps.module).
But can't understand how to change hansvaneylen
Waiting for instructions
Best regards
ArchGalileu
Comment #18
Farreres CreditAttribution: Farreres commentedOk. Probably I will have to add a database update for adding the missing tables and columns. I can't understand why the original module was so much buggy.
I will also apply the edition related to drupal_render to dev version.
Now it is too late, tomorrow in the morning I will look at this.
Comment #19
Farreres CreditAttribution: Farreres commentedI have updated the files to correct the errror
Notice: Only variables should be passed by reference in
I hope this solves the problem.About the other problen with eid
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 't.eid' in 'where clause': SELECT t.* FROM {ms_events_tickets}
I have checked the install file and there are a lot of updates related to eid field. The only thing I could find is that in the schema function there was no reference to eid field, although this reference was present in the modules. I have added the field for ms_events_tickets and let's hope this solves the problem. Please check and confirm this is solving the issue.Comment #20
MarcoPBazz CreditAttribution: MarcoPBazz at Bazzmann Agency commentedHi Farreres,
I've just checked out latest version on a fresh install and it seem that both problems are gone (either with Ticketed Event with Seating Chart's field than Ticketed Event's field).
Thanks!
Comment #21
hansvaneylen CreditAttribution: hansvaneylen as a volunteer commentedHi Farreres,
I just tried the latest version as well and can confirm that both issues have been solved.
Thanks!
Comment #22
Farreres CreditAttribution: Farreres commentedPerfect. Please, try the module and if no more bugs are found I will generate a new stable version with the added module. But first let's make sure there are no more bugs.
Comment #23
jasonaaronwood CreditAttribution: jasonaaronwood commentedThank you for putting all this together Farreres. I'm still using the Moneyscripts versions but in the next week or so I'll try the upgrade.
Comment #24
MarcoPBazz CreditAttribution: MarcoPBazz at Bazzmann Agency commentedAfter other benchmarks I didn't find any other bugs
Comment #25
Anonymous (not verified) CreditAttribution: Anonymous commentedI will test this weekend ;)
Great work
Thank you very much
Best regards
ArchGalileu
Comment #26
Farreres CreditAttribution: Farreres commentedIt seems there are many evidences that ticketing suite in moneyscripts works smoothly. Time to generate a new stable version with this new module.
Comment #27
Solarisserv CreditAttribution: Solarisserv as a volunteer and commentedHello ,
As I am looking for the dev version , I notice the following
7.x-10.x-dev tar.gz (978.38 KB) | zip (1.22 MB) 2015-Dec-27 - not sure the dates match to this conversation , please let me know which dev version are we talking about ..
Comment #28
Farreres CreditAttribution: Farreres commentedYes. I am in fact not very acquainted with git. The updates are in debian git but I don't know where, because they are not in stable nor in dev...
Anyone know what should I do after creating a stable release to go back to dev release?
Comment #29
Farreres CreditAttribution: Farreres commentedIf I didn't do anything wrong, in some hours we should have a stable release including events ticketing suite.
Now, I don't know what I should do so that dev version gets refreshed because it is still showing an outdated dev version. Any help?
Comment #30
Farreres CreditAttribution: Farreres commented