Greg Mount
Forum Replies Created
-
Posts
-
Hi Jane. Thanks for the kind words. The events calendar is built with… The Events Calendar.
I should also note that we have dropped GD on that site and will be re-launching http://www.torontomindbody.org using a different tool, so my original post in this thread is pretty much moot. We still have GD implemented on http://www.animalequity.org so that would be the place to go for a showcase of GD core and location manager on Genesis framework… and cats.
@msgliniewicz: We switched from Canvas to Genesis. Canvas is great, but Genesis is better. 🙂
We went live back in July and this is still the #1 complaint I get from our clients. Just today we received the following support message:
“Hi, I am new to Toronto Mind Body listings, and am listing teacher training events that occur on multiple dates. I would like all multiple dates to occur in a single listing, rather than a separate listing for each date. Is this possible? For now, I have resorted to only scheduling 1 day to your system to avoid the course appearing 3 separate times. Kindly let me know how to best proceed.”
Thanks Stiofan and Paolo. It would be ideal to add a “Cancel Subscription” link on the listing page, visible to authors and admins, that fires curl.
@pawon: It sounds like you are using live mode over http. Stripe will work over http in test mode, but live mode requires the add-listing and preview pages to be served over https.
@stiofan, here’s a link to the events that Stripe sends:
https://stripe.com/docs/api#event_types
It would be great if the gd stripe plugin responded properly to these events. For example, I currently receive a “Payment success to admin email” message when a card is declined or money is transferred to our bank account. Makes me wonder what our clients are receiving. 🙂
Thanks Stiofan. Adding your code to functions.php didn’t work, but I can confirm that FORCE_SSL_ADMIN is the cause.
You can ignore the different domains. I pasted the console output from the development site instead of production. The issue is present in both production and development.
Thanks for the quick action on this bug. I was able to fix before my users were out of bed. 🙂
@dmitri: I used the following css (it’s a little goofy because the code doesn’t provide semantically meaningful classes, but it gets the job done):
#geodir-sidebar .geodir_more_info br { display: none; } #geodir-sidebar .geodir_more_info span[itemprop]:after { content: ", "; }Interestingly, this issue only seems to affect places… event listings are fine.
Same issue here on two different sites.
I’ll go back to my original suggestion which is to have two event types: simple (single day/time) and advanced (what we’ve got now). This would solve 80/20 without creating more technical headaches.
@stiofan: On September 5th you asked me, “if you are dedicated to getting this working then maybe you can help?” I pinged you three times with no response, so let me ask the question in reverse: are you committed to getting this working?
@stiofan: There are so many use cases that it’s unlikely you will find a single solution that works for everyone. That said, most systems I’ve encountered order events by start date/time, so your example list would be ordered as you’ve presented it.
Here’s the challenge: GD needs to differentiate between single and recurring events. For example, an event listing for a two-week conference should not display 14 separate event listings. However, a 10-week class that takes place every Thursday evening probably should.
Here are two possible solutions:
1. Redesign the event date/time form to provide to input methods: basic or recurring. The basic input form offers the usual start and end date/time field. This would cover a single event, such as the 2-week conference example above. The recurring event form would be the form in use now, which would handle events like the 10-week course scenario. Check out the date module for an example of how this has been implemented in Drupal.
2. A second (more simplistic) approach would be to provide a simple “Remove duplicates” checkbox option on the GD admin panel. This site-wide option, if checked, would display only the first instance of an event in the listings. We currently run custom code against the events rss feed to remove duplicates in the feed.
I prefer the first option because it simplifies the UI (start and end date/time) while still handling all event scenarios (single and recurring).
