Forum Replies Created
-
Posts
-
Ever since the new update to Community Events, I’ve had an issue with dropdown menus appearing too. I did the troubleshooting and it didn’t fix it. I’m not sure what it is because I enabled all the same plugins to test and couldn’t find another conflict. I went through and commented out all my theme’s tribe-event styles only to observe that it made no difference.
I went through and changed updated styles to reveal the old blocks that still work and hide the new divs because they aren’t working. But it just doesn’t look right, and I didn’t want to go through the hassle of restyling all the old divs. And I can’t simply switch themes to get things working. Things need to work!
However, through quite a bit of trial and error, I found what I could do to make things work. I noticed that the div was there and wasn’t getting populated. So I added a z-index of 1 to the reset in the stylesheet and it made the dropdown box show up.
html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, font, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td { margin: 0; padding: 0; border: 0; outline: 0; font-size: 100%; vertical-align: baseline; background: transparent; z-index: 1 !important;Then I went through and eliminated items one by one of what I thought would make the difference. I discovered that the div is what was causing the issue. First, I updated customized themed Community Event module files with the new ones that came with the plugin update and uploaded them to the server. Second, I added the code below to the stylesheet.
div.select2-drop, div.ui-timepicker-wrapper { z-index: 1888888888 !important; }Probably don’t need the z-index set so high, but I didn’t want to go through the process of finding the exact number for making it show up on top. Third, I commented out any z-index setting the theme had set for date pickers for the events plugin. This seemed fix the issue.
Hope this works for everyone else who might be going through the same thing. And hope it works for you too.
So I went into the themed file and saw a few changes, but after uploading the file, it didn’t change the fact that the map is still visible on events that shouldn’t have one.
Here’s an example of an event that doesn’t have the map embed or link checked on the backend but still has a map displaying under the meta modules. http://meridianpoint.church/event/the-crossing/2016-08-06/
Thanks! I’m glad you like the site. The calendar works perfectly for our needs.
Well, I definitely want it to show when the user wants it available. The problem is that it shows regardless. Do it doesn’t matter if I uncheck the box that displays the Google map on the back end of the event or not. It just generates one. I wanted to share the extreme with you. There’s a map…all the time, even when we don’t want one. Lol!
I’ll take a look at the single-event.php and see what the differences are between them. Sometimes the themed pages have caused conflict in the past whenever an update to the plugin occurs. I’ll post what I find.
Some people don’t want a map to be seen because it’s their personal address. But a map appears, even if it’s not the right address.
Figured it out! …for me anyway. Before the update, I created a themed page for the community events submission page. In order to fix the bazaar weirdness, I had to recreate the themed page even though the code that I themed it with didn’t change. All I used to theme the page to the site were wrappers around the form to hold within the page, added an image and a custom header. I’m not sure if the updated version files have a new line of code that might be slightly different from the earlier version, but it seemed to the trick and get things back to normal.
I just noticed that I didn’t update the plugins as well. Did that and am still getting the same results. I’ll change themes and do the plugin test thingy as well and see what I find out then post back.
http://meridianpoint.church/updates/events/community/add
And they are all posts, not just categories.
I figured out what the issue was! Something about the older version of community events add-on with custom modified templates wasn’t cooperating with the latest updates. I’m not sure if there were some coding updates that y’all did to the add-on, but I copied the latest version of the plugin’s template pages and re-customized the look to fit my theme as I did before. Now everything works fine!
So I guess it might be important to double-check custom templates when there’s an update to the plugin, especially if something goes wrong. 🙂
Hi,
I just update the plugin to it’s latest version and I’m still having issues not seeing the Event Organizer information in the email and on the backend. This is what is received.
Test Event
March 16 @ 8:00 am – March 16 @ 5:00 pm
Event Organizer
Event Venue
Where it’s located.
Description
This is another test to see if the update cured the issue.
Review EventThanks for the reply!
1. Are the users who are attempting to add new events logged in, or anonymous?
They are not logged in or have an account with the website. That didn’t use to be an issue as far as I know. People could anonymously submit an event and input their own information in the Event Organizer area of the form. Correct me if I’m wrong on this one.2. Are the users attempting to add a new organizer, or use an existing organizer?
They are attempting to add themselves as a new organizer. Using an existing organizer works without an issue. But if they are adding themselves, nothing appears in the email we receive or on the backend view of the event.I also just updated the plugins and am still having the issue. Another thing to note, while making the Organizer fields required, if someone tries to add themselves as a new organizer, the form will not submit and the error appears. It says that the fields have to be filled out. The thing is that they were filled out. So it’s not registering those fields as completed in the form upon submission.
