Forum Replies Created
-
Posts
-
Thanks for the email, Brent. I used the creds you provided and jumped into the backend and I was indeed able to recreate the issue. I had a couple thoughts on this:
* I noticed that the backend admin bar is hidden, and seemingly on JUST the Events pages, which I didn’t think WP offered a solution for: http://d.pr/i/WQUl. How was that done? If it’s custom code, is it possible that could be conflicting with the visual editor? No idea if that’s the case but it looked weird as I didn’t have the logout options or anything else.
* I see on the admin there, we have “roles” & “restrictions.” In the past we have heard of some conflicts with custom role managers & users generally trying to adjust/restrict permissions. It sounds like per above you’ve already tested with that deactivated but I just want to double check.
* The broader events list is also messed up; when I attempt to view it as an editor it just sits at http://d.pr/i/Lfea.
* We have had a number of users report conflicts with WP-Multitouch as well, but as per the notes earlier it sounds like you’ve already deactivated that too. Let me know if I’m wrong there.All that to say…this does seem specific to the Editor role, and specifically that editor role’s interaction with Events. I’m really at a loss as to what could be causing this (you’re the first we’ve encountered it with), so if you can confirm then points above and that you’ve tried/retried those things, I can see whether our dev team has any suggestions on their end. Apologies for the inconvenience thus far.
Hey Omni. Thanks for the follow-up; I see that now, and looks like that is a byproduct of this issue as well. We’re working on it now and should have a fix before the next (2.0.6) release is deployed.
In the interim, though, you really don’t need to add the key at all. The key is not required for any functionality to work; everything operates 100% without the key in place. I’d say just move to your “live” site now, leave the key out of the picture, and add it when we fix the problem I’ve mentioned (we’ll announce it on the forums/our website). This will be before the 2.0.6 build is out so you won’t have to worry about missing any update notices.
Let me know if you have any other questions here. In the short-term, though, you’ll be fine taking no action.
Hey Liana, so it sounds like you’re all set as per your last note…am I wrong there? If the issue persists, does Henry’s most recent suggestion get you where you need to be?
Hey Brent. That’s very bizarre; is the site public, so I could take a look? If so please send me a set of Editor credentials to pro /a/ tri.be with some basic steps to recreate and a link to this thread…I can try to figure out what’s going on from there.
Hey Yancy. Thanks for the follow-up, and sorry to hear you’re disappointed. I guess I’m a bit confused as to what the issue with the code from the FAQ actually is. Jonah and I just reviewed this and the code as it stands in the FAQ is still functional: it allows you to attach WordPress’ regular tag taxonomy to your events, so tags are extended to the Events themselves. It sounds like what you’re going for is to have the tags returned with events-based links, which this method will not allow nor does it purport to. Have I missed something here? We do appreciate you bringing up the fact that it needs to be wrapped in a function…while dev-minded users will be aware of this we’ve adjusted the FAQ to make it extremely clear that this is necessary (and to clarify the other points I made earlier in this paragraph). Thanks for the heads up there.
It’s also worth noting that the functionality you are requesting is on the docket for the 2.1 release, so a more robust approach to tagging is in the works as well. We find it unfortunate to hear this comes of as misleading and incorrect though, since that was certainly not the intent, and want to make it right. What could we do to improve the experience for you?
Hi Yorgos. Thanks for the follow-up here; glad to hear you’ve made some progress but bummer that the initial issue here remains. There is a known bug in the system now with custom fields deleting when they shouldn’t (either upon resaving the settings page or possibly deleting the plugin itself). So that could account for why they went away at one point on Settings (though this change is being worked on now and will be fixed in the next release).
If I understand your last note, it sounds like you reached the conclusion that the core problem here was the qTranslate plugin. Am I correct there? If so, that’s definitely possible…we’re testing against both that and WPML for our 2.1 release, and doing whatever we can on our end to ease the integration with those two plugins, but at this point there is unfortunately no official guarantee things will play smoothly on that end.
I can see the value add here too, Henry. I’m continuing to make a case for it on our projects system too, where we’re debating the value. No guarantees and there sadly isn’t much I can offer up in the short-term, but I did want you to be aware that it’s being discussed.
Sorry I couldn’t offer up more in the short-term. If you’ve got other questions please do let me know.
Thanks for confirming, Patricio – my apologies that I didn’t see your comment(s) until now, for some reason the 4/17 post never showed up on my dashboard. My apologies.
What theme are you on? No guarantees we can provide guidance on integration, but if you let me know the name I can share any knowledge I have on known conflicts, possible solutions, etc.
Hey Robert. Thanks for the thoughts here; these are solid ideas. Can you elaborate on the first point? I’m not sure I understand and am not seeing any overlap on my Organizer list. A screenshot would be awesome 🙂
I can hear you on the additional fields, for sure. We actually pre-launch had a ‘paragraph’ block but killed it because we thought people woud be confused by having two text fields. The fact that there is demand for it means we should probably add it back…
Mariana: the integration on your two sites is looking very slick. You’re one of the first who has showcased their work with WPML so hopefully this will give them some ideas.
Henry: that is awesome. As you mention tons of people have been asking about such a feature lately…this will show them all it can be done.
We’re building a nice Showcase page on the tri.be site, too, so we can highlight some of these sites in greater depth. We’re excited about where it’s headed and I’ll definitely post a link to the finished product whenever that’s done. It won’t be anytime this week or anything but (like so many other things) it’s on the radar!
Hey guys. This is unfortunately a known issue that we introduced with the 2.0.5 release; we’re working to fix it now and should have resolved this week. There are a couple others threads on the forum here where we were discussing it previously after some users brought it to our attention.
Basically since the key isn’t required for the plugin to run anyway, I’d say ignore it for now. We’ll announce here when the bug is fixed and users can go make the change at that time. But since no functionality is lost without the key active, you aren’t missing anything without it.
Hope that helps and my apologies for the inconvenience thus far. Please let me know if you have any other questions or if I can elaborate on the points above.
Hey Louis! No problem, this should be easy. Just go to Settings -> The Events Calendar, and hit the “Licenses” tab. You should be able to just paste your Events Calendar PRO key (copied from the tri.be website) into the appropriate field there. It’ll validate for a second, but when you get the green text telling you it is valid and providing an expiration date, you should be all set.
That help? Let me know if not and I’ll adjust my response accordingly.
Awesome to hear, and happy to help. Let us know if we can do anything else for you down the road. Thanks for your support.
