# إضافة أحداث أنغوس 📅
**URL:** https://meta.discourse.org/t/angus-events-plugin/69776
**Category:** Plugin
**Created:** [11 سبتمبر 2017، 2:44ص UTC](https://meta.discourse.org/t/angus-events-plugin/69776 "2017-09-11T02:44:59Z")
**Posts on this page:** 20
**Page:** 24
### Author:  [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [29 مايو 2019، 5:44م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/467 "2019-05-29T17:44:32Z")
I’d also like to able to filter events by tags. If you use the nav bar tag filter, it works only for the agenda view, not for the calendar and maps view. ☹
But that’s really complaining on a high level. I’ve just used the plugin on my site for the first time and its fantastic!
Edit: even better, if you could also negate tags, for instance “show me all events except those tagged ‘panel-discussion’”. And then the question becomes, can you do that with combinations of multiple tags? And could it also work for calendar subscriptions?
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [31 مايو 2019، 12:20ص UTC](https://meta.discourse.org/t/angus-events-plugin/69776/468 "2019-05-31T00:20:11Z")
All good suggestions!
If you could make a formal feature request (and get @outofthebox and a couple of others to vote for it) I can add it into my workflow.
[https://discourse.angusmcleod.com.au/w/feature-request](https://discourse.angusmcleod.com.au/w/feature-request) (requires an account on my sandbox)
Cheers,
Angus
---
### Author:  [@jdaviescoates](https://meta.discourse.org/u/jdaviescoates)
#### Post date: [10 يونيو 2019، 6:02م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/469 "2019-06-10T18:02:41Z")
This great plugin has recently been installed over at [https://community.coops.tech](https://community.coops.tech) and I came here to ask that the date format be customisable, so very happy to discover it already is, thanks! 😃
I guess I’ll now just ask our admins to change it! 😛
---
### Author:  [@md-misko](https://meta.discourse.org/u/md-misko)
#### Post date: [12 يونيو 2019، 7:27ص UTC](https://meta.discourse.org/t/angus-events-plugin/69776/471 "2019-06-12T07:27:55Z")
There is an issue with the MIME type in the webcal generated link that prevents calendar from displaying events when imported into Office 365 calendar (Google calendar displays the events regardless).
Here’s the report from the validator:
> **[iCalendar.org](https://icalendar.org/validator.html?url=https:%2F%2Fdiscourse.angusmcleod.com.au%2Fc%2Fpublic-work%2Fl%2Fcalendar.ics?time_zone=Australia%2FMelbourne)**
>
> This site is devoted to promoting the iCalendar standard, which includes specifications, resources, a validation tool and PHP library. iCalendar is an open stan
> Invalid MIME type detected, should be ‘text/calendar’ (found MIME type ‘text/plain; charset=utf-8’) near line # 1
> Reference: RFC 5545 8.1. iCalendar Media Type Registration
On a side note: thank you for the fantastic work on this plugin! I’m eagerly awaiting the feature to add reminders to events, what is the current status on this?
---
### Author:  [@Globulle](https://meta.discourse.org/u/Globulle)
#### Post date: [12 يونيو 2019، 5:18م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/472 "2019-06-12T17:18:44Z")
Hi @angus, it seems to work very well. I have some extra feature requests:
- **having the link to the topic in the description of the event.** Something like : _More info at [https://meta.discourse.org/t/events-plugin-calendar/69776](https://meta.discourse.org/t/events-plugin-calendar/69776)_
- **keeping the Discourse category as a Webcal event category** : it would allow the different events to be clearly distinguished. In the same logic, the geographic position could also be embedded… see [RFC 5545 - Internet Calendaring and Scheduling Core Object Specification (iCalendar)](https://tools.ietf.org/html/rfc5545)
- last killing feature **embedding the attendees list** to allow people to notice their presence directly from their calendar manager. 😉
EDIT : I have created some feature requests on Angus’ Sandbox for these proposals as suggested by @Ellibereth:
- [https://discourse.angusmcleod.com.au/t/events-embed-link-to-original-topic-in-webcal-event/1117](https://discourse.angusmcleod.com.au/t/events-embed-link-to-original-topic-in-webcal-event/1117)
- [https://discourse.angusmcleod.com.au/t/events-add-location-to-webcal-event/1118](https://discourse.angusmcleod.com.au/t/events-add-location-to-webcal-event/1118)
- [https://discourse.angusmcleod.com.au/t/events-transfer-discourse-category-in-webcal-events/1119](https://discourse.angusmcleod.com.au/t/events-transfer-discourse-category-in-webcal-events/1119)
- [https://discourse.angusmcleod.com.au/t/events-allowing-people-to-respond-to-an-event-from-webcal/1120](https://discourse.angusmcleod.com.au/t/events-allowing-people-to-respond-to-an-event-from-webcal/1120)
Hope they are clear enough, thank you for the work!
---
### Author:  [@Ellibereth](https://meta.discourse.org/u/Ellibereth)
#### Post date: [12 يونيو 2019، 8:20م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/473 "2019-06-12T20:20:02Z")
> [@jdaviescoates](#):
>
> This great plugin has recently been installed over at [https://community.coops.tech](https://community.coops.tech) and I came here to ask that the date format be customisable, so very happy to discover it already is, thanks! 😃
Glad to hear @jdaviescoates! Let us know how it goes!
> [@md-misko](#):
>
> There is an issue with the MIME type in the webcal generated link that prevents calendar from displaying events when imported into Office 365 calendar (Google calendar displays the events regardless).
We’ll take a look at this @md-misko - in the interim can you submit a [bug report](https://discourse.angusmcleod.com.au/w/bug-report/steps/plugin)?
> [@md-misko](#):
>
> On a side note: thank you for the fantastic work on this plugin! I’m eagerly awaiting the feature to add reminders to events, what is the current status on this?
I’m not 100% sure, will check and get back to you.
> [@Globulle](#):
>
> Hi @angus, it seem to work very well. I have some extra feature requests:
>
> - **having the link to the topic in the description of the event.** Something like : _More info at [Events Plugin 📅](https://meta.discourse.org/t/events-plugin-calendar/69776)_
> - **keeping the Discourse category as a Webcal event category** : it would allow the different events to be clearly distinguished. In the same logic, the geographic position could also be embedded… see [RFC 5545 - Internet Calendaring and Scheduling Core Object Specification (iCalendar)](https://tools.ietf.org/html/rfc5545)
> - last killing feature **embedding the attendees list** to allow people to notice their presence directly from their calendar manager. 😉
Hey @Globulle, these are great ideas. Would you mind submitting [feature requests](https://discourse.angusmcleod.com.au/w/feature-request/steps/step_1_1) for them? Link us to them here so we can go vote for them!
---
### Author:  [@jdaviescoates](https://meta.discourse.org/u/jdaviescoates)
#### Post date: [12 يونيو 2019، 9:54م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/474 "2019-06-12T21:54:27Z")
> [@Ellibereth](#):
>
> > This great plugin has recently been installed over at [https://community.coops.tech](https://community.coops.tech) and I came here to ask that the date format be customisable, so very happy to discover it already is, thanks! 😃
>
> Glad to hear @jdaviescoates! Let us know how it goes!
[https://community.coops.tech/](https://community.coops.tech/) now has much clearer dates, thanks! (and I’m now and admin too, so can tweak further if I so choose! 😛 )
---
### Author:  [@csmu](https://meta.discourse.org/u/csmu)
#### Post date: [12 يونيو 2019، 10:12م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/475 "2019-06-12T22:12:42Z")
> [@md-misko](#):
>
> Invalid MIME type detected, should be ‘text/calendar’ (found MIME type ‘text/plain; charset=utf-8’) near line # 1
> Reference: RFC 5545 8.1. iCalendar Media Type Registration
That explains why Mac OSX Calendar says the format is invalid 🙂
```plaintext
Problem! Found 1 warning
Warnings
Invalid MIME type detected, should be 'text/calendar' (found MIME type 'text/html') near line # 1
Reference: RFC 5545 8.1. iCalendar Media Type Registration
Problem! Found 2 errors
Errors
This is not an iCalendar file or URL near line # 1
Reference: RFC 5545 3.4. iCalendar Object
Missing VCALENDAR object near line # 1
Reference: RFC 5545 3.4 iCalendar Object
Permalink: https://icalendar.org/validator.html?url=http://discourse.bd2l.com.au/c/cottage-singers/cs-concerts/l/calendar.ics?time_zone=Australia/Adelaide
Permalinks are available when validating by URL. You can use a permalink to send a link of the validation results page using e-mail or web posting.
JSON Permalink: https://icalendar.org/validator.html?url=http://discourse.bd2l.com.au/c/cottage-singers/cs-concerts/l/calendar.ics?time_zone=Australia/Adelaide&json=1
The JSON permalink formats the validation results in JSON format, which can be used by other programs for further analysis.
```
---
### Author:  [@Globulle](https://meta.discourse.org/u/Globulle)
#### Post date: [13 يونيو 2019، 12:06م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/476 "2019-06-13T12:06:56Z")
> [@Ellibereth](#):
>
> Would you mind submitting [feature requests](https://discourse.angusmcleod.com.au/w/feature-request/steps/step_1_1) for them? Link us to them here so we can go vote for them!
Done. I’ve edited my post to add the links: [Events Plugin 📅 - #472 by Globulle](https://meta.discourse.org/t/events-plugin-calendar/69776/472)
---
### Author:  [@md-misko](https://meta.discourse.org/u/md-misko)
#### Post date: [13 يونيو 2019، 1:44م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/477 "2019-06-13T13:44:25Z")
> [@Ellibereth](#):
>
> in the interim can you submit a [bug report](https://discourse.angusmcleod.com.au/w/bug-report/steps/plugin)?
Would you be so kind and submit the bug report for me?
I tried to register on the Sandbox but I couldn’t—I never received the confirmation e-mail (it is not in spam folder either), even after multiple retries. Could you check the SMTP logs on your side?
---
### Author:  [@Ellibereth](https://meta.discourse.org/u/Ellibereth)
#### Post date: [14 يونيو 2019، 7:04ص UTC](https://meta.discourse.org/t/angus-events-plugin/69776/478 "2019-06-14T07:04:47Z")
> [@Globulle](#):
>
> Done. I’ve edited my post to add the links: [Events Plugin 📆](https://meta.discourse.org/t/events-plugin-calendar/69776/472)
Thanks @Globulle 👍
> [@md-misko](#):
>
> Would you be so kind and submit the bug report for me?
>
> I tried to register on the Sandbox but I couldn’t—I never received the confirmation e-mail (it is not in spam folder either), even after multiple retries. Could you check the SMTP logs on your side?
Sorry about that @md-misko, I think this was a case of Outlook not behaving well with certain email services - I’ll check with angus but I’m not sure what the long term solution is. (Seen mentions of this pop up around meta every once in a while).
I validated your account manually so you should be able to log in and submit the report - let me know if you still run into any issues.
> [@md-misko](#):
>
> On a side note: thank you for the fantastic work on this plugin! I’m eagerly awaiting the feature to add reminders to events, what is the current status on this?
This has been slotted to be worked on in a couple of weeks per [https://discourse.angusmcleod.com.au/t/add-event-reminders/879](https://discourse.angusmcleod.com.au/t/add-event-reminders/879).
---
### Author:  [@md-misko](https://meta.discourse.org/u/md-misko)
#### Post date: [14 يونيو 2019، 7:29ص UTC](https://meta.discourse.org/t/angus-events-plugin/69776/479 "2019-06-14T07:29:46Z")
> [@Ellibereth](#):
>
> I validated your account manually so you should be able to log in and submit the report - let me know if you still run into any issues.
Thanks, it’s working now, bug report filed as
[https://discourse.angusmcleod.com.au/t/incorrect-mime-type-in-the-webcal-generated-link/1128](https://discourse.angusmcleod.com.au/t/incorrect-mime-type-in-the-webcal-generated-link/1128)
> [@Ellibereth](#):
>
> This has been slotted to be worked on in a couple of weeks
❤
---
### Author:  [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [20 يونيو 2019، 9:57م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/480 "2019-06-20T21:57:33Z")
> [@tomtjes](#):
>
> I’d also like to able to filter events by tags.
There’s finally a feature request for this. Please vote!
[https://discourse.angusmcleod.com.au/t/events-tag-filter-in-calendar-and-maps-views/1165](https://discourse.angusmcleod.com.au/t/events-tag-filter-in-calendar-and-maps-views/1165)
---
### Author:  [@Jeremie\_Leroy](https://meta.discourse.org/u/Jeremie_Leroy)
#### Post date: [9 يوليو 2019، 8:33م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/481 "2019-07-09T20:33:02Z")
مرحبًا بالجميع،
أعتقد أن هناك خللًا في إضافة الفعاليات، هل لديكم أي فكرة؟
---
### Author:  [@SDKAAA](https://meta.discourse.org/u/SDKAAA)
#### Post date: [11 يوليو 2019، 10:43ص UTC](https://meta.discourse.org/t/angus-events-plugin/69776/482 "2019-07-11T10:43:44Z")
Is the bellow error related to this plugin? (also posted [here](https://meta.discourse.org/t/topic-in-a-category-make-unreachable-the-category-and-user-activity-and-the-topic-itself/122644))
a user created a topic by copy pasting some content from a facebook page; this has crashed the topic iteslf, the category and his activities page. (the rest of the topics and categories of the site remained accessible)
I managed to destroy the topic from the console and everything went back to normal for the user and category.
Is this error related to the mentioned plugin [“discourse-events”](https://meta.discourse.org/t/events-plugin-calendar/69776)?
here follows the errors:
_info:_
```plaintext
NoMethodError (undefined method `nonzero?' for [1564826442, 1564826442]:Array)
/var/www/discourse/plugins/discourse-events/plugin.rb:155:in `has_event?'
```
_backtrace:_
```plaintext
/var/www/discourse/plugins/discourse-events/plugin.rb:155:in `has_event?'
/var/www/discourse/plugins/discourse-events/plugin.rb:223:in `include_event?'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/active_model_serializers-0.8.4/lib/active_model/serializer.rb:375:in `include?'
(eval):59:in `_fast_attributes'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/active_model_serializers-0.8.4/lib/active_model/serializer.rb:468:in `rescue in attributes'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/active_model_serializers-0.8.4/lib/active_model/serializer.rb:455:in `attributes'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/active_model_serializers-0.8.4/lib/active_model/serializer.rb:480:in `_serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/active_model_serializers-0.8.4/lib/active_model/serializer.rb:359:in `serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/active_model_serializers-0.8.4/lib/active_model/serializer.rb:347:in `as_json'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/json/encoding.rb:22:in `encode'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/json/encoding.rb:22:in `encode'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/core_ext/object/json.rb:41:in `to_json'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/active_model_serializers-0.8.4/lib/active_model/serializer.rb:331:in `to_json'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/multi_json-1.13.1/lib/multi_json/adapters/oj.rb:40:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/multi_json-1.13.1/lib/multi_json/adapters/oj.rb:40:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/multi_json-1.13.1/lib/multi_json/adapter.rb:25:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/multi_json-1.13.1/lib/multi_json.rb:139:in `dump'
/var/www/discourse/app/controllers/topics_controller.rb:946:in `block (2 levels) in perform_show_response'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal/mime_responds.rb:203:in `respond_to'
/var/www/discourse/app/controllers/topics_controller.rb:943:in `perform_show_response'
/var/www/discourse/app/controllers/topics_controller.rb:131:in `show'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/abstract_controller/base.rb:194:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal/rendering.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/abstract_controller/callbacks.rb:42:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/callbacks.rb:132:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/abstract_controller/callbacks.rb:41:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal/rescue.rb:22:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal/instrumentation.rb:34:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/notifications.rb:168:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/notifications/instrumenter.rb:23:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/notifications.rb:168:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal/instrumentation.rb:32:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal/params_wrapper.rb:256:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/railties/controller_runtime.rb:24:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/abstract_controller/base.rb:134:in `process'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionview-5.2.3/lib/action_view/rendering.rb:32:in `process'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-mini-profiler-1.0.2/lib/mini_profiler/profiling_methods.rb:104:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal.rb:191:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_controller/metal.rb:252:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/routing/route_set.rb:52:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/routing/route_set.rb:34:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/journey/router.rb:52:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/journey/router.rb:35:in `each'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/journey/router.rb:35:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/routing/route_set.rb:840:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.5/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/lib/middleware/omniauth_bypass_middleware.rb:32:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/tempfile_reaper.rb:15:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/conditional_get.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/head.rb:12:in `call'
/var/www/discourse/lib/content_security_policy/middleware.rb:12:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/session/abstract/id.rb:232:in `context'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/session/abstract/id.rb:226:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/cookies.rb:670:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.3/lib/active_support/callbacks.rb:98:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/callbacks.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/debug_exceptions.rb:61:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/logster-2.3.0/lib/logster/middleware/reporter.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/rack/logger.rb:28:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:18:in `call'
/var/www/discourse/config/initializers/100-silence_logger.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/request_id.rb:27:in `call'
/var/www/discourse/lib/middleware/enforce_hostname.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/method_override.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/executor.rb:14:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/sendfile.rb:111:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-mini-profiler-1.0.2/lib/mini_profiler/profiler.rb:281:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/message_bus-2.2.0/lib/message_bus/rack/middleware.rb:57:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:163:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/engine.rb:524:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/railtie.rb:190:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/railtie.rb:190:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/urlmap.rb:68:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/urlmap.rb:53:in `each'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/urlmap.rb:53:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/unicorn-5.5.1/lib/unicorn/http_server.rb:605:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/unicorn-5.5.1/lib/unicorn/http_server.rb:700:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/unicorn-5.5.1/lib/unicorn/http_server.rb:548:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/unicorn-5.5.1/lib/unicorn/http_server.rb:144:in `start'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/unicorn-5.5.1/bin/unicorn:128:in `'
/var/www/discourse/vendor/bundle/ruby/2.6.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.6.0/bin/unicorn:23:in `'
```
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [11 يوليو 2019، 11:49م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/483 "2019-07-11T23:49:14Z")
@Jeremie_Leroy @SDKAAA @icaria36 شكرًا لكم على تقارير الأخطاء.
بعد هذا الالتزام، يجب ألا تظهر المشكلة بعد الآن:
>
لمزيد من السياق:
> [@Custom field casting affected by recent update?](https://meta.discourse.org/t/custom-field-casting-affected-by-recent-update/122746):
>
> There have been multiple bug reports for the [events plugin](https://meta.discourse.org/t/events-plugin-calendar) in the last two days that all seem to be type-casting issues with custom fields. The events plugin hasn’t been substantively updated in a few months. The plugin.rb file casts event\_start as an integer: Topic.register\_custom\_field\_type('event\_start', :integer) The error is being thrown here: def has\_event? self.custom\_fields['event\_start']&.nonzero? end The error itself follows this format: NoMethodError (undefined method `nonze…
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [12 يوليو 2019، 9:55ص UTC](https://meta.discourse.org/t/angus-events-plugin/69776/484 "2019-07-12T09:55:09Z")
يبدو أن هذا التصحيح يعمل! يمكنني القول إن الفرق بين تطبيق هذا التصحيح وعدم تطبيقه بالنسبة لنا كان يعني وجود موقع معطل أو موقع (يبدو) يعمل بكامل طاقته.
كانت هذه آثار الخطأ:
- عدم عرض Discourse للمستخدمين المجهولين بعد الرأس (موقع غير قابل للاستخدام تمامًا).
- بالنسبة للمستخدمين المسجلين، على الأرجح لم يتم عرض المحتوى غير المخزن مؤقتًا (أي قوائم “الأحدث”)، وكان الباقي محظوظًا أو غير محظوظ.
- والغريب أن اثنين من بين ثلاثة مسؤولين فقدوا الوصول إلى واجهة الويب تمامًا، بينما كان الثالث (أنا) لا يزال قادرًا على الوصول إلى واجهة المسؤول وإنشاء نسخة احتياطية قبل إعادة البناء.
وبعبارة أخرى: مهما كان الخطأ، فقد يتحول إلى خطأ كبير يعطل الموقع.
في صباح أمس قمنا بترقية Discourse، وظهر الخطأ بعد ساعات.
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [12 يوليو 2019، 10:55ص UTC](https://meta.discourse.org/t/angus-events-plugin/69776/485 "2019-07-12T10:55:44Z")
ملاحظة: إذا تأثرت بهذا الخطأ، فقد تواجه مشكلة في قائمة مواضيع “جدول الأعمال” حتى بعد [التحديث](https://meta.discourse.org/t/events-plugin-calendar/69776/483?u=angus) (لا يتأثر باقي الوظائف بهذه المشكلة المحددة). لقد قدمت طلب سحب (PR) إلى Discourse لمعالجة هذه المشكلة الثانوية.
>
>
> While not likely, it is possible to end up with two rows in a custom field table… with the same related id.
>
> See further: https://meta.discourse.org/t/custom-field-casting-affected-by-recent-update/122746
>
> For example: https://discourse.angusmcleod.com.au/t/events-code-error-500/1254/4
>
> The data will look something like this.
>
> \`\`topic\_custom\_fields\`\`
>
> | id | topic\_id | name | value |
> | ------------- | ------------- | ------------- | ------------- |
> | 9180 | 62 | event\_start | 1563100201 |
> | 9179 | 62 | event\_start | 1563100201 |
>
> In most respects this eventuality can be handled in a plugin, however there is one place where this causes a cardinality issue that can't be handled in a plugin: ordering by the custom field in a \`\`TopicQuery\`\`.
>
> This PR adds a LIMIT to the custom field ordering statement in \`\`TopicQuery\`\` to handle that eventuality.
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [12 يوليو 2019، 12:59م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/486 "2019-07-12T12:59:24Z")
واجهة التقويم تواجه مشاكل أيضًا (خطأ 500). راجع [https://discuss-space.wmflabs.org/calendar](https://discuss-space.wmflabs.org/calendar) و [https://discuss-space.wmflabs.org/c/events](https://discuss-space.wmflabs.org/c/events)
---
### Author:  [@icaria36](https://meta.discourse.org/u/icaria36)
#### Post date: [12 يوليو 2019، 3:04م UTC](https://meta.discourse.org/t/angus-events-plugin/69776/487 "2019-07-12T15:04:22Z")
أهلاً… والآن تعمل دون أن نلمس أي شيء. 🤔
مُعدّل: والآن تعطلت مرة أخرى…
[Previous page](https://meta.discourse.org/t/angus-events-plugin/69776.md?page=23)
[Next page](https://meta.discourse.org/t/angus-events-plugin/69776.md?page=25)