faction23

Thanks for sharing that yitwail, that’s definitely a problem. that div is injecting in the incorrect place. it should always be injecting as our absolutely outermost container. So the issue is not with the javascript but rather something to do with that function and your customizations.

I could check into this. the quickest way would be to get a copy of the customized files so i could take a look. if you feel like doing that you can hit up my gmail at cthulhumythos /a/ gmail.com

Hey there yitwail, thanks for reporting back! OK, we definitely have an issue somewhere here, I appreciate you reporting this.

The div with an id of #tribe-events should most definitely be outside of ajax, it is something we inject with php before any other events output begins.

I am talking about a div that should look something like this in the markup: <div id="tribe-events" class="tribe-no-js" data-live_ajax="1" data-category="">

Are we talking about the same thing? If so, and it truly is being incorrectly included *inside* #tribe-events-content then we have a bug I may need to patch. As said though i do not see this issue in my local nor have we had any other reports of this, so it would seem to be something exclusive to your install or a particular configuration?

Would you mind sharing a link to the install? Or if not, could you tell me theme, events template and plugins in use so i can try to recreate and get a fix out if it turns out its something I can patch?

Thanks so much, and sorry for any trouble again!

Hey there! I am the developer who wrote those lines. In fact that js is as it should be. If those handlers are not working for you until you nest deeper in, then it means there is an issue with the install. Do you have a link to a live example so i could check if there is some other issue? Thank you!

To explain: #tribe-events is a persistent wrapper div our plugin outputs outside of ajax modified content and is designed specifically to store certain settings for js as data attributes, and also to bind event handlers for a few elements destroyed during ajax.

Yes, barry is correct. you could also try out hiding all the yaselect funk in the bar by using a tribe specific parent class, just tested and that would work. that is hacky but quick relief until the author possibly makes a change.

This is definitely an issue an i am going to apply this fix for the next release. Thanks so much for bringing it to our attention mdd061000!

Hey bodenhai! While the core plugin does not contain this functionality we do have a premium “community” addon at our website that allows for people to submit events. ??

I’m going to look into this in the next day and see if there’s some formatting work I can do on my end to get maps to play nicer. Gmaps v3 has been changing things a bit and I have noted strange behavior from the api myself at times over the last bit in regards to address requests. Will report, thanks again for the feedback!

You bet Iowa Utility! I’m going to check into the other maps issue you’ve reported for next release.

icecolo, I hope its ok, i’m going to mark this as resolved. If you still find issue with the dropdown, please open up the issue again.

Thanks so much everyone for taking the time to provide feedback and help us get this dialed fast.

Release is out! Please let me know if that works everyone. Cheers.

Awesome icecolo! Yes, using jq 1.9 will patch it for now, the only thing to check for after switching versions is that any other plugins you may have active are ready for jquery 1.9 on the front end. Events was made jq 1.9 ready some time ago, but older plugins may have issues with that version as a lot of deprecated code was stripped in that release.

@iowa utility, you bet, the version number will increment for this hotfix so you will be notified of an update, but I will also post here at its release time. ??

Thanks again everyone.

Just wanted to let everyone know I have patched this and its gone to quality assurance for inclusion in the next hotfix.

Strangely, jquery 1.9 could handle the code causing the issue in firefox, while jquery 1.8.3 did not, hence my initial notes on variance for this bug.

Sorry again for any disruption.

OK thanks for reporting back icecolo! We had another tester who reported that as working for him when he experienced this, so I thought it worth a shot.

This bug is definitely random in its behavior. I am currently doing a solid refactor of the underlying code in this area which also has some other small issues, so should know soon the entire scope and verify the fix.

Again, sorry for the hassles, this is one of those fun little bugs. ??

Hey chodges1969. Are you experiencing this issue in firefox? Or is it another browser? We have determined the issue seems to be firefox specific, but if it is happening for you in another browser please let me know version if you could! I am working on patching this now.

My response in the other thread follows:

Hey gang. Apologies again. Looks like the issue came through in the minifier (google closure compiler). Until we get the hotfix out you can try adding

define(‘SCRIPT_DEBUG’, true);

to your wp-config file. This should fix the issue until we get the hotfix out as it loads the unminified files. Please be aware that constant does also cause wp to load unminified files in the admin for the core js and css though, so its up to you whether or not you are ok with that.

Will update this thread as soon as we get the fix out, at which point you can remove/set false this line.

Hey Iowa Utility. This may also relate to the issue with the minifier that occurred and is described in our discussion with the view switcher. Try out turning on script debug as described there and see if it helps.

I’ll be looking into this issue as well tomorrow – currently patching the view switcher issue – but would appreciate any feedback from you if you have time for it.

thanks,

sam

Hey gang. Apologies again. Looks like the issue came through in the minifier (google closure compiler). Until we get the hotfix out you can try adding

define('SCRIPT_DEBUG', true);

to your wp-config file. This should fix the issue until we get the hotfix out as it loads the unminified files. Please be aware that constant does also cause wp to load unminified files in the admin for the core js and css though, so its up to you whether or not you are ok with that.

Will update this thread as soon as we get the fix out, at which point you can remove/set false this line.