Forum Replies Created
-
Posts
-
Awesome – thanks Anthony. As you can see that one is sort of a doozy. We’ll keep looking at it and I’ll respond over at the other thread accordingly.
Hey Marco. I’m not quite sure I understand the problem you’re having. Can you elaborate a bit? Are you using your own translation files, or ones that came with the plugin itself?
Hi again Peter. Just a heads up that we’ve fixed that FAQ, cleaning it up and confirming the code’s functionality along the way. Should be all set now but please let us know if you need anything else. Thanks again for pointing that out!
Hey again Maeda. So I reviewed this with the dev team today, and it looks like what you’re requesting here is no small task…it’s going to be pretty complex whatever the link ends up being and totally down a path of customization that’s unfortunately outside the realm of what we can support. Good luck figuring it out…and anyone else who has a suggestion on here is free to chime in with that. Would be interested in seeing what you ultimately come up with if you do figure this out.
Sorry I couldn’t offer up more, though.
Thanks for confirming Dave. Glad to see that got the first issue resolved.
As I’d mentioned above, I am unable to recreate the recurring events problem – I followed your instructions exactly (even with the same event name/URL) on a vanilla 2011 install with no other plugins active and the issue did not persist. This makes me think it’s almost certainly a conflict with your theme or another plugin. Have you tried deactivating plugins, and reverting to the 2011 theme as necessary, to try and identify where the conflict is? That’d be my best suggestion at this point – if you can indeed figure out where the conflict is I can try and advise you best I can from there.
Hi Anthony. Thanks for the note and sorry to hear that you’re having issues. Is this possibly the same problem being discussed here (https://theeventscalendar.com/support/forums/topic/updating-button-keeps-spinning-not-new-publishing-eith), or have I misunderstood the problem?
Hi Eric. Thanks for the note. As seems to be indicated by the other comments in the thread here, and by the fact that we’re unable to recreate this locally, this is likely a conflict of some kind. But I have a couple of options you could try. If you want to email me, I can give you the current code (somewhere between 2.0.3 and 2.1) and you can install that to see if it fixes the issue. If not, I’d ask you revert to the 2.0.3 code and send me a set of backend credentials, along with a link to this thread and some instructions to recreate on your site, so I can try to verify this there and document/pass it off to the devs.
Hey Shawn. Awesome to hear you found a workaround here – and thanks for the words about the plugin 🙂 We’re happy to hear it and appreciate all the exposure we can get.
If anything else comes up or if you ever want to revisit this issue (particularly after updating to the official 2.1 release, should it persist) do let us know.
Hi there Maeda. This is an interesting request. Not sure how you could do this myself, but it’s possible one of our devs could point you in the right direction. Let me see if anyone has any ideas.
Hey Josh. Thanks for the feedback. When the plugin was first released, it was geared more towards developers. Since 2.0 launched it’s become apparent that the market is broader than that and we’re shifting away from the “mean and lean” approach a bit as a result. The templating structure and the overall customization flexibility will definitely be improved during the 2.1 lifecycle.
Thanks for the heads up Peter. We’ll get that fixed up this week – first I want to have a dev take a look as that code is sort of old, want to make sure what we initially had there is still correct. I’ll drop a note in here once that’s set.
Thanks for the reports, guys. I’m going to see if Jonah from our dev team can take a look at this and share some insights. I know that the templating structure will be changing quite a bit for 2.1, which I suspect will resolve this…but I’ll try to see if there’s anything we can share in the short term.
Hey Matthew. Thanks for the note. We’ve gotten a few reports of this already; unfortunately there’s a bug with how contributors interact with the plugin in the 2.0.3 code that is likely causing this. Best I can offer up at this point is that we’ll have a fix in 2.1, which we’re working on now and should be out within the next month. Sorry I couldn’t share more here.
