Skip to main content

Apostrophe CMS: filtering apostrophe-events based on a field from the (extended) widget definition

We have locations (and location-pages) as the primary page type on our site.

We use the apostrophe-events module to contain basic event (day, time, location, etc.) information which is then presented via widgets within the associated location page. Our events/event-pages definitions have a required 'location' field to associate a location, and work as expected. We have a 'featured-event-widgets' defined that presents a single, selected, event.

I am trying to implement the events modules standard 'events-widgets', which presents multiple events, however I want to filter the returned events by associated location and am running into a problem.

The default implementation works as expected - it finds x upcoming events (i.e. events that haven't happened/finished yet), where x is an arbitrary number specified in the widget, and passes the collection of events to the widget.html template for expression.

My issue is that the default widget provides the next events regardless of which location they are associated with i.e. while there may be 5 upcoming events defined in location A, if there are also upcoming events in locations C and B then the widget will return 2 events from A, and 2 events from B, and 1 event from C rather then the 5 events from location A as I desire.

I have updated the events-widget index.js to include the required selection of a location.

module.exports = {
  label: 'Events Widget',
  addFields: [
    {
      name: 'title',
      label: 'Title',
      type: 'string',
      required: true
    },
    {
      name: '_location',
      label: 'Location',
      required: true,
      withType: 'location',
      type: 'joinByOne',
      filters: {
        projection: {
          title: 1,
          slug: 1,
        }
      }
    }
  ]

So my widget definition has an associated location object, and all of my events pieces have an associated location, but I am running into a brick wall in trying to use that information to filter what the underlying cursor is returning to the widget.html template.

While I can/could filter within the template, by returning an arbitrarily large number of events in order to (mostly) ensure that I obtain the required number of events for the desired location, that seems like a broken approach.

I thought adding the addFilters: [...] definition to index.js functionality would give me what I need, but I have been unable to get that approach to work e.g.

  addFilters: [
    {
      name: '_location',
      label: 'Location'
    }
  ]

After spending a bunch of time on Google and StackOverflow it seems like I might be able to do something by overriding and expanding the default construct definition in index.js, and using self.widgetCursor to achieve this, however I'm unable to determine where to find the location specified in the widget definition (presumably somewhere buried in req) to do this.

  construct: function(self, options) {
    // Append upcoming flag by extending widgetCursor.
    var superWidgetCursor = self.widgetCursor;
    self.widgetCursor = function(req, criteria) {
      return superWidgetCursor(req, criteria).upcoming(true);
    };
  }

I'm hoping I'm missing something glaringly obvious that someone can point out to me :)

Many thanks,

Shaun

Via Active questions tagged javascript - Stack Overflow https://ift.tt/jC63uEl

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype
Post a Comment
Read more

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console...
Post a Comment
Read more

ValueError: X has 10 features, but LinearRegression is expecting 1 features as input

So, I am trying to predict the model but its throwing error like it has 10 features but it expacts only 1. So I am confused can anyone help me with it? more importantly its not working for me when my friend runs it. It works perfectly fine dose anyone know the reason about it? cv = KFold(n_splits = 10) all_loss = [] for i in range(9): # 1st for loop over polynomial orders poly_order = i X_train = make_polynomial(x, poly_order) loss_at_order = [] # initiate a set to collect loss for CV for train_index, test_index in cv.split(X_train): print('TRAIN:', train_index, 'TEST:', test_index) X_train_cv, X_test_cv = X_train[train_index], X_test[test_index] t_train_cv, t_test_cv = t[train_index], t[test_index] reg.fit(X_train_cv, t_train_cv) loss_at_order.append(np.mean((t_test_cv - reg.predict(X_test_cv))**2)) # collect loss at fold all_loss.append(np.mean(loss_at_order)) # collect loss at order plt.plot(np.log(al...
Post a Comment
Read more